DP0 Delegate Homepage¶
This page includes the guidelines, resources, and activities for DP0 Delegates.
“DP0 delegate” is the term for the 300 scientists and students who will have accounts in the Rubin Science Platform (RSP) at the Interim Data Facility (IDF) during Data Preview 0 (DP0). This term has been adopted to reflect DP0 participants’ important roles of representing the broad science community as learners, testers, and providers of feedback, and of sharing the benefits of their DP0 participation with their communities as teachers and colleagues. Delegates’ DP0-related activities will be supported with resources and infrastructure (as described below). The simulated data set being used for DP0 was created by the Dark Energy Science Collaboration (DESC) as part of their second Data Challenge (DC2).
RSP Accounts¶
Activation: Delegates will be contacted by Rubin staff to provide their GitHub username. They will then be invited to join the rubin-dp0 GitHub Organization, and upon accepting the invitiation, will be able to log into the RSP at the IDF at http://data.lsst.cloud.
Policies: RSP accounts are not transferrable and delegates must not share their password with others. DP0 delegates are being given access to a shared-risk developmental version of the Rubin Science Platform and the accompanying documentation. Everyone is responsible for their own safe usage of the RSP and must be familiar with this list of RSP Usage Risks, and review the Guidelines and Expectations for DP0 delegates.
Deactivation: Delegates who are no longer using their accounts and would like to relinquish it to make way for others should please submit a GitHub issue in the rubin-dp0 GitHub Organization to let us know, and then leave the rubin-dp0 GitHub Organization. (Log into GitHub, navitate to https://github.com/settings/organizations, and click on the “Leave” button for the rubin-dp0 Organization.)
For delegates who need to get a GitHub account: go to http://www.github.com and select “sign up” in the upper right corner. For participation in DP0 it is not necessary to learn how to use git as a version control system, nor any of the git workflows or command line tools. GitHub will not be used for RSP accounts during Rubin Operations, this is a DP0-specific implementation.
Rubin Community Forum¶
The Rubin Community Forum is the central hub for all virtual discussions and support. It is the best place to post your questions about anything and everything related to DP0.
Accounts: Go to http://community.lsst.org and use the “sign up” button at upper right to create an account (unless you have one already).
Join the DP0 Delegates Group: Go to https://community.lsst.org/groups and join “DP0 Delegates”. This will ensure you have access to the the “Support – DP0 RSP Services Issues” (PLACEHOLDER for a link) category.
DP0 Kick-Off Info Sessions¶
All delegates should please attend one of these identical sessions. One of them will be recorded and made available.
Connection Info: ls.st/clo4989
DP0 Delegate Assemblies¶
Virtual meetings that occur biweekly on Fridays from 9am to 11am Pacific time (alternating with Stack Club) for DP0 delegates from North and South America and Europe, plus a Third Thursday Office Hour for live interaction for DP0 delegates from timezones in Australia and Asia (but all are welcome to attend this session).
Connection Info: (PLACEHOLDER for a link to connection info)
All are welcome to attend these assemblies, as they are not restricted to delegates. All are welcome to join for only the first or second hour, or both hours.
Assemblies Schedule¶
Date (Fridays at 9am US Pacific) |
First Hour Presentation Topic |
Second Hour Breakouts Topics |
Chair and Presenter(s) |
|---|---|---|---|
2021-07-16 |
The Rubin Vision and Roadmap for Data Preview 0 |
Demo “Intro to Jupyter Notebooks (NB) and DP0”. Q&A for delegates with NB experience. |
The Community Engagement Team (Melissa Graham) |
2021-07-30 |
Querying Catalogs via the Notebook (TAP Service) and Portal Aspects. |
Notebook Q&A. Portal Q&A. DP0 science. |
The Community Engagement Team (Leanne Guy) |
2021-08-13 |
no assembly (Rubin 2021 Project and Community Workshop) |
||
2021-08-27 |
Image Query, Retrieval, and Display. |
Butler Q&A. Notebook Q&A. Image type Q&A. DP0 science. |
The Community Engagement Team (Jeff Carlin) |
2021-09-10 |
Data Discovery with the Butler and the Portal |
Butler Q&A. Portal Aspect Q&A. DP0 science. |
The Community Engagement Team (Alex Drlica-Wagner) |
2021-09-24 |
LSST Science Pipelines |
Pipeline Q&A. DP0 science. |
TBD |
2021-10-08 |
Data Visualization |
Data vis package Q&A. DP0 science. |
TBD |
2021-10-22 |
Image Processing |
Image algorithms Q&A. DP0 science. |
TBD |
2021-11-05 |
Source Detection and Measurement |
Measurement algorithm Q&A. DP0 science. |
TBD |
2021-11-19 |
Fake Source Injection |
Fake source Q&A. DP0 science. |
TBD |
2021-12-03 |
delegate presenter(s) |
delegate working groups |
TBD |
2022-01-14 |
delegate presenter(s) |
delegate working groups |
TBD |
2022-01-28 |
Special Session on DP0.1: A Half-Year In Review |
small group discussions for delegate feedback |
The Community Engagement Team |
2022+, if desired |
delegate presenter(s) |
delegate working groups |
TBD |
Third Thursday Office Hour¶
A DP0 office hour aimed to be “time-zone - friendly” for the Australia and Asia - based delegates will be on the third Thursday of every month at 8am Tokyo / 9am Sydney (e.g., Wed 4pm in US Pacific Daylight Time). This will be open time for DP0 delegates to drop in, discuss their DP0-related activities with Rubin staff and with each other, and get support if needed.
Connection Info: (PLACEHOLDER for a link to connection info)
More dates will be added to continue these office hours if they are useful to DP0 delegates in Australia and Asia.
Stack Club¶
Stack Club is a group of LSST Science Collaboration members committed to learning how to use the Rubin Observatory LSST Science Pipelines (colloquially called “the Stack”). The idea is that the best way to learn something is to try and teach it, and so they work collectively on creating useful tutorials featuring the Stack. Many of the DP0 Delegate Assemblies presentations will be based on tutorials developed by the Stack Club. On alternating Fridays, Stack Club meets for an open hack session. Stack Club members use the NCSA implementation of the RSP, where they also have access to the DC2 data set.
DP0 delegates are welcome to join one or more Science Collaborations and to join the Friday Stack Club Zoom sessions. (DP0 delegates do not need to formally join Stack Club unless they want to contribute to Stack Club tutorial notebooks). Stack Club meetings start with a roundtable of what people want to do or learn that day, and then work proceeds as people stay connected via Zoom, with the occasional question or discussion happening. Sometimes breakout rooms are used to discuss emergent topics. Often times Rubin Data Management staff join to provide support. (NOTE WE NEED TO MENTION THAT THE DELEGATES WILL NOT AUTOMATICALLY GET AN NCSA ACCT BUT THEY CAN STILL LISTEN-IN AND WORK ON THEIR OWN NOTEBOOKS AT THE IDF.)
Connection Info: (PLACEHOLDER for a link to connection info)
Guidelines and Expectations¶
Understand the shared-risk basis of DP0 RSP use. Delegates are responsible for their own safe usage of the RSP and must be familiar with this list of RSP Usage Risks
Abide by the code of conduct. All delegates are expected to abide by the LSST Communications Code of Conduct.
Use appropriate acknowledgements and citations. If you publish work enabled by DP0, the RSP, and/or the DESC’s DC2 data set, please include: “CosmoDC2: A Synthetic Sky Catalog for Dark Energy Science with LSST” Korytov et al (2019), “The LSST DESC DC2 Simulated Sky Survey” (arXiv:2010.05926), and potentially “DESC DC2 Data Release Note” (arXiv:2101.04855), especially if you used the Object or Truth-Match tables presented in that release note. (PLACEHOLDER for additional papers and acknowledgments).
Choose a delegate activity. Delegates are invited to take on an activity that helps to maximize the impact of DP0 with respect to the DP0 goals of testing and informing development of the RSP and preparing the scientific community to do LSST science. See Suggested Delegate Activities.
Interact with your co-delegates. Participate in the Rubin Community Forum and join the biweekly DP0 Delegate Assemblies as often as you can. (SUGGESTED TEXT: ALL ASSEMBLIES WILL BE ATTENDED BY THE COMMUNITY ENGAGEMENT TEAM MEMBER, WHO MIGHT BE ABE TO FACILITATE CO-WORKING WITH OTHER DELEGATES IN A BREAKOUT ROOM.).
Use your RSP account! As there are a limited number of RSP accounts for DP0, please try to make some use of your account and learn to use at least one aspect of the RSP. There is no minimum time that you’re expected to spend on DP0. If you find that you are done with DP0, consider relinquishing your account so it can be offered to someone else.
Suggested Delegate Activities¶
All delegates are invited to take on an activity that will inform and improve development of the Rubin Science Platform development, and/or extend and enhance the benefits of DP0 within the science community, beyond the limited number of DP0 participants that Rubin Observatory is able to support.
Delegate activities are envisioned to be simple and enjoyable. They are completely voluntary and will not be tracked. Group work is encouraged, as are delegate-designed activities.
Inform and improve the Rubin Science Platform¶
rubin-dp0 GitHub Organization (PLACEHOLDER for link to rubin-dp0 issues repo)Extend or enhance the benefits of DP0 in the science community.¶
(COMMENT BY GM: SHOULD WE ENCOURAGE THE DELEGATES TO SIGN UP AND PARTICIPATE IN THE PCW?)
Getting Support¶
GitHub Issues: (PLACEHOLDER for a link and instructions and example)
Rubin Community Forum: Post new topics in the Data Preview 0 category for all questions related to DP0 science, i.e., the application of the LSST science pipelines or the RSP’s analysis tools to the DC2 data set. Post new topics in the “DP0 RSP Services Issues” (PLACEHOLDER for a link) for minor questions related to RSP service or access issues (but please do not hesitate to submit GitHub issues).
Live Support: Bring your questions to the Friday delegate assemblies, third Thursday office hours, or Stack Club meetings and perhaps someone there will be able to assist you.