WIP: latest updates for LDF

[wwieder]

• correctly concatenates h1 files now for subgid (pft) ouptput
• Updating to a newer version of uxarry seems to cause plotting issues...?
• Draft notebook with PFT survival example from h1 output for further development
• [ ]

[TeaganKing]

Somewhat relevant to this issue ticket, can we update the LDF/lib/scripts/plotting/regional_climatology.py file line 87 to not use a hard-coded ymlFilename? This causes some issues when running from a different location than the LDF directory-- eg when running through CUPID. I'm thinking something in the config file similar to the defaults_file would probably work.

[wwieder]

Maybe we can make this a priority at the CUPiD meeting tomorrow, @TeaganKing. there are a number of issues with regional plots in CUPiD that I'd like to fix. Some of these may already be addressed in the clm-diags branch on ADF.

[TeaganKing]

It's on the agenda!

[wwieder]

Somewhat relevant to this issue ticket, can we update the LDF/lib/scripts/plotting/regional_climatology.py file line 87 to not use a hard-coded ymlFilename? This causes some issues when running from a different location than the LDF directory-- eg when running through CUPID. I'm thinking something in the config file similar to the defaults_file would probably work.

I also noticed that LDF has some infrastructure for reading in default.yaml files around line 112 of the same regional_climatology file that could be helpful for reading in the location of the regions_lnd.yaml file in question here.