twVolc / PyCamPermanent

Permanent PiCam (SO2) installation project software
GNU General Public License v3.0
2 stars 2 forks source link

Deviation in results when using DOAS calibration vs Preloaded calibration method #73

Open ubdbra001 opened 11 months ago

ubdbra001 commented 11 months ago

Preloaded calibration method produces effectively the same results, but inludes data for a couple of additional timepoints. For the Lascar data (2022-05-20 16:05:15 - 17:30:30) there are additional points at: 16:05:15, 16:35:05, 16:35:10. Notably the 16:35:05 and 16:35:10 points would occur around the time where the DOAS-FOV search would start, I haven't tested to see if this changes if the time when the DOAS-FOV search start changes.

ubdbra001 commented 11 months ago

Tried it with doas_fov_recal_mins set to 25 mins and DOAS calibration and compared it to DOAS calibration and doas_fov_recal_mins: 30: Symmetric difference:

{'2022-05-20 16:30:05',
 '2022-05-20 16:30:10',
 '2022-05-20 16:35:05',
 '2022-05-20 16:35:10'}

16:30:05 and 16:30:10 not in the 25 min data 16:35:05 and 16:35:10 not in the 30 min data

ubdbra001 commented 11 months ago

Tried it with doas_fov_recal_mins set to 25 mins and Preloaded calibration, compared to DOAS calibration and doas_fov_recal_mins: 25 It produced three additional points at: 16:05:15, 16:30:05, 16:30:10, all in Preloaded calibration data

ubdbra001 commented 11 months ago

Changing remove_doas_mins doesn't seem to impact this