Kim Hoogenberg
After being graduated in 2003, Kim has worked in Amsterdam for a few years working on realtime news and rates distribution and "Over The Counter" trade engines. After that period he worked as an independent Software Engineer for almost 20 years for multiple companies and governmental organisations. Now back to his roots, he is living in Drenthe and working in what could be called his backyard at ASTRON as a Senior Software Engineer with team Rainbow where he is able to combine his passion of the Universe with his profession. Since 2026 Kim also joined SRCNet where he is working on the Federate Execution Platform for the SKA telescope. When he's off duty, Kim loves to do sports and cooking and he is happily living with his wife and 5 kids in the small village of Schoonoord.
Sessions
The SKA Regional Centre Network (SRCNet) will support scientific analysis through a federation of independently operated computing and storage facilities. Executing workflows across this infrastructure requires a common interface that accounts for data location, heterogeneous resources, and local scheduling policies.
We present the SRCNet Federated Execution Framework, a prototype that connects scientific workflow submission to execution on participating sites. A Computing Broker identifies eligible sites using resource capabilities and data locality.
Site-level Job Gateways provision pilot workers through local Kubernetes or Slurm infrastructure. HTCondor then matches queued workflow tasks to compatible pilots once resources become available, a mechanism known as late binding. This decouples task submission from worker allocation while allowing each site to retain control over its resources and scheduling policies.
The poster explains the architecture and follows a workflow from submission through site eligibility checks, pilot provisioning, execution, and status reporting. We illustrate the approach with the ICAL/Rapthor radio-interferometric calibration and imaging workflow, drawing on the prototype’s multi-node execution demonstration. We also discuss integration challenges involving authentication, delegated credentials, data access, and the boundary between federated services and site operations.
We conclude with lessons from building the prototype and priorities for operational deployment, including broader site validation, robust data staging, and execution identity management. The framework offers a concrete example of how existing scheduling technologies can support a common scientific execution service across heterogeneous astronomical computing facilities.
Astronomical software thrives on collaboration. Many collaborations, however, are created around funded projects and remain active only for as long as that funding continues. When the funding ends, the collaboration often ends with it, while the software and its users remain.
The consequences can be that software becomes unmaintained or former partners continue development independently, creating diverging forks which causes duplicated effort and uncertainty for new users and contributors. At the same time, the cross-institutional networks built during these projects disappear, networks that provide opportunities for discussion and grounds for future collaboration.
Community collaborations such as Astropy and the IVOA demonstrate that this is not inevitable. They show that sustainable collaboration can be achieved through a variety of ways of working and funding.
This BoF will explore what makes such collaborations last and why others fail. The session will be centered around a panel discussion with a panel of experts and the audience. We will explore questions including: What enables a collaboration to survive? Which governance and maintenance models work in practice? How should responsibility be shared between individuals and institutes? And which warning signs indicate that a collaboration is unlikely to remain sustainable?
Our aim, with this discussion, is to identify commonalities between successful projects, or what makes some initiatives less successful at remaining a long-lasting collabroration. If the outcome of the discussion permits, we intend to summarise those points and submit them as an entry in the proceedings, as a reference.