Wilfred Tyler Gee
Wilfred Tyler Gee
This is an umbrella issue for a number of things that can change with the horizon constraints: - [ ] Account for entire Field of View #383 - [ ]...
The `take_observation` command has some coupling between the camera and the observation that should be removed. See discussion here: https://github.com/panoptes/POCS/pull/642#discussion_r221471935
* [ ] Add lots of documentation to config file to explain options. * [x] ~~Rely on config file instead of env vars (#555).~~ * [ ] Ability to override...
One way to clean this up a bit (and make it more flexible) would be to offload these mappings to a `header_mappings.yaml` file. Same goes for `_process_exposure`. _Originally posted by...
Similar to the `observe`, `analyze_recent`, and `update_tracking`, the bulk of the logic for the pointing state should be moved outside of the state itself and into the observatory.
We should do a thorough review of the timestamp entries that are going into FITS headers as well as the timestamped file name. We should also have a single source...
If separation is largely than some threshold after `num_pointing_images` then the system should **not** proceed but should shut down. _Originally posted by @wtgee in https://github.com/panoptes/POCS/pull/894/review_comment/create_
We currently plate-solve each image and do a comparison with the pointing image in order to determine the x and y pixel offsets that are used for tracking correction. This...
In general the `create_mount_from_config` will need to handle specific cases that are different for each driver/model. Original comment regarding mount: ``` # TODO(jamessynge): We should move the driver specific validation...
The various `create__from_config` scripts are currently also capable of creating a "simulator" version of the hardware. To me that seems non-logical as creating from config should necessarily be creating real...