You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that the Pyronear project has a low-resource approach, as we try to minimise the environmental impact of our products, it seems relevant to have an idea of the CO2 emissions associated with our training sessions.
There are various solutions for this, including codecarbon developed by some D4G volunteers.
Consequently, it would be interesting to include some related metrics in our ml ops workflow.
In this way, we could compare the performance of the training sessions in terms of estimated CO2 emissions and sum it to have estimate CO2 emission of Pyronear model training
What do you think ?
Happy to discuss it :)
The text was updated successfully, but these errors were encountered:
I think it is a great idea:) I have used codecarbon before. I think it would be nice as a 1st step to monitor code execution thanks to codecarbon and / or lineprofiler. In a 2nd step improve run time and co2 emissions. It could even be part of the ML Flow process. What do you think about it @MateoLostanlen ?
Hi there,
Given that the Pyronear project has a low-resource approach, as we try to minimise the environmental impact of our products, it seems relevant to have an idea of the CO2 emissions associated with our training sessions.
There are various solutions for this, including codecarbon developed by some D4G volunteers.
Consequently, it would be interesting to include some related metrics in our ml ops workflow.
In this way, we could compare the performance of the training sessions in terms of estimated CO2 emissions and sum it to have estimate CO2 emission of Pyronear model training
What do you think ?
Happy to discuss it :)
The text was updated successfully, but these errors were encountered: