10-25-2023 01:44 AM
I acquire waveforms and images and need to save the raw data with their nested acquisition settings. Until now I used tdms and saved the settings as json string in a tdms parameter. Opening those files again works well as long as my application's settings cluster doesnt change.
I like to have configuration and data in one file. Any suggestions on how to achieve this more robustly regarding changing settings cluster?
10-25-2023 01:55 AM
Hi Quiztus,
@Quiztus2 wrote:
I acquire waveforms and images and need to save the raw data with their nested acquisition settings. Until now I used tdms and saved the settings as json string in a tdms parameter. Opening those files again works well as long as my application's settings cluster doesnt change.
I like to have configuration and data in one file. Any suggestions on how to achieve this more robustly regarding changing settings cluster?
I still would use TDMS files, but instead of converting your (typedefined) clusters to JSON strings I would store the cluster elements as individual properties of the TDMS group/channel.
It's a little more overhead while writing/reading, but prevents all problems with your cluster typedefinitions: you can read all properties and use default values for non-existing items…
10-25-2023 04:35 AM - edited 10-25-2023 04:37 AM
I followed your advice and it looks promising. For the sake of completeness I upload my working snippet.