Details

    • Type: RFC
    • Status: Implemented
    • Resolution: Done
    • Component/s: DM
    • Labels:
      None

      Description

      For the JDR/JSR I woudl like to reissue LDM-294.

      There are updates to Org charts, glossary, 3rd party software, risk management, milestones.

      Document can be found at https://ldm-294.lsst.io/v/RFC-621/index.html

        Attachments

          Issue Links

            Activity

            Hide
            swinbank John Swinbank added a comment -

            Further PR at https://github.com/lsst/LDM-294/pull/79 addresses problems with the glossary (ensuring it gets built by Travis; ensuring that all entries get properly recursively expanded; fixing formatting issues).

            Show
            swinbank John Swinbank added a comment - Further PR at https://github.com/lsst/LDM-294/pull/79 addresses problems with the glossary (ensuring it gets built by Travis; ensuring that all entries get properly recursively expanded; fixing formatting issues).
            Hide
            swinbank John Swinbank added a comment -

            Thank you Gabriele Comoretto — that summary is very helpful! A couple of comments:

            • I believe that what you are calling “Calibration Software” is actually software for generating calibration products, not software for performing calibration. I think it would be more helpful if the name reflected that. (I notice, though, that this is also an issue in LDM-148 and apparently I didn't complain about it there, so maybe we should approve this for consistency and file a new ticket to fix it later.)
            • Can we tighten up the definition of “plugin”? Do you mean this to refer to all meas_extensions_ packages, or everything which provides a meas_base-style measurement plugin, or something else? I'm not sure I understand why it's meaningful to distinguish these plugins from the rest of “Sci Pipelines Libs” — can you explain?

            Thanks again!

            Show
            swinbank John Swinbank added a comment - Thank you Gabriele Comoretto — that summary is very helpful! A couple of comments: I believe that what you are calling “Calibration Software” is actually software for generating calibration products, not software for performing calibration. I think it would be more helpful if the name reflected that. (I notice, though, that this is also an issue in LDM-148 and apparently I didn't complain about it there, so maybe we should approve this for consistency and file a new ticket to fix it later.) Can we tighten up the definition of “plugin”? Do you mean this to refer to all meas_extensions_ packages, or everything which provides a meas_base-style measurement plugin, or something else? I'm not sure I understand why it's meaningful to distinguish these plugins from the rest of “Sci Pipelines Libs” — can you explain? Thanks again!
            Hide
            swinbank John Swinbank added a comment -

            Adopting this so we can baseline the updated document for upcoming review: it's a clear step forward compared to what was there before.

            I would like to revisit the design of the product tree; I'm a little bit worried that this RFC is effectively bouncing some immature thinking there into the baseline. I'll ticket that work to be done after we have the review out of the way.

            Show
            swinbank John Swinbank added a comment - Adopting this so we can baseline the updated document for upcoming review: it's a clear step forward compared to what was there before. I would like to revisit the design of the product tree; I'm a little bit worried that this RFC is effectively bouncing some immature thinking there into the baseline. I'll ticket that work to be done after we have the review out of the way.
            Show
            womullan Wil O'Mullane added a comment - v3.8   https://docushare.lsstcorp.org/docushare/dsweb/Get/Version-60624/LDM-294.pdf
            Hide
            ktl Kian-Tat Lim added a comment -

            Yes, "Calibration Software" is for generating calibration products. There was a general desire to keep names short, but adding "Products" to the name would be reasonable (while something like "Products Generation" might be less desirable).

            The distinction between Science Pipelines Libraries and Plugins is that the former are part of every release and distribution; it was thought that various combinations of the latter may be released or distributed, and they might be released independently of the Libraries. Plugins, in my mind, include things like meas_ and obs_ packages that fulfill more-or-less-defined interfaces to general frameworks. In theory, all Tasks could be considered plugins, but most seem so fundamental that there's no reason to split them out.

            Show
            ktl Kian-Tat Lim added a comment - Yes, "Calibration Software" is for generating calibration products. There was a general desire to keep names short, but adding "Products" to the name would be reasonable (while something like "Products Generation" might be less desirable). The distinction between Science Pipelines Libraries and Plugins is that the former are part of every release and distribution; it was thought that various combinations of the latter may be released or distributed, and they might be released independently of the Libraries. Plugins, in my mind, include things like meas_ and obs_ packages that fulfill more-or-less-defined interfaces to general frameworks. In theory, all Tasks could be considered plugins, but most seem so fundamental that there's no reason to split them out.

              People

              • Assignee:
                womullan Wil O'Mullane
                Reporter:
                womullan Wil O'Mullane
                Watchers:
                Gabriele Comoretto, John Swinbank, Kian-Tat Lim, Wil O'Mullane
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Planned End:

                  Summary Panel