Release v0.4.3

v0.4.0

In this minor release:

• Deprecated Python 3.8 support
• Added more alert parsers (e.g. for INTEGRAL messages)
• Added option to control triggering the automatic planning depending on skymap area

v0.4.1

• Fixed incorrect naming of alert origin after cross-matching

v0.4.2

• Fixed unable to run without -t option if Telegram API not set

v0.4.3

• Fixed issue, when Swift alerts were marked as retracked mistakenly
• Fixed float number format in LVC alerts
• Fixed the tool to bump new version into files
• Added global FAR threshold for LVC alerts

AWARE-v0.3

v0.3.0

Since this release, native Windows platform is not supported!

New planning system.

The observation planner tries to cover the most probable are of the GW event with mosaic and target observations. It is considered that in automatic mode, as GW skymap received and GW classified as BNS or NSBH, the observation plan will be created for a first night. The planner computes how many targets a telescope can observe during the night, provided that the telescope slew time is constant, but not zero. Also, it performs a kind of clustering with nearest neighbor algorithm, since we do not want a telescope "jumps" between sky fields or targets, significantly.

Updated Telegram bot

The Telegram bot logic is rewritten in such way, that a user must subscribe to the user before receiving alert messages and observation plans. The subscription dialog is very intuitive and contains a list of alert types that could be received, and a list of telescopes for which the bot sends the observational data.

Executable scripts

Added several scripts to be able to perform sky map displaying, planning, etc in place. The possible use case is when a one wants to make plans for next days of observations (remember that 1st day planning is possibly performed) or re-create the plans, for instance, with an addition of other telescopes.

API

Changes to API:

• Config file is no more needed for using AWARE
• All config options have attribute value for a convenient access to the value
• Added more observatories
• Based on observatory, there is a certain format for the list of targets/sky fields for observations
• Telescopes have default values for photometric filter, exposure time, exposure count
• Alert events are cross-matched before sending the alert messages in Telegram and creating the plans
• Something more we forgot to mention :)

AWARE-v0.2.0-alpha

In this alpha release, we have:

• Added asynchronous consuming loop of alert messages
• Added a Telegram bot thread, which communicates with humans
• Added observation planner for events in alerts

Note. Make sure you can dedicate to AWARE about 10 GiB of RAM, which is needed for stable work with LIGO/Virgo/KAGRA localization skymaps.

AWARE 0.1.0

v0.1.0

Minor changes