International Virtual Observatory Alliance

Difference: InterOpJune2025DSP (9 vs. 10)

Revision 102025-06-02 - SaraBertocco

META TOPICPARENT	name="InterOpJune2025"

<-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

~~---+ DSP Sessions:~~ ---+ DSP Session: 4th June 2025 9:00-10:30 ---+ 4th June 2025 9:00-10:30

5th Jun 11:00-12:30

Location	Time
Washington DC, USA	Wed, 4 Jun 2025 at 09:00 EDT
UTC, Time Zone	Wed, 4 Jun 2025 at 13:00
Catania, Italy	Wed, 4 Jun 2025 at 15:00 CEST
Bristol, United Kingdom	Wed, 4 Jun 2025 at 14:00 BST
Beijing, China	Wed, 4 Jun 2025 at 21:00 CST
Paris, France	Wed, 4 Jun 2025 at 15:00 CEST
Perth, Australia	Wed, 4 Jun 2025 at 21:00 AWST
Victoria, Canada	Wed, 4 Jun 2025 at 06:00 PDT

Deleted:

<
<

[ back to main programme page]

Added:

>
>

Thusday June 4 2025 9:00-10:30, Room: room 2309

Back to main progamme page: InterOpJune202

Moderator: Sara Bertocco

Wednesday June 4 @09:00 CEST: Room
Speaker	Title	Time	Abstract	Material
Dave Morris (Remote)	Execution Broker Update	15' 9:00-9:15	The IVOA Execution Broker Working Draft represents a key step toward standardising how astronomical workflows and computational tasks are managed and executed across distributed infrastructures. This talk will provide an update on the current status of the draft specification, outlining its core concepts and goals. It will also highlight ongoing prototype implementations being developed within the context of the SRCNet (Square Kilometre Array Regional Centres Network), demonstrating practical applications and informing the evolution of the standard. The session will offer insights into lessons learned, emerging challenges, and next steps toward community adoption.

|
Joshua Fraustro

(In person)
| Generation of code from OpenAPI |
15'

9:45-10:00
| In the ongoing efforts within the International Virtual Observatory Alliance (IVOA), we are working to define our protocols using OpenAPI specifications. This approach aims to make our standards not only human-readable but also machine-actionable, thereby enhancing interoperability and automation. However, the generation of OpenAPI documentation from our existing protocol definitions presents several challenges and limitations. | | |

Joshua Fraustro

(In person)

| Generation of code from OpenAPI |

15'

9:15-9:30

| In the ongoing efforts within the International Virtual Observatory Alliance (IVOA), we are working to define our protocols using OpenAPI specifications. This approach aims to make our standards not only human-readable but also machine-actionable, thereby enhancing interoperability and automation. However, the generation of OpenAPI documentation from our existing protocol definitions presents several challenges and limitations. | | |
Mark Taylor

(Remote)
| IVOA Authentication |
15'

10:00-10:15
| The challenge of enabling non-browser clients to authenticate against VO services has been discussed over several years. Practice has now stabilised and is in use in production services and has led to an early draft of a new document tentatively named Interoperable Authentication Protocol. The scope and outline of IAP will be described, along with some open issues. | | |

Mark Taylor

(Remote)

| IVOA Authentication |

15'

9:30-9:45

| The challenge of enabling non-browser clients to authenticate against VO services has been discussed over several years. Practice has now stabilised and is in use in production services and has led to an early draft of a new document tentatively named Interoperable Authentication Protocol. The scope and outline of IAP will be described, along with some open issues. | |

Added:

>
>

CONFLICT version 9:

|
Adrian Damian

(Remote)
| Towards Federation of CADC AA&I |
15'

10:15-10:30
| We address the challenges of federating Authentication, Authorisation, and Identity (AA&I) services in the context of integrating the Canadian Astronomy Data Centre (CADC) services with those provided by the upcoming major astronomical facilities such as the SKA and Rubin. For that, we first evaluated existing proxy OIDC solutions, specifically Indigo IAM and CILogon, and also assessed the suitability of Keycloak for our federation needs. Based on this evaluation, we have chosen to prototype the required functionality within our existing Access Control (AC) system. We report on our approach and current progress and outline future development plans to support seamless and secure federated access. | | |

Adrian Damian

(Remote)

| Towards Federation of CADC AA&I |

15'

9:45-10:00

| We address the challenges of federating Authentication, Authorisation, and Identity (AA&I) services in the context of integrating the Canadian Astronomy Data Centre (CADC) services with those provided by the upcoming major astronomical facilities such as the SKA and Rubin. For that, we first evaluated existing proxy OIDC solutions, specifically Indigo IAM and CILogon, and also assessed the suitability of Keycloak for our federation needs. Based on this evaluation, we have chosen to prototype the required functionality within our existing Access Control (AC) system. We report on our approach and current progress and outline future development plans to support seamless and secure federated access. | | |
Brian Major

(Async)
| Firefly on CANFAR | No Talk (Material
Shared) | The Firefly tool is now available on CANFAR deployments. The work exposed some interesting interoperability challenges: AAI integration, container standardization, and the potential for a standardization of platform APIs that would allow tools (Firefly, CARTA, Jupyter, etc...) to interact with other tools running on the same platform and other platforms, enabling distributed computation on platform datasets. | pdf |

Added:

>
>

CONFLICT version new:

Joint session with Operations.

DSP Sessions

Moderators: Sara Bertocco, Tamara Civera

CONFLICT end

Brian Major

| Firefly on CANFAR |

15'

10:00-10:15

| The Firefly tool is now available on CANFAR deployments. The work exposed some interesting interoperability challenges: AAI integration, container standardization, and the potential for a standardization of platform APIs that would allow tools (Firefly, CARTA, Jupyter, etc...) to interact with other tools running on the same platform and other platforms, enabling distributed computation on platform datasets. | pdf | | Marcos Lopez-Caniego | ESA DataLabs |

15'

10:15-10:30

| ESA Datalabs is a collaborative platform designed to bring data closer to researchers by enabling on-demand data processing and analysis within ESA’s science archives. It integrates high-performance computing, Jupyter-based environments, and standardized data access protocols, allowing scientists to run complex workflows without the need to download massive datasets. This presentation introduces the architecture of ESA Datalabs, showcases use cases from astronomy and planetary science, and outlines how the platform supports reproducible research and interoperability through adherence to IVOA standards. By lowering the barrier to large-scale data analysis, ESA Datalabs accelerates scientific discovery and fosters innovation within the space science community. | |

Wednesday June 5 @11:00 CEST: Room
Speaker	Title	Time	Abstract	Material
ZHANG, Zhen (Remote)	Experiences and lessons learned from EP scientific workflow	15' 9:15-9:30	An automated and efficient workflow is crucial for scientific output in astronomy, particularly in time-domain astronomy. The National Astronomical Data Centre (NADC) has undertaken the development of the workflow for the Einstein Probe(EP), a high-energy X-ray satellite focused on time-domain astronomy. During the development process, we encountered challenges including workflow orchestration, workflow scalability, and the traceability of data product generation processes. To address these issues, we developed a workflow framework based on cloud technologies, including containers, message queues, and workflow orchestrators, etc. This framework offers excellent scalability and portability and significantly enhances the efficiency of complex algorithm integration and deployment in multi-team collaborations. Finally, we proposed our recommendation for provenance and workflow data model. This framework can be further applied to future time-domain astronomy projects, and we hope that our experiences can provide insights for the IVOA workflow standards.
Baptiste Cecconi	Workflow orchestration for radio interferometric imaging using EXTRACT	15' 9:30-9:45	We present the result of the EXTRACT project, which is proposing a compute continuum framework (with edge, cloud and HPC compute resources) on a distributed data environment. In our presentation, we will show how we deploy multiple cloud-ready and HPC-ready technologies to furnish radio astronomers with a simple interface to describe data processing workflows which dramatically lowers the difficulty threshold of using complex tools from the radio interferometric community. In the case of NenuFAR, we propose workflows to dynamically process the imaging data of the dynamic Sun, which enables the astrometric localisation of the solar bursts (Type II, Type III bursts), and planets (e.g. Jupiter, exoplanets), complementary to beamformed observations. This workflow integrates classical LOFAR tools and methods as well as recent direction-dependent tools (e.g. DDFacet, killMS, DynSpecMS) to perform complex operations on interferometric data, such as the processing of the NLFSS sky survey and the search for exoplanetary signatures using rebuilt dynamic spectra derived from imaging data. We will discuss how this will be interfaced with IVOA standards for data provenance and data discoverability.

META FILEATTACHMENT	attachment="Firefly-on-CANFAR.pdf" attr="" comment="" date="1748767639" name="Firefly-on-CANFAR.pdf" path="Firefly-on-CANFAR.pdf" size="797652" user="BrianMajor" version="1"

View topic | History: r24 < r23 < r22 < r21 | More topic actions...