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

Tickets/dm 5988 #1

Merged
merged 6 commits into from May 16, 2016
Merged

Tickets/dm 5988 #1

merged 6 commits into from May 16, 2016

Conversation

SimonKrughoff
Copy link
Contributor

No description provided.

@@ -3,10 +3,34 @@
# Configs to get going.
config.isr.doDark=False
config.isr.doBias=False
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Don't we have darks and biases now? If so, should we turn these on to avoid accidentally running without those corrections?

@PaulPrice PaulPrice force-pushed the tickets/DM-5988 branch 2 times, most recently from ecf756d to eca94c4 Compare May 10, 2016 15:25
When observing at the Naval Observatory, the camera is not talking to the
telescope and so the FITS headers aren't populated. Instead, additional
FITS files are being generated for the shutter with the headers in them.
Unfortunately, there's not a clear one-to-one correspondence between these
two sources.

In order to get some useful header keywords for the image data, we suck
the useful header keywords into a sqlite database. This can be used to
experiment with joining the two sets of files and, with a join strategy,
apply the shutter header values to the camera during ingest and read.

The choice of name comes from being a bit annoyed at the hoops I was
having to jump through, and not wanting to use the word "ingest"
because of the potential for confusion with ingestImages and ingestCalibs.
So it ended up being "suckMetadata.py" because it sucks.
Ingesting USNO data requires a hack because the image data and the useful
FITS headers are separated.
These config overrides allowed me to process an observation made at USNO.
We use a smallish-scale background model to avoid detections in the wings
of stars. We increase the detection threshold (5-->20 sigma) because
there's more noise in the images than we are accounting for. We use
astrometry.net for the astrometric solution.
These may be hot pixels, but we don't yet have reliable darks.
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