software breakout session: fpa related opus issues michael j. nasse, carol hirschmugl

6
Software breakout session: Software breakout session: FPA related OPUS issues FPA related OPUS issues Michael J. Nasse , Carol Hirschmugl

Upload: helena-hubbard

Post on 20-Jan-2016

220 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Software breakout session: FPA related OPUS issues Michael J. Nasse, Carol Hirschmugl

Software breakout session: Software breakout session: FPA related OPUS issuesFPA related OPUS issues

Michael J. Nasse, Carol Hirschmugl

Page 2: Software breakout session: FPA related OPUS issues Michael J. Nasse, Carol Hirschmugl

2

• Extremely sensitive to disturbances during acquisition

• Don’t move the mouse

• Network card to outside world disabled

• No antivirus running in background

• Reference interferogram not saved

• Mirror velocity is silently set to 80% of FPA frame rate in Video Assisted Mode

• FPA mosaic size limited: max: 2x3 with 96x96 pixels, 4 cm-1 resolution (filesize < 2GB), but programs such as ENVI can be used

• FPA parameters not saved in OPUS files (gain, integration time, offset, etc.)

• 128x128 pixels does not work in 4 cm-1 resolution: Out of Memory even with 4GB

• FPA electronics temperature readout fails

• OPUS runs under Vista (even 64bit) for analysis, but can’t run hardware devices, so that it can’t be used for the acquisition computer

Bruker OPUS issues (newest version: 6.5 SP 1 Build: 6, 5, 92 (20080204))

Page 3: Software breakout session: FPA related OPUS issues Michael J. Nasse, Carol Hirschmugl

3

Computer equipment

Brukerinstruments

Acquisition computer(32bit XP, 4 GB RAM)

Networkcard 1

Analysis computer(64bit Vista, 8 cores,

8 GB RAM, 3 TB hard disk)

GigabitNetwork

card 2

GigabitNetwork

card 1

Private network

Page 4: Software breakout session: FPA related OPUS issues Michael J. Nasse, Carol Hirschmugl

4

Automatic data transfer: acquisition → analysis computer

We use a batch file to transfer our data from the acquisition computer to the analysis computer. After acquiring data in OPUS we immediately unload the file in OPUS(we don’t look at the data on the analysis computer, we just acquire it there, that helpsto keep OPUS stable) and run the batch file. After that, the computer is ready to take data again (OPUS can keep running in the background as long as the files to tranferare unloaded). The batch file does the following:1.Enable network connection between acquisition computer and analysis computer(this does the same as “disable” in the Windows Device Manager)2.Transfer files with your favorite synchronization program, we use GoodSync (Shareware), but Microsoft has a free program called SyncToy or you can use the free FreeFileSync3.Disable the network connection again, so that you are ready to take data again

Here is the code:

devcon enable *SUBSYS_13768086"C:\Program Files\Siber Systems\GoodSync\GoodSync.exe" /miniwin /exit sync /alldevcon disable *SUBSYS_13768086

The *SUBSYS… has to be replaced with the code corresponding to your specific network card. See online documentation for devcon.exe. The link for devcon is below.

• FreeFileSync: http://sourceforge.net/projects/freefilesync/• SyncToy: http://www.microsoft.com/Downloads/details.aspx?familyid=C26EFA36-98E0-4EE9-A7C5-98D0592D8C52&displaylang=en• Devcon: http://support.microsoft.com/kb/311272

Page 5: Software breakout session: FPA related OPUS issues Michael J. Nasse, Carol Hirschmugl

5

Bruker OPUS database

Page 6: Software breakout session: FPA related OPUS issues Michael J. Nasse, Carol Hirschmugl

6

Bruker OPUS database

SFM: Sample FormSNM: Sample Name