You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page emerged from a discussion at the  PDAC meeting in which the proliferation of Science Platform instances, and of planned audiences for them, was discussed and raised some concerns from the development teams.

Among the issues to be considered for each use case and each LSP instance which may satisfy a use case, or several, are:

  1. Requirements for stability from a user perspective
  2. Identity of the intended users (DM / Project / non-Project, etc.)
  3. Need for persistent user environments (e.g., software installations, personal data)
  4. Datasets to be held
  5. Need for Qserv (whether for development or because of the scale of the data to be held)

Use Case perspective

Science Platform integration

Foo

Qserv development and test at scale

Foo

Exposure of large scientifically useful datasets through the Science Platform for user evaluation and feedback

Foo

Interactive environment for LSST DM developers, especially Science Pipelines, successor to ssh-in lsst-dev systems

Foo

Science data quality analysis environment

Foo

Pop-up demonstrations of the LSP to users at workshops, training sessions, etc.

Foo

Commissioning team and other non-DM Project personnel training on LSP and preparation of code for the commissioning era

Foo

Analysis of AuxTel data in 2019

Foo

"Stack Club", DESC, etc. access to the LSST Stack to enable preparation for the science era


Allocated Resources / PMCS perspective

  • No labels