New feature: When executing --get-from-DB, update the existing csv automatically with new events
What to do
(see title)
Benefit
Directly updating the existing .csv
would make a manual comparison of old and new .csv
files obsolete and updating a scan more straightforward, less time-consuming, and less error-prone (no need to take over new events in the old csv, or taking over all previous events in the new csv, respectively).
Plan of attack
Need a new method that, after calling TM.io.readCatalogSEDDB()
in xcorr.py, processes the two catalog files (.csv.old
and .csv
) accordingly (as one would do manually).
For safety / reproducibility, backup both original files by renaming them (before writing the new one):
- the
*.csv
:*-%Y-%m-%d-DB.csv
(this is the new untouched DB query) - the
*.csv.old
:*-%Y-%m-%d.csv
(this is the former reference catalog with all flags)
(with %Y-%m-%d
being the date when the respective file was created/modified).