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
LOQ (& other SANS beamlines): Laser measurements #3361
Comments
Top get the data into the NeXus file will need a few changes:
|
I am attaching 2 documents. The first (Coherent_OBIS_LX_LS_Operator's_Manual_1184163_RevAG) describes the laser system and its control unit. We will get Items 1, 2, 3, 4, 12 & 13 shown on page 2-1 (pp 61). The control unit has both 9-pin D RS232 and USB interfaces. Remote operation is described in Appendix C starting on page C-1 (pp 277). We will need VI('s) to turn the laser on/off, set the power level, read the interlock status, read the laser operating status, read/set the indicator lights (if not automatic in firmware). To give you a feel for this, the manufacturers control software is described in Section 4 starting at page 4-1 (pp 109). The second document (LSI Correlator Manual) describes the device that takes the signal recorded by the laser light detector and processes it into something scientifically useful. It comes with its own control and data analysis software. At least initially, I anticipate that we will simply run this software on a laptop sat outside the sample position. But looking ahead we should move to do two things: i) control the correlator from Ibex, and ii) incorporate the correlator output into NeXus files (either those with the SANS data, or ancillary standalone ones?). The correlator control software is described in Chapter 4 from page 12. Graphical examples of the output data are shown in Figures 4.4, 4.5 & 4.6. I don't have an example of an output file from the correlator software at present, as we don't yet have the correlator! :-) |
1st file: Small problem: it's too big to upload! I'll put a copy somewhere you can access. |
Manuals are here: \\isis\shares\ISIS_Experimental_Controls\Manuals\LSI Correlator |
From: King, Stephen Kevin, Freddie, Some developments… The Italians are talking about shipping most of the apparatus to us in “2 to 3 weeks” time. Unfortunately (from your perspective) this is unlikely to include the correlator. They have been using a loan one from the company but the one they have ordered may not arrive this year. That doesn’t affect my side of commissioning, but obviously doesn’t help you! My understanding is that the correlator is that in the attached pdf (now in Manuals folder). You will hopefully rejoice in that they provide LabView and Python calling handlers! I also attach an example of a correlator output file that the student has sent me. This contains two principle data blocks:
The correlator appears to come with software to analyse these output files. Big tick.
In the longer term, it might be desirable to actually feed the raw correlator output into the DAE, but I don’t think we need that right now. Is this any help? |
From: Akeroyd, Freddie Hi Steve, The array looks to be size 2x277, so that is 277 values of (time,intensity) I guess. I believe there will be multiple instances of this array that will need to be stored in the NeXus file? The data file you enclose looks like a file serialisation of a labview cluster, you mention they have software that can read this format, is this LabVIEW software then? The python API doesn’t look to create files in this format, so we might need to try and reproduce this format if you were planning to use their software. The format though is very labview specific and seems to describes the labview control as well as the data within it. For example the “linear sample time” is not stored as “name, value” but rather the menu where the choice is made is described and then the index of which element in this list is given
Because it is based on a description of the object holding the data, I’m not sure what happens if this object structure changes. E.g. if a new choice item was later inserted into the list, do both the writer and reader Vis need to have the same choices (to avoid it just taking the 3rd element of a different list)? If so then you would need two different readers to handle data before and after the change to the choice list. It might be LabVIEW already handles this, I would need to defer to a LabVIEW expert. However if it was possible to have files generated in a format that was less Labview specific I think that would be more flexible for the future. |
Initial meeting scheduled for 1st Feb. |
This initial meeting took place on the 13th Feb. LOQ has procured an LSI correlator and they are working with their collaborators to understand how it should be operated. From our perspective, it's important to note that the data analysis (autocorrelation of the laser/neutron measurments) is currently performed by the vendor's software, as is the control of the device. We need to investigate what functionality the vendor's python API provides us, which we will be using to control the device. @Kevin-Woods-Tessella made some notes from the meeting which can be used to guide this investigation:
The investigation will be in a different ticket. |
The meeting has taken place. We've documented what we know about the LSi correlator above. |
As an instrument scientist on LOQ, I would like to be able to take laser measurements alongside my neutron measurements.
Notes:
The text was updated successfully, but these errors were encountered: