Handle MEAN values with commas in removeBadImages.sh

[EricClaeys]

Discussed in #4302

^{Originally posted by DC1RS February 9, 2025}
After updating to v2024.12.06_01, I keep getting the message “Multiple consecutive bad images. Check the values of 'Bad image removal threshold low', 'Bad image removal threshold high' and 'Maximum auto exposure' in the WebUI.” with the same settings that worked fine with v2024.12.06 (0.1/0.9).
If I deactivate “Remove Bad Images Threshold Low / High” with 0, allsky starts up.

There is an issue with the Locale settings. I usually use de_DE.UTF-8, so decimal separator is comma instead of dot.
Now with v2024.12.06_01 there's an error message in allsky_log.txt:
2025-02-09T15:11:15.871062+01:00 allsky allsky[21142]: removeBadImages.sh: File is bad: removed 'image-20250209151112.jpg' (MEAN of 0,504436 is below low threshold of 0.1).
Changing the Locale to en_EN.UTF-8 fixed the problem.
Strangely it was working with de_DE.UTF-8 in v2024.12.06.

BR
Roland
support-none-20250209151111.zip

When a comma is used for the decimal separator, the capture program returns a MEAN with a comma. However, users have periods in the Bad Image Removal Thresholds, so removeBadImages.sh needs to handle commas in the MEAN.