Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-6722

ingestCalibs doesn't respect calib repo path

    Details

      Description

      Ingesting calib files with e.g.

      ingestCalibs.py /path/to/repo/ --calibType <any> /path/to/fits/file/*.fits --validity 999
      

      will put the calib repo (i.e. calibRegistry.sqlite3) wherever the ingest command was executed, rather than adding this to the calib repo which lies in the path specified.

        Attachments

          Issue Links

            Activity

            Hide
            mfisherlevine Merlin Fisher-Levine added a comment -

            This may be a more widespread problem than I initially reported, seems like regular ingest also doesn't always respect paths either, and possibly processCcd as well, will post details soon...

            Show
            mfisherlevine Merlin Fisher-Levine added a comment - This may be a more widespread problem than I initially reported, seems like regular ingest also doesn't always respect paths either, and possibly processCcd as well, will post details soon...
            Hide
            hchiang2 Hsin-Fang Chiang added a comment - - edited

            Try:

            ingestCalibs.py /path/to/repo/ --calibType <any> /path/to/fits/file/*.fits --validity 999 --calib /path/to/calib/repo/
            

            (i.e. using the --calib command-line argument)

            Looking at this commit the behavior you described sounds correct.

            Show
            hchiang2 Hsin-Fang Chiang added a comment - - edited Try: ingestCalibs.py /path/to/repo/ --calibType <any> /path/to/fits/file/*.fits --validity 999 --calib /path/to/calib/repo/ (i.e. using the --calib command-line argument) Looking at this commit the behavior you described sounds correct.
            Hide
            mschmitz Morgan Schmitz added a comment -

            Merlin Fisher-Levine we're going through some old open tickets. Do you happen to remember if Hsin-Fang's fix worked, and if not, assuming this is no longer an issue, is it okay to mark as Won't Fix?

            Show
            mschmitz Morgan Schmitz added a comment - Merlin Fisher-Levine we're going through some old open tickets. Do you happen to remember if Hsin-Fang's fix worked, and if not, assuming this is no longer an issue, is it okay to mark as Won't Fix?
            Hide
            mfisherlevine Merlin Fisher-Levine added a comment -

            Ummm, yeah, this feels like ancient history. There are still some slightly weird idiosyncrasies around this, like having to manually create the calib directory, but given this is almost certainly all Gen2 stuff, I think that's further evidence to mark it as Won't Fix.

            Show
            mfisherlevine Merlin Fisher-Levine added a comment - Ummm, yeah, this feels like ancient history. There are still some slightly weird idiosyncrasies around this, like having to manually create the calib directory, but given this is almost certainly all Gen2 stuff, I think that's further evidence to mark it as Won't Fix.

              People

              • Assignee:
                Unassigned
                Reporter:
                mfisherlevine Merlin Fisher-Levine
                Watchers:
                Hsin-Fang Chiang, John Swinbank, Merlin Fisher-Levine, Morgan Schmitz
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel