Replies: 2 comments 5 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
Here is a proposal for new functions to support multi-site ensemble runs. (Originally started as a GH issue, but figured there are enough unknowns and open questions that it would be helpful to get feedback here first. Here is the draft: DescriptionCreate new functions that
Proposed SolutionA workflow might look like This is mostly based on https://github.com/ccmmf/workflows/blob/fb6aeb3b678ecabc89bc7af706aeafa05b799426/downscale/02_extract_sipnet_output.R#L85 New functions (please suggest changes to names and args)
I've written code that produces the arrays and netcdf files, but have been using the tabular CSV files in my workflows. Considerations
Additional Context
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Overview
@infotroph and I were discussing how to put together multi-site ensemble forecast outputs. Current behavior is that
And PEcAn generates summary Rdata files including
But for these Rdata files (and associated PDF summary plots), each site overwrites the previous site's output.
So we were looking for a way to organize these outputs by site.
CMS project approach
For the CMS project, outputs are organized thus1:
sda.all.forecast.analysis.Rdata contains analysis.all and forecast.all, which are lists of matrices (data.frames, one per time step) that can be used for downscaling.
These data.frames look like:
Questions:
@dongchen Zhang
@PecanProject (community):
ensemble.*.Rdataand associated files from individual sites that get clobbered during multisite runs?Footnotes
from geo.bu.edu:/projectnb/dietzelab/dongchen/anchorSites/NA_runs/SDA_25ens_2024_11_25/ReadMe.txt ↩
Beta Was this translation helpful? Give feedback.
All reactions