Skip to content

Conversation

@painter1
Copy link
Contributor

This branch adds a multiprocessing capability to multidiags.py.
Also it has new tests: one of multidiags itself, and one comparing metadiags to multidiags.

…or model,obs,output) -

because os.path.exists() doesn't understand '~' in a path.
…sses have to be run in a

shell with Popen().  Communication is done with a temporary file and through the stdout pipe.
There remains some non-functional commented-out code to do this other ways (which would be
better is spawning, rather than forking,  were allowed those ways.)
… the number of processes to

be run simultaneously.  For now, the maximum is hard-coded.
…or Popen, it pickles its

Options object to a string, which is passed to diags.py in the shell command line.
…g code, which is no more than

a function call.
…ames. It makes the filenames

more repeatable, but would require us to change the present ctest baselines.
…d for use in the NetCDF file's name.

In the write_plot_data method, getting the axis of zax, do it whether zax is a variable or tuple of variables.
…omparison of an Options

instance for collection 7s as generated by metadiags and multidiags.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants