add a TAP query to populate_ossuary to populate iq_elixir

[mtbannister]

so the homebrew IQ and the elixir IQ can be compared if there's any concern over validation philosophies.

[ijiraq]

Where will 'iq_elixir' come from? Is that something that TAP provides?

[mtbannister]

Hmm. There was a way to access the elixir-processed files that showed Elixir's image quality (or fwhm, same thing) value. I thought it was from selecting in http://www.cadc.hia.nrc.gc.ca/AdvancedSearch/ but now I don't see the field given there.

[ijiraq]

OK. Looking in the EXPNUMo.head files I see some keywords that might be helpful:

DDSEEMEN= 0.76 / Dome DIMM mean seeing, arc seconds
DDSEEMED= 0.72 / Dome DIMM median seeing, arc seconds
DDSEEMOD= 0.67 / Dome DIMM mode seeing, arc seconds
DDSEESTD= 0.11 / Dome DIMM seeing deviation, arc seconds

SPOZPMEN= 0.70 / SkyProbe (orig) mean absorption, magnitude
SPOZPMED= 0.67 / SkyProbe (orig) median absorption, magnitude
SPOZPMOD= 0.66 / SkyProbe (orig) mode absorption, magnitude
SPOZPSTD= 0.06 / SkyProbe (orig) absorption deviation, magnitude

I don't know how useful the SPOZP values are.. they appear to indicate lots of adsorption, but IIRC, those values are not zeropointed correctly (are relative to some value where 0.0 is NOT zero extinction). But the seeing values are likely representative of the floor on those values. For the above image .fwhm on ccd22 is 0.78''

[ijiraq]

@mtbannister: Is this now closed?

[mtbannister]

not yet, it was low priority.

On 28/06/2013, at 10:15 , JJ Kavelaars wrote:

@mtbannister: Is this now closed?

—
Reply to this email directly or view it on GitHub.