Closed jeanconn closed 1 year ago
What's the use case? For approved products I'd go straight to the FOT MP approved_loads area.
I don't understand your approved loads use case. My use case is sparkles.yoshi to start which now has hard-coded aimpoints for convenience that I fear I'll forget to update.
You can get the zero offset aimpoint for an obsid from the ORlist for approved loads. But I now see the issue.
What about a cron job that copies the current /data/mpcrit1 file once a day and makes it accessible at https://cxc.cfa.harvard.edu/mta/ASPECT/drift/zero_offset_aimpoints.txt. I don't think those numbers are sensitive and so they can be on a public server. That way we don't need to add yet another Ska data that needs to be synced.
Sure, a public web copy would also work. Would that need a chandra_aca task schedule or just an entry in the cron task wiki and a comment in chandra_aca?
Isolated cron task doing an rsync and a comment in the code would be fine. Probably once a week is actually plenty, considering the current change frequency.
Can we just add the zero offset aimpoint table to ska data?
chandra_aca.drift.get_default_zero_offset_table could then try local disk, then icxc, then ska data.
It is annoying to need to be on head or on vpn to get the table.