Date: Thu, 28 Mar 2024 11:19:52 +0000 (UTC) Message-ID: <1337102920.18973.1711624798003@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_18972_444329715.1711624792982" ------=_Part_18972_444329715.1711624792982 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The LSST Data Management System Science Team (SST) supp= orts the DM Subsystem Scientist (as the overall Product Owner) in ensuring that Data Mana= gement Organization's initiatives provide solutions that meet the overall L= SST scientific goals. Members of the SST work together to define, maintain,= and communicate to the DM construction team a coherent vision of the LSST = DM system responsive to the overall LSST Project goals. The SST also d= evises and undertakes initiatives to scientifically validate the DMS implem= entation.
SST membership comprises:
SST Ex-Officio
The primary roles of Institutional Science Leads a= re to serve as the Product Owners for parts of the system their respective = institutions have been tasked to deliver. The System Science Analys= ts (Staff) generally lead and/or execute studies needed to support= SST work. The DM Science Validation Scientist organizes a= nd coordinates the Science Validation efforts (data challenges, other = test exercises). The Science Pipelines and Platform Scientists serve as the architects of those two elements of the system, and = broadly advise on topics related to the impact of science pipelines/platfor= m on delivered science and vice versa. These roles are defined in the = DM Organization Document (LDM-294). SST ex-officio membe= rs
Please see the = DM-Community Communications page.
This is the SST Confluence page. It's only accessible to logged in Confl= uence users (i.e., restricted to lsst-co= nfluence-users group). The short link to this page is http://ls= .st/sst.
DM SST business is generally conducted via the dm-sst@lists.= lsst.org mailing list.
Any JIRA issue (typically RFCs, DMs, and LITs) of interest to the SST ca= n be labeled with the 'dm-sst' label. Within the Data Management project on= JIRA, issues that are the responsibility of DM Science Team should be assi= gned to the 'DM Science' team. The union of the two can be viewed using&nbs= p;Issues tracked by the DM System Science Team= a> filter in JIRA, or on the associated Kanban board= .
DM SST Slack channel is #dm-sst; however, it's use is discouraged for anything other than messages not meant to be permanent (i.e., passin= g a link to someone, or communicating in real-time during meetings). There = is no expectation that any of the SST members should follow or read (catch = up) with the discussion on #dm-sst.
The SST as a whole meets every week, via BlueJeans vide= o (https://bluejeans.com/103664856, 10:00am PT, every Friday= , with the first meeting being on 24 March 2017). SST Meetings are cha= ired by the DM Subsystem Scientist. Meeting minutes are posted on the = DM Science T= eam meeting minutes page, and short-term (to be done until the next mee= ting) actions recorded as Confluence tasks (see http://ls.st/jnv for yo= ur personal list of open tasks). The meetings are not closed, but they are = intended as working meetings of the team to which others will be specifical= ly invited as relevant topics arise on the team's agenda. The LSST Project = Scientist will frequently attend the meetings of the SST.
Subteams within the SST (e.g., the, Science Validation Team, or SST= Staff Meetings) may have additional meetings and gather on a different cad= ence.
DM SST work (e.g., data for studies, document sources) should go to repo= sitories in https://github.com/lsst-dmsst, unless a more a= ppropriate place exists for it.
Final results (written-up study repor= ts) should be issued as DM Technical Notes (DMTNs) whenever appropriate. To= facilitate the issuing of DMTNs, study reports should be kept in a reposit= ory separate from the repository with study data or code (e.g., DMTN reposi= tories need to be kept in the lsst-dm github organization). The reference t= o the repository with study materials should be incorporated into the techn= ical note via the git submodule mechanism.= span>
All reports need to be added to Collection-5401 in Docushare, unless they've been publi= shed as DMTNs. If they were published as DMTNs, a Docushare URL object shou= ld be added to point to the relevant DMTN. Per project policy, documents should be added to Docushare by e-mai= ling them to Robert McKercher (the= LSST Project Librarian). Docushare group =E2=80=9CDM System Science Team" = also exists to grant/restrict access to DM-SST documents, as needed. <= /span>
Presentations given in SST roles need= to be uploaded to a sub-collection in Collection-107. Per project policy, have them added by e-mailing Robert McKercher (the LSST Project Librarian). For pr= esentations in meetings with significant DM presence, upload to a sub-colle= ction with the name of the meeting (or ask one to be created). For one-off = presentations (e.g., on telecons to project bodies, or Science Collaboratio= ns), use Collection-5712 ("DMSST Presentations").
SS= T-driven studies published as papers are generally subject to the rules of = the LSST Publication Policy. When publishing, co-authorship and comments= from LSST Builders (see Section 5 of the Publication Policy) need to be so= licited.
Description | Due date | Assignee | Task appears on= |
---|---|---|---|
|
28 Feb 2022 | Robert Lupton | 2018-11-05 DM SST F2F Agenda and= Meeting notes |
|
26 Oct 2021 | Leanne Guy | 2021-08-31 Scienc= e Metric Development Agenda and Meeting notes |
|
Keith Bechtol | 2021-09-14 Scien= ce Metric Development Agenda and Meeting notes | |
|
Keith Bechtol | 2021-09-14 Scienc= e Metric Development Agenda and Meeting notes | |
|
19 Oct 2021 | Leanne Guy | 2021-09-28 Scienc= e Metric Development Agenda and Meeting notes |
|
30 Nov 2021 | 2021-11-09 Scienc= e Metric Development Agenda and Meeting notes | |
|
31 Mar 2022 | Gregory Dubois-Felsmann | 2022-02-14 DM-SST Virtual= F2F Agenda and Meeting notes |
|
Jeffrey Carlin | 2022-04-19 Scienc= e Metric Development Agenda and Meeting notes | |
|
Colin Slater | 2022-04-19 Scienc= e Metric Development Agenda and Meeting notes | |
|
28 Feb 2023 | Leanne Guy | 2023-01-23 DM-SST Agenda and Meeting = Notes |
|
31 Jul 2023 | Eli Rykoff | 2023-01-30 DM-SST Agenda and Meeting = Notes |
|
31 Aug 2023 | Jim Bosch | 2023-02-27 DM-SST Agenda and Meeting = Notes |
|
31 Mar 2023 | Jim Bosch | 2023-02-27 DM-SST Agenda and Meeting = Notes |
|
20 Mar 2023 | Leanne Guy | 2023-02-27 DM-SST Agenda and Meeting = Notes |
|
02 Jun 2023 | Leanne Guy | 2023-03-27 DM-SST Agenda and Meeting = Notes |
30 Jun 2023 | Parker Fagrelius | 2023-03-27 DM-SST Agenda and Meeting = Notes | |
|
29 May 2023 | Leanne Guy | 2023-05-01 DM-SST Foc= us Meeting - Brokers in Commissioning |
|
26 Jun 2023 | Jim Bosch | 2023-05-08 DM-SST Agenda and Meeting = Notes |
|
31 Jul 2023 | Colin Slater | 2023-07-10 DM-SST Agenda and Meeting = Notes |
|
28 Aug 2023 | Yusra AlSayyad | 2023-08-14 DM-SST Agenda and Meeting = Notes |
Key | Summary | Created | Updated | Assignee | P | Status |
---|