Related to issue #6 --
It may also make sense if there's a LVM-Instrument configuration database which lists all the components, versions, and any interventions (cleaning, realignment, etc...). This issue isn't a "bug" but rather a much bigger subproject and perhaps even a scope change. That way, there's an element in the FITS header that has a link to a database ID entry.
Related to issue #6 --
It may also make sense if there's a LVM-Instrument configuration database which lists all the components, versions, and any interventions (cleaning, realignment, etc...). This issue isn't a "bug" but rather a much bigger subproject and perhaps even a scope change. That way, there's an element in the FITS header that has a link to a database ID entry.