DIAdem Idea Exchange

In specification for MME files is defined that "Additional descriptors" are written with "." dot as first character of descriptors.

In Diadem the properties of channel cant begin with ".", so diadem replaces it with "_", but Diadem MME data plugin loads MME files without these properties.

Could you please implement it that it will load these descriptors as well?

------

Now when i export data by MME export plugin, its doesnt collect and save Additional descriptors and after calling the function 'DataFileSave("", "MMEExport")' i must manually open each file created, parse it and add Additional descriptors by checking each line of the file. I got problem there when i got files with lot of values, because using functions "TextfileWriteLn" or methods of Scripting.FileSystemObject takes really long time.

If the data plugin export all descriptors, it would solve the problem im facing.

For example channel with 500.000 values takes minutes to "recreate" the file with just few new lines added.

For non-waveform channels that have a certain channel property populated that specifies another valid channel to use for the X-axis, it would be great if users could simply drag and drop channels into a VIEW 2D Axis System WITHOUT having to also select the x-axis channel.

(Over) Simplified logic:

When dragging a channel from the Data Portal to a 2D Axis System:

IF 'Waveform' channel property == No AND IF 'Xaxis' channel property specifies another valid channel,

THEN use this other valid channel for the X-Axis of the channel being dragged.

Example 1:

Let's say we have an internal combustion engine for which we are recording several channels at a rate of one sample per engine cycle. As the engine speed goes up or down, there is less or more time between each sample. This means we can NOT use a waveform channel. We must have an associated time channel for these several recorded channels. In this time channel, we will record a timestamp value when each engine cycle occurs.

Example of 'Xaxis' channel property value:

"Time Channels\Time Stamp Engine Cycles"

Example 2:

Let's say we are recording channels at a known rate, such as 100 Hz. A waveform would normally work for this. However, in this example, there will be gaps of no data in these data channels. These gaps may be relatively long in duration and we therefore do NOT want to record NO VALUE during this time, which would bloat our data files. We also do NOT want to put this data in separate data file nor in separate groups. This situation happens in MANY scenarios for us. For this, we must have an associated time channel for each of the data rates, such as "Time Stamp 1 Hz", "Time Stamp 10 Hz", "Time Stamp 50 Hz", and "Time Stamp 1000 Hz".

For both of these examples, plotting such non-waveform channels in a 2D Axis System could take less work on the end users' part, if we could add a little smarts to this drag-n-drop plotting operation. Implementing something like this will make creation of plots with meaningful x-axis values for non-waveform channels as easy as plot creation for waveform channels.