SP-1758: Update RTN-002: user profiles, analysis use cases, and support use cases #5
Conversation
Abstract, authors, intro, and doc structure.
There was a problem hiding this comment.
The biggest changes needed are to the analysis use cases for the RSP, IDACs, and brokers. They've gone too far into describing specific science use cases, and need to be generic and focused on analysis tools (RSP functionality). In some cases, the use case does not fit the RSP aspect (is not possible). There are a bunch of individual comments that try to provide more guidance. Apologies SP-1758 maybe did not quite provide adequate guidance here... it does say "focus on science and functionality" and maybe I should have said "think about science and write about functionality". I didn't want to make direct edits today, but, I suspect I'm still not clear on the vision here -- if more examples would be helpful I'll make a patch branch no problem. Just let me know.
And then there remain issues in Section 4... in SP-1758 "continue to update the support use cases to the new template" - I think that just got missed.
| @@ -43,6 +43,8 @@ | |||
| \setDocChangeRecord{% | |||
| \addtohist{1}{2021-03-05}{Released.}{Melissa Graham} | |||
| \addtohist{2}{2023-04-19}{Add user profiles.}{Andrés A. Plazas Malagón} | |||
| \addtohist{3}{2024-12-01}{Reorganize document (SP-1758).}{Melissa Graham} | |||
| \addtohist{3}{2025-01-21}{Reorganize document (SP-1758).}{Andrés A. Plazas Malagón} | |||
There was a problem hiding this comment.
Just one line for version 3, like this.
\addtohist{3}{2025-01-21}{Reorganize document (SP-1758).}{Melissa Graham, Andrés A. Plazas Malagón}
|
|
||
| \textbf{Description:} | ||
| An unsupervised student user (or ``unaccompanied undergraduate") might be trying | ||
| to get their own research experience on their own; perhaps they were unable to find |
There was a problem hiding this comment.
Fix awkward wording "to get their own research experience on their own".
| They are working on an analysis for a well-defined project that will yield publishable results. | ||
|
|
||
| \textbf{Experience:} | ||
| A few too many astronomy courses at the upper-undergrad and graduate levels. |
There was a problem hiding this comment.
Fix awkward wording "A few too many", could do "A few to many" but "At least a few" is probably clearer.
| \subsection{Integrated Aspects} | ||
| \input{up_integrated_aspects.tex} | ||
| These analysis use cases represent general things that users want to do in the Rubin Science Platform, | ||
| using specific scientific examples. |
There was a problem hiding this comment.
The analysis use case need to represent general things users want to do in the RSP, and should roughly match with existing or planned functionality. It's ok in some cases to have a "for example, " but these currently read much more like science use cases and generic analysis use cases -- too specific. I'd like to scale them back to generic analysis.
What we don't want is for users (or UC/SAC) to see this and assume our understanding of science use cases is very narrow and get worried about that.
I'll make a few examples but if you could review and generic-ify all analysis use cases.
|
|
||
| \textbf{P-101}: User interface cone search on the object catalog, review the results overplotted on the HIPS map. | ||
|
|
||
| \textbf{P-102}: Astronomical Data Query Language (ADQL) cone search on the object catalog with magnitude constraints, create a color-magnitude diagram in the results view. |
There was a problem hiding this comment.
Astronomical Data Query Language (ADQL) search with column constraints, and creating plots based on the retrieved data in the results view.
| @@ -0,0 +1,8 @@ | |||
| \textbf{I-201} Retrieve PSF cutouts from coadd images (e.g., using the Notebook Aspect of the RSP) to derive parameters of PSF models. | |||
There was a problem hiding this comment.
Rewrite to focus on GPU, the IDAC aspect. This IDAC use-case starts with using the RSP, which is confusing.
| \textbf{I-201} Retrieve PSF cutouts from coadd images (e.g., using the Notebook Aspect of the RSP) to derive parameters of PSF models. | ||
| Use these parameters to train machine-learning-based algorithms for galaxy classification using GPU resources at IDACs. | ||
|
|
||
| \textbf{I-202}: Find galaxy clusters in LSST data using Rubin APIs and notebooks for exploratory analysis. |
There was a problem hiding this comment.
For a NERSC-based case the IDAC functionality is high-performance compute and co-located datasets. Focus on that. Don't say "download the data" b/c that is not something an individual user should be doing.
| @@ -0,0 +1,8 @@ | |||
| \textbf{B-201} Identify Tidal Disruption Events (TDEs) and extreme AGN by constructing long-term light curves from difference images using forced photometry. | |||
There was a problem hiding this comment.
These are again too specific. The things brokers offer that the RSP doesn't is real-time streaming and filters, LC classification, watchlists notifications, etc. Focus on that functionality. I can help here.
|
|
||
| \clearpage | ||
| \section{Use Cases} | ||
| \section{Support Use Cases} |
There was a problem hiding this comment.
Section 4.2 and later appear boldface, need to fix.
|
|
||
| \clearpage | ||
| \section{Use Cases} | ||
| \section{Support Use Cases} |
There was a problem hiding this comment.
Section 4.4 and later have not been updated to the new template.
No description provided.