It does indeed, thanks. As for point 2) I have seen mention that 10/3nm
mode is substantially oversampled and that it would benefit from some form
of deconvolution or LOWESS processing before use. But I take it from your
answer that it's good to go as it comes out of the drivers, yes?
Thanks again,
Jack
On Wed, Dec 28, 2016 at 12:16 AM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote:
Hi,
1) I understand that in high res mode the device produces data at every
10/3nm. Is the
data processed by Argyll/drivers in any way before being written to the
file and if so how?
yes of course - the data from the instrument is raw sensor values, so the
driver has to do a bunch of processing to convert this to calibrated
values.
2) Would you recommend processing the output data in the file and if so
how?
I'm not sure what you mean. The results are calibrated spectral values.
Only
you know what you want to do with them after that.
3) Are sampling intervals other than 10/3nm and 'standard' available to
spotread and if so
what's the relative switch?
No. These are what are implemented in the ArgyllCMS driver. There seems
little
point in attempting to go below 3.333 nm, as this is the closest regular
spacing to
the sensor capability itself, and in any case the spectral resolution is
limited by the slit width. You can of course resample to larger spacings
using the usual methods (i.e. those recommended in the CIE specs.).
Hope this helps,
Graeme Gill.
