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

Run dependence for condition queries #57

Open
sdobbs opened this issue Feb 21, 2017 · 4 comments
Open

Run dependence for condition queries #57

sdobbs opened this issue Feb 21, 2017 · 4 comments

Comments

@sdobbs
Copy link
Collaborator

sdobbs commented Feb 21, 2017

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.

@DraTeots
Copy link
Collaborator

Could you suggest real-life example of what and how should be searched?

@sdobbs
Copy link
Collaborator Author

sdobbs commented Feb 28, 2017

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.

@DraTeots
Copy link
Collaborator

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

@sdobbs
Copy link
Collaborator Author

sdobbs commented Feb 28, 2017 via email

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

No branches or pull requests

2 participants