You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zppy can currently be run on multiple simulations/members of an ensemble, by using different configuration files to specify different data paths.
It would be nice to add automation such that a single zppy configuration file could be used to post-process all members of an ensemble. Perhaps a summary pdf could be generated as well, displaying mean, median, etc.
The text was updated successfully, but these errors were encountered:
One potential issue may be submitting/queueing the large number of jobs that would be generated, considering post-processing just one simulation/member launches many jobs.
I ran zppy on a 250-member ensemble using a code that loops over each case and modifies the .cfg file, then submits the runs if I have less than some threshold number of runs in the queue. It worked great!
zppy
can currently be run on multiple simulations/members of an ensemble, by using different configuration files to specify different data paths.It would be nice to add automation such that a single
zppy
configuration file could be used to post-process all members of an ensemble. Perhaps a summarypdf
could be generated as well, displaying mean, median, etc.The text was updated successfully, but these errors were encountered: