Alert samples

[fe51]

This PR introduces following modifications:

• Updates Dockerfile to python 13
• Updates Download notebook
• Adds function in utils
• Updates send_real_alerts with various example

After this, might be useful to discuss and remove/refactor send_real_alerts.ipynb

[MateoLostanlen]

Hi @fe51 , alerts got shifted bbox :)

[MateoLostanlen]

I tired to run send_real_alerts.ipynb but got

[fe51]

Hi @MateoLostanlen

• About shifted bbox, are you sur it does not come from the current bug in the platform ? (on big screen Bbox & image do not fit on large screens pyro-platform#181)

• Have you delete the previous alert_samples dir you have ? (because alerts folder name because the name is related to the datetime of the first detection) -> and the code only check the presence of alert_samples dir

[MateoLostanlen]

Hi ok my bad you are right for both 😄

[MateoLostanlen]

Hello @fe51, thanks for the PR. Overall it works fine, nothing to say about that, but it’s a bit of a pity that it remains very manual:
There are quite a lot of steps if we want to select a new alert. Ideally, the cam_triangulation dictionary would be handled automatically, or only based on indexes

In any case, this notebook also needs some cleaning at the beginning. We can merge the PR to validate the new features, and then make another one later for the cleanup

[fe51]

Thanks for the feedback and I share your point of view, especially about triangulation alerts and the need to clean the notebook.

About triangulation and automation, not implemented due to lack of time, as it is necessary to ensure that the correct cameras are associated with the selected alerts.
However, in this regard, it is also necessary to consider how often new triangulated alerts should be added to this development environment.

I will open 2 issues to work on it.