Closed griffin-h closed 2 years ago
I worked on this today. I created a Candidate
model in the TOM that matches the existing candidates
table in the database. Now when @lund0946's ingestion script adds things to that table, they will be displayed on the TOM. The ingestion script also keeps track of unique targets, but I have not yet figured out how to associate those targets with the Target
objects in the TOM. I want to allow us to add external targets as well, so I don't want to change schema to exactly match the old candidates table. This might require some small edits to the ingestion.
I updated the pipeline (tom_targets
branch) to use the TOM Toolkit's tom_targets_target
table. Just waiting for @lund0946 to figure out the pipeline cleanup issue before merging.
We need to automatically ingest CSS (and eventually 90Prime & Mont4k) candidates from @KerryPaterson's pipeline into the TOM's database. We also need to crossmatch against existing candidates in the database to avoid duplicates between our own telescopes and other public candidates. Then a unique list of candidates should be displayed for scanning and promotion.