06-09-2022 08:45 PM
@mcduff wrote:
Colleagues dislikes about TDMS - Mainly it does not fit their workflow. Some people here use Matlab, (yes, there is a reader but always seems to have problems with some files), Python (same reason as Matlab), IDL (no importer available I believe), and to a lesser extent sometimes Igor or another program. (Igor may have an importer, I know Origin does.) They want to analyze the data, not just visualize it, and often batch process the data.
I'd have to dig around to find the article. But the reader for Matlab (and probably Python) do not exactly work with the DAQmx Logging formatting of the TDMS file. But you can use LabVIEW to read the file and write it again to use the "normal" TDMS setup. But at that point, you might as well just read it and convert to whatever format your coworkers desire.
06-09-2022 10:04 PM
@crossrulz wrote:
@mcduff wrote:
Colleagues dislikes about TDMS - Mainly it does not fit their workflow. Some people here use Matlab, (yes, there is a reader but always seems to have problems with some files), Python (same reason as Matlab), IDL (no importer available I believe), and to a lesser extent sometimes Igor or another program. (Igor may have an importer, I know Origin does.) They want to analyze the data, not just visualize it, and often batch process the data.
I'd have to dig around to find the article. But the reader for Matlab (and probably Python) do not exactly work with the DAQmx Logging formatting of the TDMS file. But you can use LabVIEW to read the file and write it again to use the "normal" TDMS setup. But at that point, you might as well just read it and convert to whatever format your coworkers desire.
Don't worry about it, I think I have seen it in the past. Actually, I have had the issue with the Matlab script where the first file in a series does not work, then all subsequent files work.
There are two things that can be improved with the DAQmx logging feature, in my opinion: