You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once Postgres is up and running at CSD3, we need to copy some of the data stored in the Postgres registry database at NERSC into the new Postgres database running at CSD3.
Steps for rebuilding the roman-desc-sims data repository at CSD3:
Generate export yaml files from /repo/roman-desc-sims at NERSC using a special export script in which the data transfer functionality is disabled (since we have already copied those data by hand to CSD3) and copy those yaml files to CSD3.
Re-organize the folders at CSD3 containing the transferred data, replicating the directory structure of /repo/roman-desc-sims at NERSC.
Create a new data repository at CSD3, with butler create, nominally using the postgres db.
Ingest calibration products, refcats, and skymaps.
Import the registry info for the transferred data into the CSD3 repo, using a special import script so that the prepared repo directory structure can be used as-is.
Rebuild the chained collections.
Run test queries and test pipelines.
I've already done all of these steps for small test repos using sqlite3 at NERSC and at CSD3. I will put copies of the final export and import scripts in this github repo, for the record.
Once Postgres is up and running at CSD3, we need to copy some of the data stored in the Postgres registry database at NERSC into the new Postgres database running at CSD3.
Jim started a discussion about the technical details on Slack #dm-middleware-support.
The text was updated successfully, but these errors were encountered: