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

DM-26550: Add support for ObservationInfo.observation_reason #248

Merged
merged 1 commit into from Sep 4, 2020

Conversation

timj
Copy link
Member

@timj timj commented Aug 31, 2020

This allows TESTTYPE handling to be unified.

Requires lsst/astro_metadata_translator#40

Copy link
Member

@RobertLuptonTheGood RobertLuptonTheGood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that the test observation_reasons are very realistic, but as long as no-one cargo cults them that's OK.

@@ -24,8 +24,7 @@

config.parse.retarget(LatissParseTask)

del config.parse.translation['testType']

del config.parse.translators['testType']
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this white-space only change?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not a whitespace only change.

@timj
Copy link
Member Author

timj commented Sep 3, 2020

I don't think I can do anything other than believe the value of the TESTTYPE header can I? Garbage in and garbage out. If you think that TESTTYPE=bias could be translated to something else then I'm happy to tweak the translation here.

@RobertLuptonTheGood
Copy link
Member

Tim explained that the test code was using real TESTTYPE values, so my comment is wrong. Good to merge

This allows TESTTYPE handling to be unified.
@timj timj merged commit 0e15625 into master Sep 4, 2020
@timj timj deleted the tickets/DM-26550 branch September 4, 2020 17:03
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.

None yet

2 participants