DIAdem Idea Exchange

I've noticed that the easiest way to relate a channel calculation back to the original channel is to append to the channel name:

iH_EngSpeed_rpm

iH_EngSpeed_rpm_RegX

iH_EngSpeed_rpm_RegY

iH_EngSpeed_rpm_1

iH_EngSpeed_rpm_2

iH_EngSpeed_rpm_Filtered

Filtering for *engspeed, or *engspeed_rpm will return all of the above channels, but in my experience I rarely want to see all the additional channels...With enough channels, it can effectively obscure the channel you're looking for!

The simplest way I can think of to obscure these with the current functionality would be to have a stop character ("\"?) to prevent the filter from grabbing anything beyond that point:

*EngSpeed_rpm\ would return anything ending in *EngSpeed_rpm

Another way would be to get rid of the assumed * at the end of the filter, forcing people to put one on themselves when necessary (but that would be changing the current functionality and would likely confuse users at first):

*Engspeed_rpm would return anything ending in *EngSpeed_rpm

*EngSpeed_rpm* would return everything with EngSpeed_rpm inside it

This would also be nice for looking for channels that end in something, like anything ending in *nm\ rather than anything with nm in the name...

With diadem it is not easy to break axis. But sometimes it would be really helpful to be able to break especially the y-axis to make some diagrams much more easy to understand... this is e.g. possible with Origin or other programs and sometimes very helpful - it would be great to implement this feature in Diadem report and view also

Right now, you can only delete one page at a time (using delete or the "manage...") feature.

Why cant I just select multiple pages and "delete all".  Or in the "manage..." feature, why cant I select more than one at a time (otherwise what is the little check box for?) and delete all?

Would be very helpful to add these features

Hi,

I quite often use a 2nd y-axis in a 2D-diagram. In order to improve the visibility I like to use the same grid for the first and second axis but different scaling. The 2nd y-axis is set to automatic scaling because of changing data ranges. Unfortunately the scaling range used for the second y-axis is completely unpredictable. Therefore the scale is way to big and the setting has to be corrected manually. This is very annoying, because the automatic choice is often not very logical and this behavior is not documented at all.

regards

SvenB

Hey,

A feature I have been asked about many times is what if I want to give another user a report to add to theirs.  ATM you have to move the TDR file and a data file with the correct channels.  Making this simpler would be good.  Perhaps even a function to package data required for report so that someone else can open the TDR and TDM and know everything will be in the right place.

Cheers,

James

I would like this for custom pinning functions specific to our needs (like pin all channels of same name) and for the calculation manager (if a calculation's equation is defined as a channel property, re-calculate it or bring up the calculation manager, etc.)

For example, if the Waveform X-Step Width of a waveform channel is "500", DIAdem VIEW synchronization - using the default playback rate of "1" - will playback one value every 500 seconds, as though it is assuming that the channel was recorded with one data point every 500 seconds.  If you set the Waveform X-Unit to "ms" (because you realize your data was recorded every 500 milliseconds), the playback rate of VIEW synchronization is still one value every 500 seconds.  The only way to adjust the playback speed is to adjust the VIEW synchronization playback rate.  It would be nice if VIEW synchronization playback respected channel units.

I would like to have a option to set default properties.

  For example: I need default 0.7 curve width, change default color scheme for axis system, etc. On dialog boxes should be a Set as default button.

I would like to change multiple curve properties at once.

  Means to select several curves and switch display mode to spikes, or set another line style, etc.

Hi all!!

I would like to be able to view the date of a time channel in a 2D Axis System. I know I can do it transfering it to DIAdem REPORT and then selecting the desired format in the axis, but I want to do it on VIEW.

I have tried with a waveform channel, a channel made of time stamps... I think it would a great feature!!

Thanks!!

It should be possible to save .SUD dialogs for previous version so you could open Diadem 2010 Dialogs in Diadem 11.1

My DIAdem users do a lot with mechanical vibration and find it very useful to plot multiple data sets on a tripartite graph.  I have looked at implementing this in DIAdem without success.  I have seen it done using Matlab, and, although the author had to write the graphing routine explicitly himself in M-script, at least the basic graphing environment gave him the tools to do so.  I realize this is a rather esoteric request, but it would be helpful in our work. 

Take a look at the enclosed for a classic example, ploting shock spectra with axes of acceleration, displacement, frequency, and velocity.  The tripartite graph is slowly becoming more popular in other plotting packages.  I'd love to be able to keep up with them in DIAdem.  Thanks!

I often create custom reports that have a box drawn "FreeFrame" with a text box "FreeText" inside. In some cases, I put too many characters in the text box and it breaks the bounds of the box. It is difficult to predict the size of the text box unless you use a font like courier. I would like the property of size added to the report text box.

• The use case is update the text box with the text.
•  Check the rendered text box size.
• Adjust font size if the box exceeds the size of the surrounding box.

Title says it all.  I don't like waiting while files load.  Can this process be threaded?

Hi,

I´d like to know how many people would like to see structured error and warning handling in dataplugins.

Just having the ErrorRaise method doesn´t suit my needs of get some detailed informations when just a warning would be sufficient.

How about having a RaiseWarning method?

and

a kind of UI to query the datafinder of files and paths where warnings and erros occur

br,

thomas

Substantially beef up the ability to pipe data from labview into diadem.

• Importing text arrays/tables
• importing graphs, with annotations
• greater control over text values : make them easily reordered and renamed, perhaps make them polymorphic to allow cluster usage, that way order isn't important and changes to the layout won't change the location of the variable in the array/cluster

German

-------------------------------------------------------------------------

Es ist nicht möglich die Graphenreihenfolge in einem Report zu ändern wenn man mehrere Y Achsen hat!!!!

Die Graphenreihenfolge lässt sich nicht durch die Hoch und Runter Pfeile in der Achsendefinition ändern.

Das ist wirklich schlecht und sehr unkomfortabel!

Sollte dringend und sehr schnell geändert werden ist ein echtes Ärgernis wenn man mit Daten arbeitet bei denen man mal kurz die Reihenfolge ändern will weil diese sich ungeschickt überschneiden!

Ein Programm wie Diadem das das mit einer Achse kann sollte das auch unbedingt mit mehreren Achsen können ( das ist mal ein richtig fetter Käfer   ....

Grüße Stephan

//English

--------------------------------------------------------------------------

It is not possible to change the graphs order in a report if you have different Y-Axis without changing the Y-Axis.

You can not change the Order with using the Up and down buttons  in the Axisdefinition (don't works).

That is really worse and very uncomfortable!!!!

Should be changed very fast!!!!

A Programm like Diadem that manage this in one Axis should manage this always in two three....four.... Axis too.!!!!!

Greets Stephan

Whatever method is used in the "Calculate Circle Approximation" does not do well if there are not points around an arc which is close to 360°.  I suspect the Kasa method, or something similar is used (link to Matlab code:  http://blogs.mathworks.com/pick/2008/03/14/fitting-a-circle-easily/).  This method works well if there are points all around the 360° of a circle, but not so well if the data only covers an arc.  If you go to Chernov's page ( http://www.math.uab.edu/~chernov/cl/) you can find a link to Matlab code for the Pratt Method ( http://www.math.uab.edu/~chernov/cl/MATLABcircle.html), which works great for arcs.  Although I have not tested it, I suspect the Pratt Method works well for data distributed across 360° as well.  If that is the case, I would recommend that you either add an "arc fitting" function using the Pratt Method or replace the method used in the "Calculate Circle Approximation" with the Pratt Method.

Attached is an image of an example of latitude and longitude data.  Note that, because this is lat & lon data, the circles look like ovals, but they really are circles.  I was trying to fit a circle to the red curve between the two vertical black cursor lines.  The green circle was obtained by using the "Calculate Circle Approximation" function while the blue circle was calculated via the Pratt Method.