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

Dual-beam measurement acquisition issues #89

Closed
dlnorgaard opened this issue Jul 16, 2018 · 3 comments
Closed

Dual-beam measurement acquisition issues #89

dlnorgaard opened this issue Jul 16, 2018 · 3 comments
Assignees
Labels

Comments

@dlnorgaard
Copy link

The dual-beam acquisition of data does not appear to work in adaptive mode. Also, for some reason, Christoph is getting results of both channels into the same evaluation log files whereas I was getting them into two separate ones during testing.

On Sat, Jul 14, 2018 at 11:25 AM, Kern, Christoph ckern@usgs.gov wrote:
Hi Diana

I have made further tests with the dual beam Mobile DOAS software. You were right in that the fitting of the Slave channel does indeed work when using a fixed exposure time! In that case, the spetrum fits as well as the red and blue bars displayed in real time make total sense. However, the results of both spectrometer channels are still written into the same EvaluationLog. Not sure if this is intended.

Attached is some example data we collected on 7/12. These are wind speed measurements that we made while sitting under the plume with the master channel looking 10 deg towards the vent, the slave looking 10 deg away from the vent (20 deg separation of the 2 channels).

The cfg.xml is the same as before, with just the exposure time now fixed to 50 ms.

Thanks!

Christoph
Kilauea20_20180712_1223_windspeed.zip

@dlnorgaard dlnorgaard added the bug label Jul 16, 2018
@dlnorgaard dlnorgaard changed the title Dual-bean measurement acquisition issues Dual-beam measurement acquisition issues Jul 16, 2018
@dlnorgaard
Copy link
Author

Description of what Christoph was seeing in adaptive mode is below. I tried running it in office and do appear to get an odd fit for the second channel:

image

On Tue, Jul 10, 2018 at 7:35 PM, Kern, Christoph wrote:
Hi Diana and Matias

I went out and collected some dual beam MobileDOAS data today. The good news is that the spectral acquisition seemed to work really well, and I'm confident I can analyze the data later in the office.

What didn't work so well is the real time spectral analysis. I'm not sure why, but the fit for the second channel of the spectrometer was very strange. It didn't seem to really be fitting SO2. It immediately showed -2000 ppmm, then changed only by 2000 ppmm (just reaching 0) while the first channel went up to more than 10,000 ppmm. I also tried unplugging the channel 2 fiber, but the fit still gave numbers very close to 0 with hardly any noise. I'm not sure how this is possible for dark spectra.

Do you think you could check and see if you can find any obvious mistakes in the fit procedure for the second channel? I tried reproducing the fits in DOASIS, and they seem to work better there. Not sure what is going on...

I'm attaching some of the collected data. Kilauea 11 is a wind measurement attempt, Kilauea 13 contains 2 traverses.

Thanks

Christoph

@dlnorgaard
Copy link
Author

The fit window names must differ in order to get separate evaluation logs for each channel. Some code changes were made to ensure that fit window names differ.

dlnorgaard pushed a commit to dlnorgaard/MobileDOAS that referenced this issue Jul 19, 2018
…) or (Slave) on insert (for NOVACProject#89).  Warn user that last fit window cannot be removed (for NOVACProject#91).
@dlnorgaard dlnorgaard self-assigned this Jul 24, 2018
dlnorgaard pushed a commit to dlnorgaard/MobileDOAS that referenced this issue Jul 24, 2018
dlnorgaard pushed a commit that referenced this issue Jul 24, 2018
fix evaluation of second channel in adaptive mode (#89)
@dlnorgaard
Copy link
Author

Issue in adaptive mode fixed. Also, there seems to be an agreement that we will have two eval logs, one for each channel. Changes in GUI has been made to ensure this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant