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

Please document the --rerun option

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: pipe_base
    • Labels:
    • Story Points:
      1
    • Epic Link:
    • Sprint:
      DRP F16-1
    • Team:
      Data Release Production

      Description

      DM-3371 adds the --rerun option to command line tasks. The help for this option reads:

      rerun name: sets OUTPUT to ROOT/rerun/OUTPUT; optionally sets ROOT to ROOT/rerun/INPUT

      While essentially correct, that's not particularly helpful in understanding what's actually going on here. A motivation and description of this functionality is available in RFC-95: please ensure that, or some variation of it, is included in the stack documentation.

        Attachments

          Issue Links

            Activity

            Hide
            swinbank John Swinbank added a comment -

            While pipe_base is really a job for Process Middleware, and documentation for SQuaRE, since this is purely debt from the HSC porting effort I suggest we handle this within DRP.

            Show
            swinbank John Swinbank added a comment - While pipe_base is really a job for Process Middleware, and documentation for SQuaRE, since this is purely debt from the HSC porting effort I suggest we handle this within DRP.
            Hide
            vpk24 Vishal Kasliwal [X] (Inactive) added a comment -

            Hi Russell! Can you please review the work done on this ticket? Mostly, it's a summary of RFC-95.

            Show
            vpk24 Vishal Kasliwal [X] (Inactive) added a comment - Hi Russell! Can you please review the work done on this ticket? Mostly, it's a summary of RFC-95 .
            Hide
            rowen Russell Owen added a comment -

            Overall this is nice and clear. The examples are very helpful. I did have some suggestions for improving clarity (on github). I also noted one or two places where LSST policies should be removed from the documentation.

            Show
            rowen Russell Owen added a comment - Overall this is nice and clear. The examples are very helpful. I did have some suggestions for improving clarity (on github). I also noted one or two places where LSST policies should be removed from the documentation.
            Hide
            vpk24 Vishal Kasliwal [X] (Inactive) added a comment -

            Merged to master...

            Show
            vpk24 Vishal Kasliwal [X] (Inactive) added a comment - Merged to master...
            Hide
            vpk24 Vishal Kasliwal [X] (Inactive) added a comment -

            I missed a few comments - sorry! I'll fix them by Thursday.

            Show
            vpk24 Vishal Kasliwal [X] (Inactive) added a comment - I missed a few comments - sorry! I'll fix them by Thursday.

              People

              • Assignee:
                vpk24 Vishal Kasliwal [X] (Inactive)
                Reporter:
                swinbank John Swinbank
                Reviewers:
                Russell Owen
                Watchers:
                John Swinbank, Russell Owen, Vishal Kasliwal [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: