At 18:05 -0500 01/07/2004, Daniel Flatin wrote: >David Thomson wrote: > > A colleague of mine wants to write data from LabVIEW into files of >>Igor waves to analyze in Igor. I told him that I could find such >>conversion VI's, as I had used them years ago. Alas, all I could find >>are LV 3.0 VIs. Nothing in the Dev Zone. >> Does anyone know of more recent LV-Igor VI's that are available? > >I remember those VI's. They wrote data to an Igor binary format. Unless you are >limited by disk >speed or disk space, you might want to consider a simple tab delimited file or maybe >an Igor text >file which can contain embedded Igor commands. Igor can be configured to watch a >batch file and >process it when the modification timestamp changes, making it easy to have concurrent >data collection >and analysis. You could also do this with AppleScript, and I am sure there is some >other option on >that other platform, but Igor's batch approach relieves you of having to manage a >third programming >environment. Also note that with the embedded commands in an Igor text file you can >customize the >processing for each data file. The advantage of using the text route is that all >your code can be in >G or in Igor's scripting language, ensuring both human readability and platform >portability.
I was looking into this a little while ago. I was thinking that the best way to do this would be Apple events to send a script to Igor to setup a FIFO and the named channels and then have LabVIEW pipe data into the FIFO. What would be really cool is to pipe data into the FIFO from a named pipe. A background task in IGOR could read data from the pipe (in either ascii or binary) and place it in the fifo. LabVIEW could read the instruments and write the data to the named pipe as it is collected, closing the pipe when it is done. -Scott
