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 described on this page. 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; arXiv:2010.05926).
Guidelines and expectations¶
Understand the RSP Risks and Caveats of using the DP0 RSP on a shared-risk basis.
Abide by the Code of conduct.
Adhere to the Policies for acknowledgments, citations, and publications.
RSP accounts¶
Activation: Delegates will be contacted by Rubin Observatory staff to provide their GitHub username. All delegates will be invited to join the rubin-dp0 GitHub Organization and its Delegates team, and must accept this invitation in order to log into the RSP at the Interim Data Facility (IDF; the Google Cloud). With a browser that is logged in to GitHub, navigate to http://data.lsst.cloud and choose “log in” at upper right. A pop-up window will ask to “Authorize Rubin Science Platform IDF Production Environment”. Click the green button that says “Authorize lsst-sqre”. Note that this last authorization step will need to be performed after every logout.
Policies: RSP accounts are not transferable and delegates must not share their password with others. DP0 delegates are being given access to a shared-risk developmental version of the RSP and the accompanying documentation. Everyone is responsible for their own safe usage of the RSP and must be familiar with this list of RSP Risks and Caveats, 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 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, navigate 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 Observatory 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. People new to the Rubin Community Forum might appreciate this video demonstrating how to navigate and post topics to the forum.
Accounts: Go to http://community.lsst.org and use the “Sign Up” button at upper-right to create an account.
Join the DP0 Delegates Group: Go to https://community.lsst.org/groups and join “DP0 Delegates”. This will ensure you have access to the private “Support - DP0 RSP Service Issues” subcategory.
DP0 kick-off info sessions¶
All delegates should view the recording if they were unable to attend live.
Slides and Recording: ls.st/clo4989
DP0 Delegate assemblies¶
Connection Info (Zoom and Google Calendar Links): ls.st/dp0-events
Time: Biweekly on Fridays from 9am to 11am US Pacific time (alternating with Stack Club; 4pm UTC). See the Assemblies schedule for dates.
The Delegate Assemblies are a live, virtual seminars for DP0 delegates to learn more about DP0, the RSP, and the DC2 data set.
Assemblies with a formal presentation component are split into 2 one-hour sections, and all are welcome to join for only the first or second hour, or both hours. Everyone is welcome to attend, the assemblies are not restricted to delegates.
Everyone is welcome to propose breakout topics for the second hour. The first five minutes of the second hour will be spent connecting people with similar interests and setting up breakout rooms.
Assemblies without a formal presentation component will go straight into breakout rooms. The first five minutes of the assembly will be spent connecting people with similar interests and setting up breakout rooms. Everyone is free to join and leave breakout rooms and to work on whatever they like.
Rubin Observatory staff will always be on hand in the main room to answer questions and provide assistance with DP0-related work during breakouts.
Assemblies schedule¶
Rows in italics are tentative topics. Please reach out to Melissa Graham with suggestions or contributions (e.g., send her a direct message in the Community Forum). Suggestions and contributed talks are welcome from anyone, e.g., delegates, Rubin Observatory staff.
Date (Fridays at 9am US Pacific) |
First Hour Presentation Topic |
Second Hour Breakouts Topics |
Chair and Presenter(s) |
|---|---|---|---|
2021-07-16 |
Introduction to DP0, and to the RSP’s Notebook and Portal Aspects. |
General Q&A. Portal queries Q&A. Python learners. Lightcurves. Large scale structure (LSS). |
The Community Engagement Team (Melissa Graham) |
2021-07-30 |
Querying Catalogs with TAP in the Notebook and Portal Aspects. |
LSS Working Group. Data visualization. General Q&A. Delegate “New Friends”. Single-star lightcurves. |
The Community Engagement Team (Leanne Guy) |
2021-08-13 |
no assembly (Rubin 2021 Project and Community Workshop) |
||
2021-08-27 |
More fun with image display. |
The Community Engagement Team (Jeff Carlin) |
|
2021-09-10 |
More fun with the Butler. General Q&A. Delegate networking. |
The Community Engagement Team (Alex Drlica-Wagner) |
|
2021-09-24 |
Source detection and measurement. Supernovae. Resolved stellar populations. General Q&A. |
Yusra AlSayyad (Rubin Algorithms and Pipelines Team) |
|
2021-10-08 |
Visualization packages Q&A. DP0 science topics. |
Keith Bechtol (Rubin Commissioning Team) |
|
2021-10-22 |
New-to-DP0 tutorial. Supernovae. Large scale structure. Resolved stellar populations. General Q&A. |
The Community Engagement Team |
|
2021-11-05 |
Resolved stellar populations. Large scale strucutre. Extinction in DP0. General Q&A. |
Louise Edwards, Kristen Larson, and the CET |
|
2021-11-19 |
Resolved stellar populations. Large scale strucutre. |
Sylvie Dagoret-Campagne and the CET |
|
2021-12-03 |
Source injection. Deep learning. General Q&A. |
Andrew Bradshaw (Rubin Camera Subsystem Team) |
|
2022-01-14 |
no assembly (AAS) |
||
2022-01-28 |
Large Scale Structure. Variability. Resolved Stellar Populations. General Q&A. |
The Community Engagement Team |
|
2022-02-11 |
general Q&A, resolved stellar pops, welcome new delegates! |
The Community Engagement Team |
|
2022-02-25 |
general Q&A, resolved stellar pops, background subtraction, machine learning with DP0, truth data |
The Community Engagement Team |
|
2022-03-11 |
general Q&A, truth data, photo-z, orientation for new delegates |
The Community Engagement Team |
|
2022-03-25 |
general Q&A, PSFs, resolved stellar pops, photo-z |
Sylvie Dagoret-Campagne and the CET |
|
2022-04-08 |
general Q&A, source injection, resolved stellar pops |
The Community Engagement Team |
|
2022-04-22 |
general Q&A and emergent topics |
The Community Engagement Team |
|
2022-05-06 |
Portal Techniques |
TBD delegate working groups |
Alessandro & Sara, and the CET |
2022-05-20 |
TBD delegate presenter(s) |
TBD delegate working groups |
TBD |
2022-06-03 |
TBD delegate presenter(s) |
TBD delegate working groups |
TBD |
2022-06-17 |
TBD delegate presenter(s) |
TBD delegate working groups |
TBD |
Stack Club¶
Connection Info (Zoom and Google Calendar Links): ls.st/dp0-events
Time: Biweekly on Fridays from 9am to 11am US Pacific time (alternating with Assemblies schedule; 4pm UTC).
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, so Stack Club members create Jupyter Notebook tutorials that feature the Stack. Many of these notebooks were used to create the DP0 tutorial notebooks. Sessions begin with a roundtable of what people want to do or learn that day, and then work proceeds as people stay connected via Zoom, asking questions or having discussions in the main room or breakout rooms.
Rubin Observatory staff are always present to provide support for DP0 and the RSP. DP0 delegates are very welcome to join the Friday Stack Club sessions, whether it’s for the full two hours or just to drop in for a few minutes and ask a question (like an office hour). DP0 delegates do not need to formally join Stack Club unless they want to contribute specifically to the Stack Club’s repository of tutorial notebooks.
Third Thursday office hour¶
Time: Thursdays at 04:00 and 14:00 UTC (to serve the Asia-Pacific, APAC, and Europe, the Middle East, and Africa, EMEA, time zones respectively)
2022 Dates: April 21, May 19, June 16, and July 21
Please see this Rubin Community Forum topic for more information and connection details.
These office hour sessions are open, drop-in discussions designed to compensate for the fact that the time of the Delegate Assemblies was only convenient for DP0 delegates in North and South America, Europe, and Africa. Everyone is welcome to attend any of these sessions, instead of or in addition to the Delegate Assemblies and the Stack Club sessions.
There is no set agenda for these sessions, but Rubin Observatory staff are always in attendance, and topics are left open to attendees. For example, delegates could discuss their DP0-related analysis with Rubin Observatory staff and with each other, review the DP0 RSP tutorials together, collaborate on DP0-related science, and get support from Rubin Observatory staff as needed.
Suggested delegate activities¶
All delegates are invited to take on an activity that will inform and improve development of the RSP 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 RSP¶
Extend or enhance the benefits of DP0 in the science community¶
DP0 Working Groups¶
“DP0 Working Groups” (DP0 WGs) are any collection of DP0 delegates who want to work together on similar DP0-related science or analysis tools.
DP0 WGs are meant to be fairly informal; there are no pre-set DP0 WGs topics, and anyone can propose and coordinate a DP0 WG.
The Rubin Observatory Community Engagement Team (CET) is supporting DP0 WGs by providing Zoom breakout rooms for co-working sessions and a shared repository in the rubin-dp0 GitHub Organization, as described below.
To get your DP0 WG on the list below, or request any other kind of DP0 WG support, please contact Melissa Graham.
When would DP0 WGs meet? Breakout rooms during the second hour of the DP0 Delegate assemblies, or anytime during Stack Club sessions, will be created for any and all who request one. DP0 WGs could also meet any other time they want to, for the convenience of their members.
How would DP0 WGs collaborate?
One way to facilitate collaborative work is to use the delegates’ shared repository in the rubin-dp0 GitHub Organization.
As described in that repository’s README file, simply create a new directory in the repository with an appropriate name (e.g., for a Transients Hosts Galaxies DP0 Working Group, could use “wg-transients-host-galaxies”).
To facilitate collaboration, it is recommended to keep a README file updated with descriptions of the directory’s contents.
Can I start a DP0 WG by myself? Yes! In time, other delegates might join your efforts, and remember that more delegates will be joining for DP0.2 next year.
How can I advertise a DP0 WG? Make a new topic in the Community Forum’s Data Preview 0 category titled, e.g., “Invitation to Join the Transient Host Galaxies DP0 Working Group”. If applicable, describe some of the groups potential activities, link to the relevant folder in the shared GitHub repository, and/or say when and where the tag-ups will be.
Current working groups and their contact info:
Working Group |
Contact |
|---|---|
Fabio Ragosta |
|
Bernardita Ried Guachalla |
Getting support¶
Several venues are provided to support DP0 delegates, as described below. There is no wrong place to post questions or requests for assistance! Hearing about issues and receiving feedback from delegates is a key component of DP0.
Scientific support via the Community Forum¶
The Support – Data Preview 0 subcategory is the best place for DP0 delegates to post topics related to scientific support.
Scientific support includes questions about the DC2 simulated data set, the DP0 data products, and/or the application of the LSST Science Pipelines to the DP0 data set, as well as general discussion about DP0-related scientific analyses, or DP0 policies and guidelines.
This subcategory will be monitored by the Rubin Observatory Community Engagement Team (CET). DP0 delegates are especially encouraged to post new topics and reply to others’ posts in this subcategory.
Technical assistance via GitHub issues¶
Bug reports, persistent technical issues, and requests for assistance from Rubin Observatory staff should be submitted by DP0 delegates as GitHub issues in the rubin-dp0 GitHub Organization’s Support repository. Requests for new features or for global installations of commonly used software packages are also welcome via GitHub issues.
In the horizontal menu bar at the top of that page, click on the “Issues” option (with the circled dot icon), then choose the green “New Issue” button at right. Next to either “Bug report” or “Feature request” choose “Get started” (as appropriate for your case), and fill in the title and contents of your issue. In the right side-menu, do adjust the labels as appropriate, but leave the other options. Click “Submit new issue” when you’re ready. These issues will be addressed by Rubin Observatory staff.
Minor or ambiguous RSP service and access issues¶
Please feel free post even small questions as new topics in the “Support - DP0 RSP Service Issues” private subcategory of the Community Forum.
This subcategory enables DP0 delegates to determine if others are experiencing the same issue (e.g., “is this local or general network outage?”, “my query is taking a long time, is this a real problem or did I do it wrong?”), crowd-source solutions to technical issues from each other when possible, and have a non-public venue for DP0-related questions. Updates about commonly experienced access issues or planned service outages will be posted by Rubin Observatory staff in this category.
Since the “DP0 RSP Service Issues” subcategory is not public, it cannot be linked to directly, but anyone who is logged in to the Community Forum can access it via the main landing page at community.lsst.org.
Read more in the Community Forum about Scientific Support and Technical Assistance for DP0 Delegates.
Live support¶
Bring your questions to the Delegate Assemblies, third Thursday office hours, or Stack Club meetings. Rubin Observatory staff members will usually be in attendance and able to assist you.
Code of conduct¶
Please review the Rubin Code of Conduct (CoC) at ls.st/comms-coc.
If you experience or witness a violation of the CoC in the Community Forum, please flag the post. Forum moderators will handle the issue from there. Please note that there are a few reasons why posts get flagged, and CoC violations are only one of them. Here are some guidelines on how to react if your post is flagged.
If you experience or witness a violation of the CoC in another venue, please reach out to Sandrine Thomas, one of the Rubin Observatory Workplace Culture Advocates who has agreed to be the contact person for DP0 Delegates. Please also feel free to reach out to any Community Engagement Team member at any time: Melissa Graham, Jeff Carlin, Greg Madejski, Jim Annis, Alex Drlica-Wagner, or Tina Adair. All can be contacted by email or via direct message in the Community Forum.
Policies for acknowledgments, citations, and publications¶
Cite the DESC’s publications for the DC2 simulated data set, which is being used for DP0. If you publish work based on the DP0 data set, you must cite “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) if you used the Object or Truth-Match tables, which are presented in that release note.
Consider extending co-authorship or acknowledgments to DP0 delegates whose work you used, or who have helped you, as appropriate. Delegates are encouraged to openly share their DP0-related work and/or code during DP0 Delegate assemblies, via the Community Forum, within DP0 Working Groups, and in the shared GitHub repository delegate-contributions-dp01. This is intended to facilitate collaboration, which requires proper acknowledgments. For example, if you use another delegate’s Jupyter Notebook as a starting point for your Notebook, give credit to that person at the top of your Notebook. If another delegate’s work contributed to your DP0-related publication, consider including an acknowledgment, citing their relevant publications, and/or extending co-authorship, as appropriate.
Be aware that DP0-related work done by Science Collaboration (SC) members might be subject to the publication policies of their Science Collaborations. Significant overlap between the DP0 working groups and SC working groups, committees, or task forces is to be expected, because the science goals of DP0 and the SCs overlap (i.e., preparing for LSST). Each SC has their own policies regarding collaboration, co-authorship, and publications and delegates are responsible for following the policies of their SCs, if and when they pertain to their DP0-related work. If cases of real or perceived conflict between the general open nature of DP0 collaboration and any SC policies arise, delegates are expected to understand and abide by their SC’s policies. In other words, the fact that work is DP0-related does not nullify any SC policies that might apply to a delegate’s work. Example scenarios might include sharing SC-developed software with delegates who are not members of that SC, or using code or analysis results collaboratively by delegates in a SC publication.
Note that the Rubin Observatory Publication Policy does not apply to publications by delegates that are based on their DP0 work.