-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate reference data from CloudMicrophysics.jl and Cloudy.jl within CI build instead of storing datafiles in the repo (which do not contain instructions on how to generate these data...) #1279
Comments
For the ARG example this should be pretty simple. The same figures from the original paper are generated in the The Julia scripts to make these plots are https://github.com/CliMA/CloudMicrophysics.jl/blob/main/docs/src/plots/ARGplots_fig1.jl and https://github.com/CliMA/CloudMicrophysics.jl/blob/main/docs/src/plots/ARGplots.jl. |
I don't have much experience with Cloudy. Thats a question to @edejong-caltech and @sajjadazimi I can help with the ARG plots. Do you really want your CI depend on Julia packages? Or would you rather just generate the data yourself once and then save it? Or is it enough to put a link to our CI? |
@claresinger, @trontrytel, thanks for following up
I'd vote against having the data saved, and in favor of generating it on CI. This ensures that:
BTW, we already depend on Julia in CI to check the README Julia snippets: PySDM/.github/workflows/readme_snippets.yml Lines 39 to 53 in d6b0df2
In PyMPDATA, in an analogous way, we are comparing to output from libmpdata++ generated on the fly: https://github.com/open-atmos/PyMPDATA/blob/29fb3b836f5dc730e49bc4dc2075ddc52a26c667/.github/workflows/tests%2Bpypi.yml#L176-L184 It is enough to have one job executing the calculations with a Julia package, which then can upload the generated JSON files as artifacts for other jobs to be fetched, here's an example (Julia vs. Matlab vs. Python output comparison): https://github.com/open-atmos/PyPartMC/blob/main/.github/workflows/readme_listings.yml
I'm not sure if sharing artifacts across different repos and platforms isn't more difficult than generating it in PySDM's CI? |
Sounds good. I didn't remember that you already have some Julia in your CI. Then we just have to run those two scripts from your documentation here. I can make an mwe with the necessary package manager commands |
Hi. Here is a code snippet that should generate the data for the 5 figures from the paper. Just change the extension from
Also, I'm using some simple plotting package to see the results, but obviously that dependence and the plotting should be deleted in the end. |
Thank you @trontrytel ! |
Stale issue message |
@trontrytel, @edejong-caltech,
In two examples in PySDM, we store in the repo data generated with CliMA Julia tools:
It would be great to generate these data on the fly in CI. For example, we could write it to JSON from Julia and then load from Python.
I'd need your help here - we don't have yet even information on how to generate these data with the Julia tools, so this would improve reproducibility and clarity of the examples in many ways!
We can of course specify the exact version of the Julia tools to use.
We can also generate these datafiles once and make them available as artifacts for all other CI jobs - it's enough if this works on one single environment.
This should be also helpful for the Julia projects, as bumping versions we will have info if these output changes or not.
Help welcome!
Thanks,
S.
The text was updated successfully, but these errors were encountered: