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

getmag: marking files as bad --> marked as upper limits #56

Open
abostroem opened this issue Aug 20, 2020 · 0 comments
Open

getmag: marking files as bad --> marked as upper limits #56

abostroem opened this issue Aug 20, 2020 · 0 comments
Labels

Comments

@abostroem
Copy link
Collaborator

When I run
lscloop.py -n 2020pzn -e 20200727 -s getmag --type mag --show
and click on the g-band point and then use 'b' to mark it as bad instead is prints:

 dateobs         jd        mag    dmag  telescope filter magtype
---------- ------------- ------- ------ --------- ------ -------
2020-07-28 2459058.56066 18.8988 0.0275    1m0-12      B       1
2020-07-28 2459058.56530 18.7559 0.0147    1m0-12      g      -1
2020-07-28 2459058.56996 19.0887 0.0402    1m0-12      i       1

and when I check on the status of the file

lscloop.py -n 2020pzn -e 20200727

The file still appears, showing that the quality has not been set from 127 --> 1 (in contrast marking as bad at the checkpsf stage explicitly prints that its updating the quality from 127 --> 1)

@abostroem abostroem added the bug label Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant