Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Karabo Integration into MMODA #545

Open
Lukas113 opened this issue Feb 22, 2024 · 4 comments
Open

Karabo Integration into MMODA #545

Lukas113 opened this issue Feb 22, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request prio-high High priority

Comments

@Lukas113
Copy link
Collaborator

Lukas113 commented Feb 22, 2024

After iterating with the MMODA team, we have evaluated the following use-case:

Demo from Sky to dirty-image on their backend renkulab, with the according MMODA template for input and output parameters. Configurable must be the most important parameters like sky-sources, observation-time, phase-center, which telescope, field of view. To what extend they must be configurable is unclear atm (e.g. sky-sources). The following things need to be considered:

  • Freedom of choice for configurable parameters?
  • How can we ensure that these configurations don't have memory, resource and time-issues?
  • MMODA interface of the defined parameters?
  • How do we provide and ensure input parameter dependencies (E.g. frequency-channels on a survey)?
  • What about reproducibility and maintenance? Different Karabo-versions (breaking API), different dependency-resolving (rebuilding of environment), how much do we have to care for CSCS object storage backwards-compatibility?

That's my understanding of how we proceed from our last meeting with MMODA on Feb22. @lmachadopolettivalle and @anawas were also part of the meeting. Feel free to add or change something.

@Lukas113 Lukas113 added enhancement New feature or request prio-high High priority labels Feb 22, 2024
@Lukas113 Lukas113 self-assigned this Feb 22, 2024
@lmachadopolettivalle
Copy link
Collaborator

Looks correct to me, thank you for the write-up @Lukas113. We agreed on starting with a MVP that has one or a few default sky models, fields to input key observation parameters (pointing phasecentre, frequency channels, observation length...), and a dropdown with a few telescope configurations (SKA-MID, SKA-LOW, MeerKAT). The demo should go from the sky model to visibilities and dirty images, and output the dirty images generated by the pipeline. We will meet again with the MMODA team in 2 weeks to reassess our progress.

@Lukas113
Copy link
Collaborator Author

@sfiruch I think we should create an i4ds (or Karabo?) group on renkulab for repository-management.

@sfiruch
Copy link
Member

sfiruch commented Mar 4, 2024

@sfiruch I think we should create an i4ds (or Karabo?) group on renkulab for repository-management.

Yeah, that sounds reasonable. Can you create one for Karabo? Ideally the project wouldn't be I4DS/FHNW-specific. (Somewhat tangential: I also thought that we should move all Karabo repos into a Karabo GH org)

@Lukas113
Copy link
Collaborator Author

The initial setup is done on karabo-dirty-image-sim repository. I wasn't able to a Karabo or i4ds group, because the MMODA-bot needs the repository to live in the astronomy/mmoda group. So you have to request access to the repository if you want to contribute. The most important information about how MMODA is working can be found in their dev-guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request prio-high High priority
Projects
None yet
Development

No branches or pull requests

3 participants