-
Notifications
You must be signed in to change notification settings - Fork 49
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
prepare POCS for a filterwheel mode #941
Comments
"Modify target.yaml parser to accommodate the filter_name key." I believe this is done automatically in Also by targets.yaml, we are referring to the value of May also be good to add filter_name to metadata / filename? |
Not necessary, that code has been there a while. There just needs to be a filterwheel configuration in the camera config. |
@danjampro and @AnthonyHorton how is this Issue in relation to the work that has been done? |
Modify POCS to accommodate Filterwheels.
Describe the solution you'd like
Here are the tasks for prepping a camera for a filterwheel:
filter_wheel.config
, for each filterwheel require a filter_wheel configure to have adefault_filter_name
taht will be used if someone doesn't speicifyfilter_name
intargets.yaml
Here are the tasks for prepping a single observation of a target:
target.yaml
each target can have an optionalfilter_name
key/name that specifies the desired filter for a targettarget.yaml
parser to accommodate thefilter_name
key.scheduler.observation.Observation
.camera.take_observation
, iffilter_name
was specified and iffilter_wheel_exists=True
, then runcamera.move_to(filter_name)
Related Issues/PRs
If there are any related Issues or PRs list them here:
Depends on: #940
The text was updated successfully, but these errors were encountered: