-
Notifications
You must be signed in to change notification settings - Fork 7
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
Run dependence for condition queries #57
Comments
Could you suggest real-life example of what and how should be searched? |
This is motivated by the idea that at some point the name of the default config file name may change, so one could do something like: @is_production = ( (run<33000) && (run_config== FCAL_BCAL_PS_m9.conf) ) || ( (run>=33000) && (run_config== FCAL_BCAL_PS_ST_m9.conf) ) In reality, the search would be a lot more complex than this. At some point, daq_run might also be set to a non-"EXPERT" value. |
Aha. Now I clearly understand the problem. Could inventing one more condition that track this condition fix this? For example run_config_xxx which depends on run_config but is the same for run<33000 and run>=33000 |
Yes... interesting... I think that could work? Let me think about this.
…On Tue, Feb 28, 2017 at 5:48 PM Dmitry Romanov ***@***.***> wrote:
Aha. Now I clearly understand the problem. Could inventing one more
condition that track this condition fix this? For example run_config_xxx
which depends on run_config but is the same for run<33000 and run>=33000
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABIJaudsiIctXtbYLEnHdLuAyHmK0R2hks5rhKQ1gaJpZM4MHb0E>
.
|
We need to be able to specify some run-dependent conditions for standard search aliases e.g. "@is_production", so it would be nice if these conditions could be built into the aliases, or some other method.
The text was updated successfully, but these errors were encountered: