Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 'MAYAPRO' to spectrometer model drop down #8

Closed
dnorgaard-usgs opened this issue Nov 16, 2017 · 3 comments

Comments

Projects
None yet
1 participant
@dnorgaard-usgs
Copy link
Contributor

commented Nov 16, 2017

No description provided.

@dnorgaard-usgs

This comment has been minimized.

Copy link
Contributor Author

commented Dec 7, 2017

16-bits
2065 pixels
5200 offset removal
need to confirm

What is max intensity?

double CSpectrometerModel::GetMaxIntensity(const SPECTROMETER_MODEL modelNumber){
switch(modelNumber){
case S2000: return 4095;
case USB2000: return 4095;
case USB4000: return 65535;
case HR2000: return 4095;
case HR4000: return 16535;
case QE65000: return 65535;
case MAYAPRO: return 4095;
default: return 4095;
}
}

@dnorgaard-usgs

This comment has been minimized.

Copy link
Contributor Author

commented Dec 7, 2017

This seems to be output for evaluation log. Doesn't seem to matter what text to put in?

switch(m_specInfo.m_specModel){
case S2000: string.AppendFormat("\tspectrometer=s2000\n"); break;
case USB2000: string.AppendFormat("\tspectrometer=usb2000\n"); break;
case USB4000: string.AppendFormat("\tspectrometer=usb4000\n"); break;
case HR2000: string.AppendFormat("\tspectrometer=hr2000\n"); break;
case HR4000: string.AppendFormat("\tspectrometer=hr4000\n"); break;
case QE65000: string.AppendFormat("\tspectrometer=qe65000\n"); break;
case MAYAPRO: string.AppendFormat("\tspectrometer=mayapro\n"); break;
default: string.AppendFormat("\tspectrometer=s2000\n"); break;
}

@dnorgaard-usgs

This comment has been minimized.

Copy link
Contributor Author

commented Dec 7, 2017

On Thu, Dec 7, 2017 at 12:21 AM, Santiago Arellano santiago.arellano@chalmers.se wrote:
Hi Diana,

Nice to hear from you.
I see two possibilities to deal with this feature. The quicker is to add a ‘case’ line for the MAYA spectrometers, specifying the parameters that make them different than other spectrometers. In this case the value that the other models are returning is the dynamic range of the ADC. Whenever you see ‘4095’ corresponds to spectrometers that use a 12 bit ADC and thus the signal can get up to 2^12=4096 counts (this is to say 0 to 4095 units) to measure intensity of light. If the value is 65535 is because the ADC has 16 bits. In the case of MAYA it should also be 65535 (the value that you show for the HR4000 seems weird, as it doesn’t match exactly any power of 2, maybe it should be 16385 if it uses a 14 bits ADC, but as far as I know no one actually uses this spectrometer in novac).

The value for pixels is the x-axis in the spectrum, the number of channels that each spectrometer uses to represent wavelengths of light. Most spectrometers use 2048 (active) pixels, and this is also the case with the MAYA. In the manual http://oceanoptics.com/wp-content/uploads/OEM-Data-Sheet-Maya2000Prov3.pdf (p. 7) you can find the description of the functions assigned to the pixels, some are darkened, some are active. It says that the MAYA uses pixels 10 to 2057 for the spectrum. But I think we could in principle collect more channels but some of them are useless.

For the MobileDOAS program the best solution, which I think it does in some way already now, would be to make the program read the EEPROM of the spectrometer and retrieve automatically the specifications (serial number, model, number of bits, number of active pixels, firmware). The OceanOptics software has this feature so if you connect a spectrometer shows something like this:

Not all information is needed, basically the number of bits, pixels and serial number are the most interesting for novac.

Best regards,
Santiago.

@dnorgaard-usgs dnorgaard-usgs self-assigned this Dec 9, 2017

dnorgaard-usgs added a commit that referenced this issue Feb 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.