We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be very useful if one could use the output from a code as the value for a variable in a YMMSL file.
Suggestion for format: code_name any arguments
code_name any arguments
I think it would make sense to do this in the environment of the muscle_manager interpreting the YMMSL files.
The configuration.log would show the instantiated value.
One immediate example that comes to my mind would be to provide an auto-incrementing run number.
As an example, I have a script that
and would be called in a typical use case as
settings: run: next_run test 92436
next_run test 92436
This would remove the problem of overwriting an existing run.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It would be very useful if one could use the output from a code as the value for a variable in a YMMSL file.
Suggestion for format:
code_name any arguments
I think it would make sense to do this in the environment of the muscle_manager interpreting the YMMSL files.
The configuration.log would show the instantiated value.
One immediate example that comes to my mind would be to provide an auto-incrementing run number.
As an example, I have a script that
the program will take the latest value from ~/.shots/$DEVICE/$SHOT/run,
increment it by one, store the new value and return it
and would be called in a typical use case as
settings:
run:
next_run test 92436
This would remove the problem of overwriting an existing run.
The text was updated successfully, but these errors were encountered: