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

Editing ticket for Getting Started Tutorial set

    XMLWordPrintable

    Details

      Description

      This ticket follows DM-10637, the addition of a Getting Started tutorial series based on DMTN-023, and is a means for reviewing that work before it is merged.

      Draft content root: https://pipelines.lsst.io/v/DM-11391/getting-started/index.html

        Attachments

          Issue Links

            Activity

            Hide
            jsick Jonathan Sick added a comment -

            Here's the new review ticket for the Getting Started tutorial series. Thanks Lauren MacArthur!

            Show
            jsick Jonathan Sick added a comment - Here's the new review ticket for the Getting Started tutorial series. Thanks Lauren MacArthur !
            Hide
            lauren Lauren MacArthur added a comment -

            This looks great. I've put many comments on the PR...feel free to ignore the purely stylistic ones as you see fit. I do wonder about the plan the various "FIXME"s as some of them do seem like show-stoppers.

            Show
            lauren Lauren MacArthur added a comment - This looks great. I've put many comments on the PR...feel free to ignore the purely stylistic ones as you see fit. I do wonder about the plan the various "FIXME"s as some of them do seem like show-stoppers.
            Hide
            jsick Jonathan Sick added a comment -

            Thanks for your comments Lauren MacArthur. I think one of the big sticking points is the Butler repo setup.

            Regarding the FIXMEs, I'm starting to wonder if, for the sake of a "Getting started" tutorial. if it might be better to provide the reader with a ready-to-go Butler repo (everything is pre-ingested) so that we can avoid a bunch of these issues? Of course, we'll have to provide another tutorial on repo setup and provide Butler documentation in general, but setting up a repo might be too advanced for an initial encounter with the stack (this tutorial series doesn't have to be everything for everyone).

            Show
            jsick Jonathan Sick added a comment - Thanks for your comments Lauren MacArthur . I think one of the big sticking points is the Butler repo setup. Regarding the FIXMEs, I'm starting to wonder if, for the sake of a "Getting started" tutorial. if it might be better to provide the reader with a ready-to-go Butler repo (everything is pre-ingested) so that we can avoid a bunch of these issues? Of course, we'll have to provide another tutorial on repo setup and provide Butler documentation in general, but setting up a repo might be too advanced for an initial encounter with the stack (this tutorial series doesn't have to be everything for everyone).
            Hide
            lauren Lauren MacArthur added a comment -

            If the user doesn't know how to set up a proper repo following this tutorial, you had better remove your final comment;

            By now you’re ready to start experimenting with the LSST Science Pipelines for your own projects.

            !

            Show
            lauren Lauren MacArthur added a comment - If the user doesn't know how to set up a proper repo following this tutorial, you had better remove your final comment; By now you’re ready to start experimenting with the LSST Science Pipelines for your own projects. !
            Hide
            jbosch Jim Bosch added a comment -

            DM-12450 and DM-12531 (implementing RFC-407 and RFC-409) involve a pretty major behavioral change in how command-line tasks behave w.r.t. existing data products and existing configuration/schemas/versions. I've updated DMTN-023 accordingly (on tickets/DM-12531), but didn't actually see the old behavior described here at all - I think that just means it was out of scope for this document, and will be worked into some other new long-term home on another ticket. Please let me know if that's incorrect.

            Show
            jbosch Jim Bosch added a comment - DM-12450 and DM-12531 (implementing RFC-407 and RFC-409 ) involve a pretty major behavioral change in how command-line tasks behave w.r.t. existing data products and existing configuration/schemas/versions. I've updated DMTN-023 accordingly (on tickets/ DM-12531 ), but didn't actually see the old behavior described here at all - I think that just means it was out of scope for this document, and will be worked into some other new long-term home on another ticket. Please let me know if that's incorrect.
            Hide
            jsick Jonathan Sick added a comment -

            Thanks for the very helpful comments Lauren MacArthur!

            Show
            jsick Jonathan Sick added a comment - Thanks for the very helpful comments Lauren MacArthur !

              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.