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

Silence missing filter name warning for dark observations #1072

Closed
wants to merge 3 commits into from

Conversation

danjampro
Copy link
Collaborator

  • Currently a logger call at info level is made when an observation is taken without a filter specified (filter_name=None).
  • Dark observations do not know which filter_name corresponds to the dark position for each camera, so filter_name=None is always (and necessarily) specified.
  • New behaviour is to log a warning if the observation is not dark and the filter is not None

@danjampro danjampro requested review from wtgee and fergusL January 27, 2021 03:57
@danjampro danjampro changed the title first Silence missing filter name warning for dark observations Jan 27, 2021
@codecov
Copy link

codecov bot commented Jan 27, 2021

Codecov Report

Merging #1072 (9e8b53d) into develop (cb4d26e) will increase coverage by 0.03%.
The diff coverage is 80.00%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #1072      +/-   ##
===========================================
+ Coverage    84.76%   84.79%   +0.03%     
===========================================
  Files           77       77              
  Lines         6531     6532       +1     
  Branches       560      561       +1     
===========================================
+ Hits          5536     5539       +3     
+ Misses         836      834       -2     
  Partials       159      159              
Impacted Files Coverage Δ
src/panoptes/pocs/camera/camera.py 83.48% <80.00%> (+0.50%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cb4d26e...9e8b53d. Read the comment docs.

@wtgee
Copy link
Member

wtgee commented Jan 29, 2021

@danjampro I still think it might be a good time to bring the BiasObservation and DarkObservation into POCS itself, which would clean this up a bit as we wouldn't have to pass around the dark flag (which I just don't like for some reason).

Any reason we couldn't move most of this PR here? AstroHuntsman/huntsman-pocs#332

wtgee added a commit that referenced this pull request Jan 31, 2021
Following changes in `panoptes-utils`, this cleans up and simplifies the Docker services.

## Description

* **Breaking change** Python 3.8
* **Breaking change** Default service install does not include ``focuser`` dependencies.
* **Breaking change** Default Docker command is a ``ipython`` console with the simulators loaded.
* **Breaking change** Docker image only contains limited set of files.
* **Breaking change** Directories inside the service image have been simplified for easier mapping onto desired targets on the host. The main top-level directory (i.e. ``$PANDIR``) is now ``/POCS`` with other folders nested underneath.
* **Breaking change** Removing ``peas`` scripts.
* Simple example script for creating a ``POCS`` instance with all simulators.
* Using ``threading.excepthook`` to log errors in camera exposure threads. Addresses some of #1047.
* Updated install script (includes ZSH again).
* Pointing state is skipped if `num_pointing_images==0`.
* Images use ``gcr.io/panoptes-exp/panoptes-utils`` as base.
* Docker files are all contained within ``docker`` folder.
* Docker image has tycho2 10-19 index files for plate-solving.
* Docker services (``config-server`` and ``pocs-control``) are started in ``global`` mode so there can be only one.
* Config changed to run with simulators out of the box.
* Removing old scripts and config files.
* Simplify testing service by removing ``tests/env`` file.
* The default ``radius`` for solving images is 15°. 

## Related Issue
Needed by #1071, #1072
@danjampro
Copy link
Collaborator Author

Closing in favour of #1069

@danjampro danjampro closed this Feb 1, 2021
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

Successfully merging this pull request may close these issues.

2 participants