LLNL
Add support for non-merlin blocks in specification file
I'm not too familiar with the merlin workflows yet, so I'm not sure what is the purpose for the addition of non-merlin "user" block. If you could let me know what to add for docs I can include it in the merlin_specification.rst and merlin_variables.rst where it is documented.
We can workshop it in the comments, maybe @jimagaffney can give us an example.
The user block allows other variables / yaml syntax in the workflow file to be propagated through to the workflow (including in the .parital.yaml and .expanded.yaml). This gives the user increased flexibility in how they write their files.
For instance, a user can use anchors etc. to define configurations and then reference them later
That's great. Is there an sample or example I can use? Since in the current documentation an example was given for each block.
That's great. Is there an sample or example I can use? Since in the current documentation an example was given for each block.
@jimagaffney can you cook up an example?
That's great. Is there an sample or example I can use? Since in the current documentation an example was given for each block.
@jimagaffney can you cook up an example?
Jim says he can cook up an example at the end of next week
I think we should be good for this one and the other PR. #378 I don't have anything else I need to change for either. If you can take a final look, to check we should be good to merge them in.