As discussed during the last update meeting, it would be beneficial to avoid the dawn and dusk periods for the optical profiles in the operational setup.
Mostly because of strong temporal changes in background and potential switch on/off of Raman channels.
To be flexible in the non-operational setup a flag at the cloud free profile segmentation step might be an option.
I.e. to exclude/flag cloud free profiles that are too close to sunrise/sunset.
From the location and height, the times of sunrise and sunset can be 'easily' calculated.
I would propose to use skyfield, mostly to avoid a own implementation and because it's also used in sunscanpy for the radar pointing calibration.
Example for the calculation
For the question which time to exclude we can either go for a fixed interval (e.g. +- 30 mins) or make it dependant on the sun elevation angle (e.g. following the definitions of civil/nautical/astronomical twilight)
As discussed during the last update meeting, it would be beneficial to avoid the dawn and dusk periods for the optical profiles in the operational setup.
Mostly because of strong temporal changes in background and potential switch on/off of Raman channels.
To be flexible in the non-operational setup a flag at the cloud free profile segmentation step might be an option.
I.e. to exclude/flag cloud free profiles that are too close to sunrise/sunset.
From the location and height, the times of sunrise and sunset can be 'easily' calculated.
I would propose to use skyfield, mostly to avoid a own implementation and because it's also used in sunscanpy for the radar pointing calibration.
Example for the calculation
For the question which time to exclude we can either go for a fixed interval (e.g. +- 30 mins) or make it dependant on the sun elevation angle (e.g. following the definitions of civil/nautical/astronomical twilight)