-
Notifications
You must be signed in to change notification settings - Fork 15
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
suggestions from pmd general assembly #1193
Comments
I like the idea, in particular when we move towards one HDF5 file per workflow rather than once HDF5 file per calculation. |
there was also a request to allow custom submission scripts - since there was a user that wanted to adjust parameters inside the job submission script across varying types of jobs. |
In
We might have to document it a bit better. The full discussion on this topic is available in the corresponding pull request #1082 For future reference, the documentation is a bit better for |
so basically, replace the parameters that are changing anywhere in the jinja jobscript with the text
right? |
Correct. |
Suggestions from materialdigital general assembly.
Export an environment yaml inside the hdf5 file automatically?
Down to the granular (atomic dependencies... e.g. not just "pyiron_atomistics" but all the package versions that were used in a particular pyiron run?
The text was updated successfully, but these errors were encountered: