Changing the order of opened scripts (tabs) manually would be awesome feature. Now its a bit frustrating when u got scripts in different folders and you would like to change the order when you work on more than one script.
At present there are a number of ways to apply Y-Axes to a collection of curves on a 2D Curve chart, as shown:
But my colleagues and I think it would be useful if there could be a button that generated an axis per unit type (e.g. Volts, Amps, DegC). That way like curves can be compared on the same axis without the distortion of larger number curves skewing the perspective of the axis.
Make an option to have REPORT auto-scaling work like VIEW:
VIEW updates the Y-Axis range to be appropriate for the presently visible data when Y-Axis auto-scaling is on and a manual X-Axis range is selected.
REPORT presently maintains the Y-Axis scale of the entire Y-Axis channel's range regardless of X-Axis range selection.
The current behavior requires the user to manually scale both the X and Y axis, when manually selecting an X-Axis range on a highly variable data set. In my case, I'm setting the X-Axis range in a script (last 30 days), but will now also have to determine and set a manual Y-Axis range for the 30 day window of X-Axis values.
I put "Optional" in the description because sometimes the current behavior is desired (if the user wishes to maintain a consistent Y-Axis at all times).
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.
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"
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.
When working in DIAdem SCRIPT, it is often necessary to work on more than one file at once. The way this is implemented at the moment is with tabs:
However, it can be quite tedious to switch back and forth between 2 scripts for things like copy/pasting, comparing code or simply editing code on 2 files concurrently.
My suggestion would be for a SCRIPT editor with split screen functionality, roughly like this:
With many users working with widescreens today, this would better make use of screen real-estate.
In VIEW tab, when working with 2D-graphs some times it is useful to change the line width, the background color, the axis color, the line style... as in the REPORTER tab because for analyzing and studying the data before having the final data to report, the VIEW tab offers much more comfort. The Curve and Axis Definition in REPORT can replace the current 2D Axis System Display window:
There should be an integrated feature in DIAdem to create Boxplots. You can already find the min Q1 median Q3 and max in the analysis portion. I have not been able to find a good way to make a boxplot in DIAdem, and it's a very clunky process in excell. I've had to use DIAdem to process data then export the interested channels to excel to make acutal boxplots, which still requires a lot of manipulation.
To do this in excel you create a modified boxplot based on the difference in the five number summary. These numbers are put into a stacked boxplot, then the settings are played with to give the finalized look of a box plot.
The Differences plotted as a stacked bar plot looks like the following with borders on and the bottom and top sections made invisible with error bars to mark the min and max values
There should be a way to do a similar process, or even an automatic box plot creator in DIAdem.
Let me know what you think,
DIAdem has a data reduction option which can used in DIAdem Navigator to reduce the data beeing loaded but if it is up to do it after teh loading one needs to write a script or formula to do it.
I think it would be a great interest to have such a simple functionality in DIAdem Analysis too that cna be applied to the internal data (i.e. results of calculations).
it would be helpful to have the following option in the View:
In case of moving the cursor through the 2D-Graph, I would like to have the table scrolling automatically the same way with highlightning the values of the cursors position.
A typically Diadem workflow consists of at least two parts: Navigator and View or Navigator and Report.
I always have to save and load every single file separately.
I wish I could have a button "Save Project" where all files of the actual project were saved in a single package and a similar "Open Project" Button.
The package can be a Zip-File that contains all the *.TDM, *.TDX; *.TDV, *.TDR and *.VBS files of the open project.
It's very common you need to do a presentation with several information and if you can put a video playing a synchronized video, map, audio and data graphs, like DIAdem VIEW do, your presentation will be cause a excellent impression. To do this today you need a capture screen toll, If DIAdem have a native tool to do this it would be great.
I'd like to propose a few improvements to the zoom functionality in DIAdem VIEW that are sorely missing usability-wise:
I think that for points 2 and 3 there are several ways this could be done. I think the focus should be on usability. The user needs to be able to navigate the data as quickly and as efficiently as possible and the current zoom implementation is clearly impractical for many users.
there is only one manual scale to be set in a 2D graph in VIEW Panel. It would be a great idea if setting manual scales would allow you to set seperate scales for seperate plots on one graph.
First of all, I really like the new ParallelProcessing feature which allows great time savings. The thing that sometimes makes it a bit cumbersome is that when you want to use it, you always have to define at least two additional script files, the worker script and the callback script. This is especially annoying as the SCRIPT-view is not particularly user-friendly when you work on different scripts at the same time.
An example is an evaluation script where you want to filter a series of rather long channels. There is potential for huge time saving doing it in parallel. Today, you would have to create a separate worker script around the ChnFiltCalc-function and a separate callback script to pass the filtered channel back into the main data portal. If you now have several of those smaller operations distributetd over your main evaluation script, you will end up with a large number of scripts unless you come up with a smart way to pack everything into just a pair of those.
What I propose is a sub-environment for worker and callback (like function or sub), so that you can pass subtasks to the workers from within the main script, e.g. without the need to create additional VBS-files.
Referring to the example above where oMyEvalChn is one of the signals that I want to filter, it could maybe look like this:
Worker MyWorkerScript1(oChn) Call ChnFiltCalc(...oChn...) Callback = ChnToArray("/Filtered") End Worker Call oMyWorker.Run(MyWorkerScript1, oMyEvalChn)
Being able to create a report with different page sizes
At the worksheet parameters you can choose to use local page format, but you can only select the orientation (portrait or landscape). I Propose to add page size property when you select to use local page format, being able to indicate Height, Width or ratio.
I have a customer who would like to use 3D Axis systems on VIEW section.
This function is for Report section.
As you can see below.
He would like to realize this function on VIEW section as well.
I wish this function would be made for VIEW section as well.
My suggestion concern the SCRIPT tab. I think that it is necessary to implement a real automatic indentation function as you can find in most of Integrated Development Environment.
Indeed, when you write a VBS code, you have to structure your code manually while DIAdem could structure it automatically.
For instance, after an "if" and until "end if" DIAdem could insert a tabulation.
Rather than a channel that has a "fixed" value (numeric or string), this new "calculation channel" type would be a function of other channels. Currently, if Channel3 = Channel1 + Channel2, and then I change the values for either Channel1 or Channel2, I have to re-execute the calculation
ChnCalculate("Ch(""Channel3"") = Ch(""Channel1"") + Ch(""Channel2"")")
Now, if there was a "calculation channel" where I could define Channel 3 as "Channel1 + Channel2", I wouldn't need to perform this re-execution!
Another way to explain is to have a channel that works like Excel calculation cells. The cell calculation stays the same, and when the input cells change, the result cell is automatically updated.
I'm not sure if I explained this well, please ask for clarification if necessary.
The DIAdem R&D team is committed to reviewing every idea submitted via the DIAdem Idea Exchange. However, we cannot guarantee the implementation of any DIAdem Idea Exchange submission until further documented.