Skip to content

Commit

Permalink
Merge pull request #11 from lsst/PREOPS-3621
Browse files Browse the repository at this point in the history
Preops 3621
  • Loading branch information
MelissaGraham committed Oct 26, 2023
2 parents c36fb4c + 0ce9f6c commit b57eb06
Showing 1 changed file with 9 additions and 6 deletions.
15 changes: 9 additions & 6 deletions RDO-051.tex
Expand Up @@ -39,6 +39,7 @@
\addtohist{1.2}{2022-02-09}{Version 1.2. Clarified meeting attendance.}{Melissa Graham, Michael Strauss}
\addtohist{1.3}{2023-02-22}{Version 1.3. Update name of CST.}{Melissa Graham}
\addtohist{1.4}{2023-09-30}{Version 1.4. PREOPS-1058.}{Melissa Graham}
\addtohist{1.5}{2023-10-17}{Version 1.5. PREOPS-3621.}{Greg Madejski}
}

\begin{document}
Expand All @@ -49,7 +50,7 @@
The Rubin Community Science team (CST) will be seeking regular feedback from the science user community on the quality of the data products and the efficacy of the RSP throughout the lifetime of the LSST.
The Rubin Users Committee is charged both with soliciting this feedback from the community, and actively using the LSST data and the RSP.
Users Committee members may also participate in User Acceptance Testing for the RSP under the guidance of the CST.
The Users Committee will regularly report to the Rubin Lead Community Scientist and to the Rubin Observatory Director with recommendations for science-driven improvements to the LSST data products and the RSP tools and services.
The Users Committee will regularly (typically twice a year) report to the Rubin Lead Community Scientist and to the Rubin Observatory Director with recommendations for science-driven improvements to the LSST data products and the RSP tools and services.
Their goal is to maximize the scientific productivity of the user community, while prioritizing equitable access and inclusive practices throughout the diverse user community.

The Users Committee will be a standing committee in place by February 2022, and will continue through the life of Rubin Observatory operations.
Expand Down Expand Up @@ -82,10 +83,10 @@ \section{Committee Membership}
The Chair is the principal point of contact with the CST.
The CST and Users Committee Chair together will arrange meetings of the committee.
The Chair will ensure that the minutes of the meetings are prepared and posted publicly\footnote{
Minutes and reports should be posted in the Rubin Community Forum, in the Science category with the tag \#users-committee.}.
Minutes and reports should be posted in the Rubin Community Forum, in the Science category at \url{https://community.lsst.org/tag/users-committee} with the tag \#users-committee.}.
The Chair of the Users Committee shall also serve as an ex officio member of the Users Committee of the National Optical-Infrared Astronomical Research Laboratory (NOIRLab).

Individuals may be nominated for membership on the Users Committee by filling out a form (see Appendix \ref{sec:apA}) and e-mailing it to the Chair of the Rubin Observatory SAC.
Individuals may be nominated for membership on the Users Committee by filling out a form (see Appendix \ref{sec:apA}) - including explicitly your area of expertise - and e-mailing it to the Chair of the Rubin Observatory SAC.
Self-nominations are encouraged.
Once a year the CST will provide a list of which Users Committee members are rolling off the committee and must be replaced and which are available to serve another year.
The SAC will review the list of nominations and put forward a slate to the Operations Director, who will then approve the list.
Expand All @@ -99,6 +100,7 @@ \section{Committee Activities}
These can be held virtually or face-to-face (with virtual conferencing enabled for those unable to travel).
A natural venue for a face-to-face meeting would be in coordination with the annual Rubin Observatory
Project and Community Workshop (PCW).
If the PCW is held as a purely virtual meeting, the Committee might meet in person or virtually, upon an agreement between the CST lead and the UC chair.

Meetings shall be open to all members of the Rubin users community and all Rubin staff, but the members of the
Users Committee can call for closed executive sessions as needed.
Expand Down Expand Up @@ -156,12 +158,13 @@ \section{Rubin Support for the Users Committee}
\item arranging and hosting meetings,
\item seeking Rubin expertise on technical issues that may arise,
\item providing tutorials for the Committee regarding new features,
\item developing an on-line portal for comments from the community,
\item developing an on-line portal for comments from the community (the Rubin Community Forum),
\item organizing surveys or polls for community feedback at the request of the Committee,
\item and suggesting timely topics for the Committee’s consideration.
\end{itemize}

Travel funding for 12 people in support of at least one of the two yearly meetings being face-to-face are included in the non-labor costs of the Community Science team.
Travel funding for 12 people in support of at least one of the two yearly meetings being face-to-face are included in the non-labor costs of the Community Science team.
When a meeting takes place during the Rubin PCW, the funding covers the entire duration of the PCW.
Virtual attendance will be an option for all meetings.
While service on the Users Committee is not currently a paid position, the work done on the Committee is a vital and significant contribution to the operations of Rubin Observatory, and will be recognized as such by the Rubin leadership.

Expand All @@ -182,7 +185,7 @@ \section{Nomination Form}\label{sec:apA}
\item Nominated by (if not a self-nomination).
\item Career stage that best describes the nominee for the next two years (e.g., graduate student; postdoctoral researcher; research staff scientists / engineer; junior / senior / emeritus professor).
\item Science Collaborations (if any) the nominee is a member of.
\item Nominee’s Rubin-related science interests (up to one paragraph).
\item Nominee’s Rubin-related science interests and specific area of expertise (up to one paragraph).
\item Nominee’s experience with the Rubin Science Platform or LSST Science Pipelines; their relevant experience with the Rubin Observatory data products and services such as Data Preview 0 or Stack Club; their unique perspective (e.g., junior researcher, historically underrepresented in astronomy); and/or their technical experience with relevant precursor surveys such as, e.g., HSC, KIDS, or DES (up to one page).
\end{enumerate}

Expand Down

0 comments on commit b57eb06

Please sign in to comment.