Action plan for MicadoWISE usage on Jupyter Hub
This is an umbrella issue to track what is necessary to make most use of our OmegaCEN Jupyter Hub, in particular w.r.t. MICADO.
- Jupyter Hub: https://practicum.astro.rug.nl/
- Instructions to add a user: https://gitlab.astro-wise.org/micado/micadowise/-/wikis/New-user
The main goal is that the MICADO DFS team (e.g. Yixian, Ric) can use the Jupyter Hub to
- simulate data
- commit and store data into the archive
- search and retrieve data from the archive
- process data
- do some simple analysis, like quick look and trend plots
To make this possible we have a multistage approach:
-
Run what we have now: simulate data and process it. -
Retrieve data from the archive #238 (closed) , and process that. -
Store data into the archive. This should work and mainly requires - testing,
- writing down how to set credentials
- actually include it in the notebook, at least optionally
-
Create WISE-recipes for MICADO - preferably this will be a single recipe that can create any data product, like the ProcessTargetRecipe, that just sets dependencies, retrieves data, and calls
make()
- first run this locally
- then on lpu
- then on dpu
- preferably this will be a single recipe that can create any data product, like the ProcessTargetRecipe, that just sets dependencies, retrieves data, and calls
-
Run actual CPL recipes within these recipes. -
Create notebooks for some actual use cases of the MICADO use cases document.