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
There is a bug in the software that occurs when you "Enable automatic instrument calibration from measured spectra" in the 'Calibration' settings of an instrument. Enabling the feature automatically generates reference cross sections as desired, but when these are automatically loaded into the instrument's 'Evaluation' settings, the 'Name' in the list of reference files changes from a simple identifier (e.g., SO2) to a more complex string (e.g., SO2_Bogumil_295K). These new, more complex names are then used in the column headers above the respective fit results in the EvaluationLog. Once this happens, the software apparently no longer understands which fit results to use when identifying plumes, determining plume locations, or calculating the 'plume completeness' parameter. There is never a vertical line indicating a plume center in the scan, the real-time plume completeness is always set to -999, and all real-time derived fluxes are set to 0.
Interestingly, the software is able to identify the SO2 column density when doing Post-Flux analysis. Everything works fine in the "Flux" calculation dialog, so Post-Flux processing is still possible. However, some observatories rely on the real-time fluxes, at least as a preliminary product, so not having those is a major issue for them. For now, they have been instructed to simply uncheck the "Enable automatic instrument calibration from measured spectra" box and use the default references in the fit. But this is a nice new feature so it's a shame not to be able to use it.
The text was updated successfully, but these errors were encountered:
There is a bug in the software that occurs when you "Enable automatic instrument calibration from measured spectra" in the 'Calibration' settings of an instrument. Enabling the feature automatically generates reference cross sections as desired, but when these are automatically loaded into the instrument's 'Evaluation' settings, the 'Name' in the list of reference files changes from a simple identifier (e.g., SO2) to a more complex string (e.g., SO2_Bogumil_295K). These new, more complex names are then used in the column headers above the respective fit results in the EvaluationLog. Once this happens, the software apparently no longer understands which fit results to use when identifying plumes, determining plume locations, or calculating the 'plume completeness' parameter. There is never a vertical line indicating a plume center in the scan, the real-time plume completeness is always set to -999, and all real-time derived fluxes are set to 0.
Interestingly, the software is able to identify the SO2 column density when doing Post-Flux analysis. Everything works fine in the "Flux" calculation dialog, so Post-Flux processing is still possible. However, some observatories rely on the real-time fluxes, at least as a preliminary product, so not having those is a major issue for them. For now, they have been instructed to simply uncheck the "Enable automatic instrument calibration from measured spectra" box and use the default references in the fit. But this is a nice new feature so it's a shame not to be able to use it.
The text was updated successfully, but these errors were encountered: