Hello everyone,
I am continuing my development of the aiida-flux-scheduler, Implementing the Flux scheduler from LLNL, and want to save information for the scheduler to the parent workchain. I am wanting to do this with no changes to aiida-core and just using what’s available. I had thought to put it into the builder.metadata but that only accepts certain values. Then I had remember people discussing extras but it seems that only works for the children of the parent workchain. For reference, I attempted to do this on the PwRelaxWorkChain for QE. The data format would be simple dictionary. Please let me know if there is another spot I could save this information.
Poking around I see that you can do node.base.extras.set(). This would work if I was using the submit option which returns the node. Currently I am debugging and would want to set this information before as I am using the run command so I can actively see what’s happening. Additionally, I am wanting to have this information available to the scheduler so it would need to be available at the time of submission.
@ali-khosravi Wondering if you could give some feedback on this? I’m close to finishing the features I want and just not sure how to proceed. Thanks!
@nkeilbart I don’t think if it’s possible to make the info of node.base.extras.set() available in the scheduler without touching aiida-core.
I still remember some of the messages that we had communicated through the other thread, where you wanted to develop a scheduler plugin. Are these related to that?
Since this has been long standing, I suggest let’s set up a video call so we talk.
I think it’s easier and more efficient that way.
Just drop me an email with your desired date/times:
ali.khosravi@psi.ch
Thanks Ali. I sent an email reaching out. The way I’m attempting to set this up I would hope doesn’t need to alter aiida-core. The main thing I need is a way to save information to the parent workchain with information for the flux scheduler. A simple way would probably just be to throw it in the description for now. I had hoped there would be a generic slot that would be available but I wasn’t able to get it to accept it. I do have an idea where a small modification in aiida-core could fix it and hopefully with minimal implications for other plugins. Either way, I’ll hopefully talk with you soon. Thanks.