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
Adding a workchain that takes files from a folder and runs a given calculation on all the files. The use for this is to use it later inside a training workchain.
Problems:
Adding more codes with different entry points might make the thing slightly more complex than expected. Basically I would like to give as an input an entry point for the calculations to run and then use it to set up a calculation.
To explain better: this is how you set up a calcjob or a workflow. Let's use the entry points mlip.opt and quantumespresso.pw.relax
Then this is how the WorkChain takes the inputs. Basically spec.input are inputs for the first steps of the workchain, and then every subprocess takes its own inputs in the form of a dictionary with the expose_inputs function.
At the moment I cannot use the "entrypoint" input to chose the type of calculation to do inside the workchain, because both the input and expose_input need to be defined outside, so I have to have basically different keywords for any calculation I want to run high-throughputly (in this example I want to run either the janus opt or the qe-workchain for opt).
I will ask about this in the aiida.discourse, but if this is not fixable basically I will need to manually choose which types of calculations I want to add to the workchain.
TLDR
making a high-throughput screening for different types of calculations (quantumespresso, janus opt, janus sp etc) might make it uselessly complex for me and the user, so I need to decide what's worth doing:
what calculations do we want in the high-throughput screening workchain? are janus optimisation and qe optimisation enough?
Should I just not make a high-throughput workchain and proceed with the training?
The text was updated successfully, but these errors were encountered:
Adding a workchain that takes files from a folder and runs a given calculation on all the files. The use for this is to use it later inside a training workchain.
Problems:
https://github.com/stfc/janus-core/issues/196
To explain better: this is how you set up a calcjob or a workflow. Let's use the entry points mlip.opt and quantumespresso.pw.relax
Then this is how the WorkChain takes the inputs. Basically spec.input are inputs for the first steps of the workchain, and then every subprocess takes its own inputs in the form of a dictionary with the expose_inputs function.
At the moment I cannot use the "entrypoint" input to chose the type of calculation to do inside the workchain, because both the input and expose_input need to be defined outside, so I have to have basically different keywords for any calculation I want to run high-throughputly (in this example I want to run either the janus opt or the qe-workchain for opt).
I will ask about this in the aiida.discourse, but if this is not fixable basically I will need to manually choose which types of calculations I want to add to the workchain.
TLDR
making a high-throughput screening for different types of calculations (quantumespresso, janus opt, janus sp etc) might make it uselessly complex for me and the user, so I need to decide what's worth doing:
what calculations do we want in the high-throughput screening workchain? are janus optimisation and qe optimisation enough?
Should I just not make a high-throughput workchain and proceed with the training?
The text was updated successfully, but these errors were encountered: