Version 2.34.0 (2026-10-23)
- Redesigned sub-filter panels
- Clearer layout: "Any of" / "All of" groups, on/off options as chips, conditions as aligned rows; a roomier panel on the web and no more sideways scrolling on phones
- Set values with sliders, day presets (1/3/7/14/30 days) and +/- steppers instead of typing every number
- Sub-filters now name their units: GW class probabilities [0-1], significances [σ], Sun distance [deg], days since last detection, latest magnitudes [mag]
- A new "All bands" row sets one magnitude limit for all photometric bands at once
- See how many of the loaded events each filter lets through, in the sub-filter panel and, if you switch it on in the display settings, on every filter button
- On mobile, a tune icon on each filter button opens its sub-filters (long-press still works)
- Your filter settings (on/off choices and sub-filter values) are kept when a new version updates the filters
- Bi-directional integration with the Gravitational-Wave Treasure Map
- Report a whole tilepy schedule, or a single pointing of a GW event, of one tilepy pointing or of a custom event; the instrument of your observatory is preselected
- Report planned pointings as completed once observed, or cancel those you will not observe
- See everybody's pointings on the sky map of GW events, with the instrument footprints; switch instruments and planned/completed pointings on and off
- Send events to SkyPortal
- Connect with your SkyPortal API token under Account settings > Observatory & TOM access and save an event as a source for the groups you choose; the source links back to Astro-COLIBRI
- ICARE and Fritz are already available, you can add further SkyPortal instances yourself
- Request observations from the Las Cumbres Observatory network with your LCO proposal, and follow their state and data
- Filter the broker alert stream with your own filters (Python SDK 1.3.0)
- Apply the filters you saved in the app, the file from the "Download Filters" button, or a filter written by hand to the alerts you receive: consumer.consume(event_filter=...)
- Same result on the JSON and the VOEvent topics, and the same as in the API searches
- New API endpoint /saved_filters returns the filters saved in the app for your account, ready to use in your searches
- Documentation: broker filtering and the SDK tutorial
- Follow the important alerts on the AT Protocol, the open network behind Bluesky, without any account
- Every alert of the important stream is posted publicly from @astro-colibri.science, seconds after the broker, in the native JSON format and as VOEvent
- Listen live with the nebra Python package, or browse the archive
- Documentation: alerts on the AT Protocol; the broker status panel shows whether the AT Protocol mirror is running
- Send events to your VO desktop tools (TOPCAT, Aladin Desktop, DS9, ...) via SAMP
- In science mode on the web interface, a new button in the event details sends the event's position and a VOTable of the event to the SAMP applications running on your computer
- Start TOPCAT or Aladin Desktop to open a SAMP hub, then accept the connection from Astro-COLIBRI; works in Chrome and Firefox (Safari cannot connect to a local SAMP hub)
- New public API endpoint /get_event_as_votable returns one or more events (trigger_id, archive_id or source_name) as a VOTable
- Richer VOEvents
- VOEvents from the broker and the API now include the photometry of optical transients (first, peak and last detection per band) and more event details: constellation, associated event, discoverer name, image links
- Minor features and improvements
- New documentation page on TOMs and observing services
- The tilepy request dialog shows the visibility of the event on the chosen date from the chosen observatory, right under the date and time
- CBAT "TCP" transient announcements are now sent to everyone subscribed to "Optical transients: other", next to the CBAT nova alerts
- Python SDK: alert.important tells you whether an alert on the astrocolibri.all stream is also on the astrocolibri.important stream, so you can filter the full stream without subscribing to both
- /getContour API endpoint now returns each localisation region with its credible level (contours); the contours50/contours95 fields were removed