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

Maximum exposure time in 'adaptive' mode is too long #100

christophkern opened this issue Jul 27, 2018 · 2 comments


None yet
2 participants
Copy link

commented Jul 27, 2018

When making measurement in the 'adaptive' exposure time mode, we sometimes get very long exposures. This can e.g. happen when passing under a tree. Then, the instrument decides it's very dark and selects a very long exposure time. In a separate issue, I have described what I think is a better method for determining the new exposure time. Here, I address the limit for maximum possible exposure time, regardless of how the exposure time is determined.

The user sets the integration time of the measurement in the configuration. We typically use 1000 ms. This means that the spectrometer records as many spectra as it can in 1 second, adds them up and sends them to the computer.

However, if the light level drops (e.g. due to a tree), the new exposure time can sometimes exceed the integration time. I think that I have seen exposure times of 4 seconds or longer. Such a long exposure time is annoying, because it usually leads to oversaturated spectra and also blocks the acquisition of useful data for quite a while. I therefore suggest that the maximum permissible exposure time should be equal to the user-defined integration time. In our example, the maximum exposure time should be 1000 ms. That way the spectrometer will take 1 spectrum at 1000 ms, then re-asses the light situation, and we can stay on our acquisition rate of 1 acquisition per second.


This comment has been minimized.

Copy link

commented Sep 9, 2018

Added a fix to limit the maximum exposure time to the time-resolution of the measurement in commit 1384473 .

@mattias42 mattias42 self-assigned this Sep 9, 2018

@mattias42 mattias42 closed this Oct 28, 2018


This comment has been minimized.

Copy link

commented Oct 28, 2018


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.