Conversation
dmsci.tex
Outdated
| The DM Scientist has the ultimate responsibility for ensuring DM initiatives provide solutions that meet the overall LSST science goals. | ||
| As such, this person leads the definition and understanding of the science goals and deliverables of the LSST Data Management and is accountable for communicating these to the DM engineering teams. | ||
|
|
||
| The DM Scientist reports to the Rubin Director / |
There was a problem hiding this comment.
Reporting to the Rubin Director would put the DM Scientist on the same level as the AD for DM: is this intended, or should the DM Scientist report to the Associate Director for Data Management? May need discussion.
There was a problem hiding this comment.
Agree - this is not a role that should report to the Director. There is a conflict of interest though in reporting to the AD. I would suggest that the DM lead scientist reports to the LSST lead scientist, with the ADs reporting to the Director.
Similarly, the DM Scientist does not need to be in the operations exec
| The DM Scientist is a member of the DM and Rubin Change Control Boards and the Rubin Operations Science Team. | ||
| He/she chairs and directs the work of the DM Science Team. | ||
|
|
||
| Specific responsibilities and authorities include: |
There was a problem hiding this comment.
Maybe the text above this line could go in the formal role description, and the specifics below just live in this Mgmt Plan?
There was a problem hiding this comment.
The role above has been updated. I think now that this remains here.
| {3.1d.3}&{Data Services Oversight}&{Oversees the SQuaRE and Advanced Databases Teams, functionally supervising the leaders of those teams and reporting on their activity to the AD for RDM. } \\ \hline | ||
| {3.1d.4}&{Data Acquisition Oversight}&{Oversees the SQuaRE and Advanced Databases Teams, functionally supervising the leaders of those teams and reporting on their activity to the AD for RDM. } \\ \hline | ||
| {3.1d.5}&{Data Production Oversight - SLAC}&{Oversees the Algorithms and Pipelines and Campaign Management Teams, functionally supervising the leaders of those teams and reporting on their activity to the AD for RDM. } \\ \hline | ||
| {3.1e}&{NCSA Management Support}&{Provide Project support at NCSA for teh NCSA team} \\ \hline |
There was a problem hiding this comment.
| {3.1e}&{NCSA Management Support}&{Provide Project support at NCSA for teh NCSA team} \\ \hline | |
| {3.1e}&{NCSA Management Support}&{Provide Project support at NCSA for the NCSA team} \\ \hline |
tables/mroles.tex
Outdated
| {3.1d.4}&{Data Acquisition Oversight}&{Oversees the SQuaRE and Advanced Databases Teams, functionally supervising the leaders of those teams and reporting on their activity to the AD for RDM. } \\ \hline | ||
| {3.1d.5}&{Data Production Oversight - SLAC}&{Oversees the Algorithms and Pipelines and Campaign Management Teams, functionally supervising the leaders of those teams and reporting on their activity to the AD for RDM. } \\ \hline | ||
| {3.1e}&{NCSA Management Support}&{Provide Project support at NCSA for teh NCSA team} \\ \hline | ||
| {3.1??}&{Data Management Scientist}&{Ensure DM produces fit for purpose products, shepherd papers and investigations} \\ \hline |
There was a problem hiding this comment.
| {3.1??}&{Data Management Scientist}&{Ensure DM produces fit for purpose products, shepherd papers and investigations} \\ \hline | |
| {3.1??}&{Data Management Lead Scientist}&{Leads the understanding and evaluation of DM performance to ensure LSST data products and services enable transformative science, and shepherds key papers and investigations showcasing their potential.} \\ \hline |
dmsci.tex
Outdated
| Leadership and participation in the performance hub/task force is also assumed under this guise. | ||
| This group would provide science-driven prioritization of cross-department activities and global validation, trend analysis, KPI tracking, and anomaly detection based on high-quality deliverables from each department. Provides a forum at which to raise issues and address cross-cutting topics, provide cross-functional coordination, ensuring alignment with Rubin \& LSST science goals. | ||
|
|
||
| \subsection{DM Science Lead} |
There was a problem hiding this comment.
| \subsection{DM Science Lead} | |
| \subsection{DM Lead Scientist} |
dmsci.tex
Outdated
|
|
||
| \subsection{DM Science Lead} | ||
| {\bf to end up in Staffing Sheet roles and then appear in \secref{sec:roles}} | ||
| The DM Scientist has the ultimate responsibility for ensuring DM initiatives provide solutions that meet the overall LSST science goals. |
There was a problem hiding this comment.
| The DM Scientist has the ultimate responsibility for ensuring DM initiatives provide solutions that meet the overall LSST science goals. | |
| The DM Lead Scientist has the ultimate responsibility for ensuring DM initiatives provide solutions that enable transformative science with LSST across all its science drivers. |
| \item Serves as Data Management Liaison as requested by Science Collaborations or agrees delegates. | ||
|
|
||
| \item Defines the science acceptance criteria for DM deliverables (both final and intermediate) and validates that they have been met (Science Validation). | ||
| \item Delegates authority and responsibility as appropriate to institutional Science Leads and other DM science Team. |
There was a problem hiding this comment.
| \item Delegates authority and responsibility as appropriate to institutional Science Leads and other DM science Team. | |
| \item Delegates authority and responsibility as appropriate to other DM Science Leads |
| \item Develops, maintains, and articulates the vision of DM products and services responsive to stakeholder needs. | ||
| \item Communicates the DM System vision to DM stakeholders. Works with the DMAD to communicate and articulate the DM System vision, requirements and especially priorities to the DM team. | ||
| \item Develops and/or evaluates proposed changes to DM deliverables driven by schedule, budget, or other constraints. | ||
| \item Validates the science quality of DM deliverables and the capability of all elements of the DM System to achieve LSST science goalsi with the V\&V team. |
There was a problem hiding this comment.
| \item Validates the science quality of DM deliverables and the capability of all elements of the DM System to achieve LSST science goalsi with the V\&V team. | |
| \item Validates the science quality of DM deliverables and the capability of all elements of the DM System to achieve LSST science goals with the Data Validation team. |
| The DM Scientist is a member of the DM and Rubin Change Control Boards and the Rubin Operations Science Team. | ||
| He/she chairs and directs the work of the DM Science Team. | ||
|
|
||
| Specific responsibilities and authorities include: |
There was a problem hiding this comment.
The role above has been updated. I think now that this remains here.
dmsci.tex
Outdated
| As such, this person leads the definition and understanding of the science goals and deliverables of the LSST Data Management and is accountable for communicating these to the DM engineering teams. | ||
|
|
||
| The DM Scientist reports to the Rubin Director / | ||
| The DM Scientist is a member of the DM and Rubin Change Control Boards and the Rubin Operations Science Team. |
There was a problem hiding this comment.
| The DM Scientist is a member of the DM and Rubin Change Control Boards and the Rubin Operations Science Team. | |
| The DM Lead Scientist is a member of the DM and Rubin Change Control Boards and the Rubin Operations Science Team. |
| {\textbf{Data Production}} & Yusra AlSayyad & & Data Production \\ \hline | ||
| {\textbf{Campaign Management}} & ? & Y (N/ A) & Campaign Management \\ \hline | ||
| {\textbf{Algorithms \& Pipelines}} & Yusra AlSayyad & ? (Jim Bosch) & Algorithms \& Pipelines:In ops our construction POs (JimB+EricB) become our group leads, so PO prob not necessary. \\ \hline | ||
| {\textbf{V\& V}} & Colin Slator & & Verification and Validataion \\ \hline |
There was a problem hiding this comment.
| {\textbf{V\& V}} & Colin Slator & & Verification and Validataion \\ \hline | |
| {\textbf{V\& V}} & Colin Slator & & Data Validation \\ \hline |
| \section{DM Science} \label{sec:dmsci} | ||
| DM-Science Team Led by the DM Scientist would look after DMS science validation, community liaison, optimization of the as-built DMS, new scientific opportunities. | ||
|
|
||
| This would also be the home for cross-functional teams with no dedicated staff as forums at which to raise issues and address cross-cutting topics, ensuring alignment with Rubin \& LSST science goals. |
There was a problem hiding this comment.
| This would also be the home for cross-functional teams with no dedicated staff as forums at which to raise issues and address cross-cutting topics, ensuring alignment with Rubin \& LSST science goals. | |
| The DM Science Team would oversee DM-related science units as they transition from construction to operations, facilitating the integration of their contributions into standard DM operations workflows. | |
| The DM Science Team serves as a forum at which to raise cross-functional topics within DM and ensure alignment with Rubin and LSST science objectives. |
|
|
||
| This would also be the home for cross-functional teams with no dedicated staff as forums at which to raise issues and address cross-cutting topics, ensuring alignment with Rubin \& LSST science goals. | ||
| Leadership and participation in the performance hub/task force is also assumed under this guise. | ||
| This group would provide science-driven prioritization of cross-department activities and global validation, trend analysis, KPI tracking, and anomaly detection based on high-quality deliverables from each department. Provides a forum at which to raise issues and address cross-cutting topics, provide cross-functional coordination, ensuring alignment with Rubin \& LSST science goals. |
There was a problem hiding this comment.
I think the DM Scientist is responsible for doing this for DM - and then raising any issues to the head of Science. The Head of LSST leads the KPIs for the whole system
Co-authored-by: Leanne Guy <5301176+leannep@users.noreply.github.com>
No description provided.