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

Review for pipe_tasks in DM-2939: modernize astrometry interfaces #15

Merged
merged 8 commits into from Aug 12, 2015

Conversation

TallJimbo
Copy link
Member

No description provided.

astrometer = pexConfig.ConfigurableField(
target = measAstrom.AstrometryTask,
doc = "astrometry task; used to match sources to reference objects, but not to fit a WCS",
)
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 looks like you're touching all the places where the astrometry subtask is used here; could we rename it at the same time to astrometry for consistency?

There are also other places we use astrometer, which I'd also like to change; I prefer just calling the subtask astrometry, since we tend to name other tasks after the "act of doing something" (e.g. measurement) not "a thing that does something" (measurer).

Copy link
Contributor

Choose a reason for hiding this comment

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

OK. Done in pipe_tasks, and that exposed one instance where I had failed to update an interface. obs_subaru has an instance of a class that has an astrometer subtask and an astrometry method; that will take some thought.

Copy link
Member Author

Choose a reason for hiding this comment

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

Do recall what class that was? I think now obs_subaru is now integrated into the stack enough we should at least just consider changing it here.

Copy link
Contributor

Choose a reason for hiding this comment

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

It's for using hscAstrom instead of meas_astrom. That shouldn't be necessary any more. Don't worry about it. If we need it for HSC, I'll work around you.

Copy link
Contributor

Choose a reason for hiding this comment

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

The task in question is SubaruAstrometryTask and is still present on master. I think it does require need updating because some of the code it used from meas_algorithms changed. For example SubaruAstrometryTask is a subtask of what was AstrometryTask but became ANetAstrometryTask. I have updated it on tickets/DM-2939. I removed the term "astrometer" at the same time (it was a very minor change).

ImageDifferenceTask used outdated code to find reference objects
that overlap an exposure and match them to sources.
I updated the code to use the modern astrometry task API.
I improved the documentation of two values returned by
CalibrateTask.run.
MeasureMergedCoaddSourcesTask now calls the astrometry tasks's
run method instead of assuming it has an astrometer which has
a useKnownWcs method.
For consistency rename a local variable astrometer to astrometry
in ProcessImageTask
ImageDifferenceTask had a workaround for the fact that our
tan-sip fitter used to fail if CRPIX was large. That's been fixed,
so I removed the workaround and managed to eliminate use of
a hard-coded astrometry task at the same time.
@r-owen r-owen merged commit b282cf6 into master Aug 12, 2015
@ktlim ktlim deleted the tickets/DM-2939 branch August 25, 2018 06:45
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

3 participants