Updating the VIs means a lot of work, but what are the benefits? A slightly slimmer VI is none in my opinion and I cannot think of an Igor feature, that is not already supported. At the time I wrote the VIs I looked about the old VIs of Gary Johnson that was written for Igor 4 where Igor waves had only one dimension. There is a very good Igor xop that can read hdf5 files. I know of other people who use the hdf5 file format for this purpose. Not being able to write to an Igor binary wave continously is a limitation of this file format you have to deal with. The reduced scattering datasets were analyzed using SasView 5.0. If you insert the polymorphic VI in your program, LabView will replace it with the specific VI that is required for the data array you connected. data was placed on absolute intensity scale.5 The reduction of raw USAXS data was performed using the Indra package within the Igor Pro 8.04 (Wavemetrics, Inc.) environment. As soon as the LV array reaches this limit, you can save it to disk and start again. Referring to your example: I think 50 MB of data is not very much. Igor binary waves are not suited for continous acquisition, because you have to know not only the length of the wave but also each value in order to calculate the checksum which is required for a valid file. Maybe using classes instead of polymorphic VIs. Any thoughts on this?Īlso, I think that the program as it is can probably stand to be updated. This would be problematic as we might run into some memory issues if we just preallocate a huge chunk of memory before hand. The one gotcha seems to be that you need to know the size of the wave before we actually write the wave. I think this is possible, but I haven't really delved into this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |