Skip to content
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

Automatization / making config files more clever #423

Open
arummler opened this issue Mar 11, 2018 · 0 comments
Open

Automatization / making config files more clever #423

arummler opened this issue Mar 11, 2018 · 0 comments

Comments

@arummler
Copy link
Contributor

Some thoughts: In the moment there is only the OnNext... mechanism which loads a consecutively numbered config after the run stops. This requires a lot of config files. What e.g. about having a counter variable $runcounter which can be used in expressions within the config file? A setting NextConfigFile= in the config file? More complex expressions (with some sort of library). Remote control of the run control in order to have a Monitor e.g. monitor quality of data and automatically stop and restart run with the same config (StopRun(not-successful), reinit, reconfig, StartRun).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant