I think it makes sense to add some words to DMS-REQ-0130 listing the products from the aux telescope. Maybe also add an explicit requirement to say that the data from the aux telescope are archived in the same way as camera data and another requirement saying that the data are reduced. I would also like to know what the performance requirements are for the aux telescope pipeline, similar to DMS-REQ-0131.

OSS-REQ-0315 is a bit vague in the sense it says we should take the data because we need it but doesn't bother to say we should reduce it.

Expanding on this general theme, but not specifically the AuxTel:

LSE-61 currently calls out some subset of calibration products and labels them as requirements. In fact, the Calibration Products Production will generate a lot more products than are currently listed. We can claim that almost anything is covered by DMS-REQ-0130 ("The DMS shall produce and archive Calibration Data Products that capture the signature of the telescope, camera and detector"), but for consistency we should either add all of the other CPP products to the DMSR, or remove the subset of products that are currently called out specifically.

At some level, the right way to approach this may be to think of (an updated) LSE-180 as having the same relationship to the DMSR in terms of calibration products as LSE-163 has to the DMSR in terms of science products.

(There's actually some sort of philosophical question here about what it's appropriate to have as a requirement: presumably the real requirements is just that all calibration products required to calibrate the AP and DRP products to at a level which meets the science requirements must be archived. Calling out a bunch of specific calibration products as requirements seems — to first order — unnecessary, except to the extent that they might be required in L3.)

Bringing this to the attention of Leanne Guy and Jeffrey Carlin in case they have also noticed the aux tel data processing absence in LSE-61 as part of the verification work.

Do we want an explicit requirement or do we want an implicit requirement in that it's impossible to calibrate a data release without the AuxTel data so clearly we must be able to process the data. The advantage of a requirement is that it gives us an early win in verification. The disadvantage is the paperwork. Isn't there already a milestone related to this?