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

Re-work DMTN-023 as a quick start tutorial

    XMLWordPrintable

    Details

      Description

      This ticket covers creating a Getting Started tutorial for pipelines.lsst.io. The aim is to let a person who has never used the pipelines have a hands-on experience with the Stack to understand its patterns and capabilities and develop good feelings for it.

      The best route is to adapt content from https://dmtn-023.lsst.io:

      • Rework as a tutorial, with deeper explanations moved to framework processing context docs.
      • Update the tutorial so that it works.

        Attachments

          Issue Links

          is triggering

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-11391 Editing ticket for Getting Started Tutorial set

          • Done
          relates to

          Bug - A problem which impairs or prevents the functions of the product. DM-10834 CmdLineTask -j multiprocessing hangs with long data ID lists

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-10340 parent repository properties are dropped when loaded via child repositories.

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-11034 Add afw.display getting started tutorial

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-11077 Add Getting Started tutorial about multi-band forced photometry catalog analysis

          • Done

            Activity

            Ascending order - Click to sort in descending order
            7 older comments
            Hide
            Permalink
            jsick Jonathan Sick added a comment - - edited

            OK. I guess I can put this on a user branch for integration? (for what it's worth, combining business accounting with the Git branching has its downsides)

            It would certainly be better to merge this after v14 is out (the tutorial won't be compatible with the 13 or 13.1).

            DM-11077 and DM-11034 are related tickets that add additional tutorial steps. Should I treat those tickets the same way? Close for now and add them to the new review ticket?

            Show
            jsick Jonathan Sick added a comment - - edited OK. I guess I can put this on a user branch for integration? (for what it's worth, combining business accounting with the Git branching has its downsides) It would certainly be better to merge this after v14 is out (the tutorial won't be compatible with the 13 or 13.1). DM-11077 and DM-11034 are related tickets that add additional tutorial steps. Should I treat those tickets the same way? Close for now and add them to the new review ticket?
            Hide
            Permalink
            lauren Lauren MacArthur added a comment -

            For fear of them getting lost, I submitted some preliminary comments on the PR.

            Show
            lauren Lauren MacArthur added a comment - For fear of them getting lost, I submitted some preliminary comments on the PR.
            Hide
            Permalink
            jsick Jonathan Sick added a comment -

            Thanks Lauren MacArthur!

            Show
            jsick Jonathan Sick added a comment - Thanks Lauren MacArthur !
            Hide
            Permalink
            swinbank John Swinbank added a comment -

            Sorry for being slow on getting back to this.

            OK. I guess I can put this on a user branch for integration?

            (for what it's worth, combining business accounting with the Git branching has its downsides)

            I think that's partially true, but you yourself raise another issue here: we don't want to merge to master until after the next release.

            (Actually I'm not sure how that'll work in general — will we tag pipelines_lsst_io at the same time as everything else which makes up the release? And show the version corresponding to the most recent release, rather than master, by default?)

            DM-11077 and DM-11034 are related tickets that add additional tutorial steps. Should I treat those tickets the same way? Close for now and add them to the new review ticket?

            I think the same approach, but maybe making a separate "review" ticket for each one, rather than combining them all into one.

            Thanks for your help with this!

            Show
            swinbank John Swinbank added a comment - Sorry for being slow on getting back to this. OK. I guess I can put this on a user branch for integration? (for what it's worth, combining business accounting with the Git branching has its downsides) I think that's partially true, but you yourself raise another issue here: we don't want to merge to master until after the next release. (Actually I'm not sure how that'll work in general — will we tag pipelines_lsst_io at the same time as everything else which makes up the release? And show the version corresponding to the most recent release, rather than master , by default?) DM-11077 and DM-11034 are related tickets that add additional tutorial steps. Should I treat those tickets the same way? Close for now and add them to the new review ticket? I think the same approach, but maybe making a separate "review" ticket for each one, rather than combining them all into one. Thanks for your help with this!
            Hide
            Permalink
            jsick Jonathan Sick added a comment -

            Closing this ticket out. I've created a new branch and PR with DM-11391 (I didn't go with an integration branch after all; instead DM-11391, DM-11392, and DM-11393 just branch off each other).

            Show
            jsick Jonathan Sick added a comment - Closing this ticket out. I've created a new branch and PR with DM-11391 (I didn't go with an integration branch after all; instead DM-11391 , DM-11392 , and DM-11393 just branch off each other).

              People

              Assignee:
              jsick Jonathan Sick
              Reporter:
              jsick Jonathan Sick
              Reviewers:
              Lauren MacArthur
              Watchers:
              Jim Bosch, John Swinbank, Jonathan Sick, Lauren MacArthur
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.