Search results won't display Channel.Maximum or Channel.Minimum

[GS]

I did a Search Channels on a given channel name. I got the desired results except when I display Channel.Maximum (or minimum) in the search results I get NOVALUE for the results. However I can display the max or min for a file in the data portal. Why won't the search return the values? I watched one of the demo videos and it looked like it worked fine there.

George

[winner]

Hi George

That is no standard function of DIAdem. But the menu is available after using the menu Help>>Examples and starting the Example "New Example for Version 10.0">>"Shortcut menu for the Searchresultlist of the Datafinder"

Hope this helps.

Winfried

[GS]

I get the Channel.Maximum for the example you mentioned, but when I go back to my data I get NOVALUE again for Channel.Maximum.

Why would that be presented as a search property if you can't search on it?

George

[winner]

Hi George

It seems that the characterist values are not calculated for that datasets. I suggest that you do not use TDM data. Most dataplugins do not calculate that characteristic values.

Winfried

[GS]

How does the example get the Channel.Maximum data?

I'm using TDMS data. I thought that was the recommended data type to use now. If DIAdem doesn't calculate characteristic values for the recommended data type it seems like it really should.

Can someone please explain why the Channel. Maximum and Channel.Minimum show up as properties available for search when searching a Channel if DIAdem doesn't intent to return a value? I'm a little disheartened now. I thought this search engine was going to be useful.

George

[Brad_Turpin]

Hi George,

There are a number of Channel properties that DIAdem calculates automatically when a data set is loaded into the Data Portal:

Minimum

Maximum

NoValueKey

Monotony

SourceDataFileName

SourceDataFilePath

      :           :          :

These properties can exist in the data file but often do not.  Any TDM file will automatically have the Minimum and Maximum properties assigned in the data file, but these are not automatically assigned in TDMS files or DataPlugin files.  You can, of course, always calculate any properties and save them to the file at the same time as you're saving the original data-- then they will be available for searching.  The DataFinder will only return search results if the property exists in the data file and has a value assigned to it.

For the particular case of the Minimum and Maximum properties, these are standard properties that are automatically optimized by the DataFinder, so these names show up in the property list even when there are no Minimum or Maximum properties in your search files, just like the annoying "RegisterInt#", "RegisterTxt#", "RegisterVal#" properties.

If you load the data file into DIAdem, then re-save it over the original data file, all these automatically calculated "Data Portal" properties are then saved to the data file and are then available for searching in the DataFinder.

Hope that clears things up,
Brad Turpin
DIAdem Product Support Engineer
National Instuments

[GS]

Thanks. That clears it up. Not really what I wanted to hear, but at least I understand now. Guess I'll have to store more data.

George

[Craig T]

I had the same problem and this thread answered my basic question.  Would you provide a little more information about how to save the maximum and minimum properties when the TDMS file is created?  I'm using LabView to create the TDMS file and wonder if there is a function in LabView to store these properties.

-Craig

[GS]

Use the TDMS Set Properties VI to store Maximum and Minimum. See the attached VI for an example.

George