BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.adass.org//adass2026//speaker//RLUJNY
BEGIN:VTIMEZONE
TZID:AWST
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1;UNTIL=20051231T160000Z
TZNAME:AWST
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20070325T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:AWST
TZOFFSETFROM:+0900
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20071028T030000
RRULE:FREQ=YEARLY;BYDAY=4SU;BYMONTH=10;UNTIL=20081025T190000Z
TZNAME:AWDT
TZOFFSETFROM:+0800
TZOFFSETTO:+0900
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-adass2026-WP89MK@pretalx.adass.org
DTSTART;TZID=AWST:20261104T173000
DTEND;TZID=AWST:20261104T183000
DESCRIPTION:Astronomy is entering an era in which several major facilities 
 are simultaneously operating\, or standing up\, science platforms designed
  to deliver petabyte-scale data and computing to their communities. As mis
 sions and observatories move from data collection to data delivery at scal
 e\, they are independently converging on similar architectural choices —
  and independently running into similar operational challenges — around 
 federated access\, compute-to-data\, authentication\, and long-term sustai
 nability. This BoF is proposed by confirmed panelists from Euclid/ESA Data
 labs\, Vera Rubin Observatory\, the SKA Regional Centre Network (SRCNet)\,
  Roman Telescope\, CADC/CANFAR\, NASA/Fornax and LOFAR. Other platforms ar
 e invited to join the discussion to compare architectures\, operational le
 ssons\, and user-facing services for large-scale science platforms and wor
 kflows.\n\nWith Euclid's Data Release 1 (DR1)\, a full year of Vera Rubin 
 Observatory operations\, the launch of the Roman Space Telescope\, and SKA
  Low's science verification getting underway next year\, the timing is ide
 al to take stock of what's working\, what isn't\, and where the community 
 could converge — on topics such as federated data access\, compute-to-da
 ta models\, interoperability standards\, and the balance between bespoke p
 latform development and shared infrastructure. Panellists will open the se
 ssion with a short position statement on how their platform is architected
  and operated today\, before the floor opens to a moderated discussion aim
 ed at surfacing common challenges and concrete opportunities for collabora
 tion across observatories.
DTSTAMP:20261015T123845Z
LOCATION:Seminar Room 1
SUMMARY:Science Platforms at Scale: Developing Data Services in the Petabyt
 e Era - Javier Ballester Arenas\, Yan Grange\, Marcos López-Caniego\, San
 dor Kruk\, Jesus Salgado\, Christophe Arviset\, Michele Delli Veneri\, Ros
 ie Bolton\, William O Mullane\, Carmen Toribio\, Brian Major
URL:https://pretalx.adass.org/adass2026/talk/WP89MK/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-adass2026-JBADXP@pretalx.adass.org
DTSTART;TZID=AWST:20261104T173000
DTEND;TZID=AWST:20261104T183000
DESCRIPTION:For a few years now\, some astronomical data centers have obser
 ved an increasing number of incoming requests. This usually indicates that
  a service is becoming more popular and useful. However\, the number and r
 ate of these requests is so high that the services are becoming increasing
 ly overwhelmed\, ending up by a saturation and complete unavailability. Wo
 rryingly\, this trend is speeding up. Consequently\, services are becoming
  unavailable more often and more quickly than before.\n\nThe recently obse
 rved growth in activity actually hides a different user profile. Until now
 \, humans and indexing crawlers were the only users of our services. Now\,
  there is a new category of users: AI bots. Unlike the other users\, they 
 are much more aggressive. There are two main reasons for this. First\, the
 y rely on cloud infrastructures. This allows them to massively parallelize
  the web scrapping operations and use an enormous number of different IP a
 ddresses\, making them impossible to block with the usual methods. Second\
 , they do not adhere to any best practices\, such as the well-known `robot
 s.txt`\, which indexing crawlers (search engines) read and follow.\n\nThro
 ugh this BoF\, CDS (France)\, ESAC (Spain)\, and Data Central (Australia) 
 aim to discuss beyond the negative impact of this recent practice on their
  infrastructures and explore strategies to maintain the high availability 
 and quality of their services while allowing AI to reasonably interact wit
 h them. Everyone is welcome to join the discussion and share experiences\,
  solutions (e.g. mirrors\, proxy\, authentication\, ban with well-identifi
 ed and shared IP ranges)\, and\, more generally\, ideas.
DTSTAMP:20261015T123845Z
LOCATION:Seminar Room 3
SUMMARY:How to cope with the rapidly increasing number of aggressive incomi
 ng requests? - Simon O'Toole\, Christophe Arviset\, MANTELET Gregory\, Gil
 les Landais
URL:https://pretalx.adass.org/adass2026/talk/JBADXP/
END:VEVENT
END:VCALENDAR
