Opened 16 years ago
Last modified 16 years ago
#221 new Data problem
Field in header files labelled 'fwhm' is actually bandwidth
| Reported by: | benj | Owned by: | benj |
|---|---|---|---|
| Priority: | alpha 5 | Milestone: | |
| Component: | Metadata | Keywords: | |
| Cc: | mggr | Other processors: |
Description
The field in Specim raw data header files labelled "fwhm" (Full Width Half Maximum) isn't actually the FWHM, it's the bandwidth. Confirmed by Specim via email (see below).
Bill currently thinks that it probably doesn't have any effect on processing (since Specim's calibration algorithm appears to have been written assuming that the FWHM is actually the bandwidth), but it's potentially confusing to users who are likely to assume that it's the FWHM when it isn't.
(comment edited 21/Sept/2009 to remove direct quotes of Specim emails - a relevant summary has been inserted instead)
- Specim confirmed that FWHM as given in the .wls files and in .hdr files is actually bandwidth
- an average FWHM is calculated for spectral peaks during calibration
- no accurate FWHM is currently available
Note: See
TracTickets for help on using
tickets.
(comment edited 21/Sept/2009 to remove direct quotes of Specim emails - a relevant summary has been inserted instead)
Got another email from Specim with the average FWHMs (3nm for Eagle and 8.9nm for Hawk, over the full spectral area).