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

Runtime configuration of reconstruction algorithm #188

Open
mlincett opened this issue May 9, 2023 · 1 comment
Open

Runtime configuration of reconstruction algorithm #188

mlincett opened this issue May 9, 2023 · 1 comment
Labels
enhancement New feature or request skydriver Specific to production concerns: condor, REST, docker, singulairty, etc.

Comments

@mlincett
Copy link
Collaborator

mlincett commented May 9, 2023

Presently, reconstruction algorithms have some hardcoded behaviors that we may want to configure at runtime. For example, the number of tested vertex positions.

In some cases, these can be tuned with environment variables (like the "mini" scan configuration, see start_scan.py).

We can think of a scenario in which we pass an additional string (JSON?) as config for the reconstruction algorithm.

@ric-evans
Copy link
Member

This sounds like a reasonable need. I imagine there will be some settings for reco X that would not be apply to reco Y. I propose using a single dedicated CL arg, like --reco-algo-config that will take key:value pairs (similar to --nsides). This avoids the overhead transferring and persisting small config files.

For SkyDriver, the user can provide a dict.

@ric-evans ric-evans added enhancement New feature or request skydriver Specific to production concerns: condor, REST, docker, singulairty, etc. labels May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request skydriver Specific to production concerns: condor, REST, docker, singulairty, etc.
Projects
None yet
Development

No branches or pull requests

2 participants