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

Thinking about STIPS configuration parameters #150

Open
york-stsci opened this issue Oct 5, 2021 · 0 comments
Open

Thinking about STIPS configuration parameters #150

york-stsci opened this issue Oct 5, 2021 · 0 comments

Comments

@york-stsci
Copy link
Collaborator

Currently, STIPS has a bunch of configuration parameters, and all of them are treated the same way. They have a default value kept inside STIPS itself, can be given a default value by creating a new configuration file and telling STIPS to look at it, and can be set at run-time by providing values when creating top-level objects (SceneModule and ObservationModule).

For some configurations (e.g. log level, data output location, whether to use parallel processing, PSF oversampling) this makes a lot of sense, because a single observation (or scene) should probably use the same values throughout. However, for some configuration parameters (e.g. random number seed) it probably makes more sense to let each detector in an observation have a separate value (although, especially for testing/reproducibility purposes, having that separate value be generated in a known way does likely make sense.

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