systematic plan for mock transients
caseyjlaw opened this issue · comments
We have the ability to simulate transients, but do not regularly use it in real-time observing. It would be valuable to implement an end-to-end plan for adding, finding, and tracking mock transients as a regular check of data quality.
Starting to sketch this out. Basic idea:
- Create database for saving parameters inserted into data.
- Insert transient randomly into data with range of physical characteristics to allow statistical measurement of detection efficiency with DM, dt, and phase offset.
- Run detection pipeline blindly and save all candidates, real and mock.
- Compare candidates to mock database after detection as veto before getting excited.
- Could optionally use a pseudo-random process to define input parameters. This would allow us to identify mock transients even if the mock database lookup fails.