We need a mechanism to change ledger entries. This should use an "override" ledger that can be read in an automated fashion, not just for the real data, but also for the alternate MTL ledgers. The "override" ledger should be consulted as part of the end-to-end MTL loop.
The prototype case will be to force z~5, visually inspected QSOs to always be re-observed. But, we should code this up with the expectation of more general cases.
A critical detail is that if a target's state has not yet been updated in the ledger, it should not be altered. Otherwise the alternate MTL ledgers will be updated to include targets that haven't yet been observed in that alternate realization.
geordie666
commented
3 years ago
We need a mechanism to change ledger entries. This should use an "override" ledger that can be read in an automated fashion, not just for the real data, but also for the alternate MTL ledgers. The "override" ledger should be consulted as part of the end-to-end MTL loop.
The prototype case will be to force z~5, visually inspected QSOs to always be re-observed. But, we should code this up with the expectation of more general cases.
A critical detail is that if a target's state has not yet been updated in the ledger, it should not be altered. Otherwise the alternate MTL ledgers will be updated to include targets that haven't yet been observed in that alternate realization.