The idea is to provide a "Channel concatenation" button in the default Analysis panel > Channel Functions.
After clicking this button, a dialog box should open, where the various Channels of different Channel Groups can be selected for the concatenation process. In the same dialog box, some options for the channel concatenation could be selected as well.
In this moment, some example scripts can be found in the discussion board for the concatenation of N Channels in M Groups. However, these scripts are quite cumbersome, not easy to customize, and providing too many optional features that are aiming to address shortcomings in the time or data channels to be concatenated.
It is a good practice, however, to correct first the issues in your Time and Data channels that prevent them of being concatenated properly.
The channel concatenation function would be a very useful feature, especially for engineers working with big datasets, that are increasingly recorded in contemporary data acquisition.
Typical examples of big datasets are vehicle CAN network data, recorded over an extended period of time (weeks, months).
Usually, these data are divided into multiple data files, which then need to be concatenated afterwards in order to cover a selected recording period, prior to further analysis of the data.
I am very glad that the SRS analysis function was included in DIAdem! Thanks! Now, I would really like to be able to supply my own channel of specific frequencies that I would like the SRS analysis performed at. The current implementation has the user enter the number of frequencies he wants per octave. There are occasions where I am generating an SRS from data to match an existing SRS and it would be very useful to use the same frequencies as the original. Thanks!
Add a function to setup live measurements of curve data between cursors. As the cursors move the function uses the new curve data between the cursors to immediately update the measurement field(s). This functions comes standard on most advanced digital oscilloscopes. The oscopes' usually have a measurement screen where measurement parameters are entered for the specific measurement desired. My immediate desire was just to measure RMS between verticle cursors but by no means should this function be limited to one measurement type.
I think it would be helpful to have something like this example http://www.ni.com/white-paper/3549/en (DIAdem2012 optimized Version) as user defined function (like hysteresis).
I'm new to Diadem so this may be an option that I've not discovered yet...
I have very large data files which take a couple of seconds to display on a chart. Annoyingly if I want to add an extra plot to an existing graph Diadem re-draws all the graphs, not just the new data. I have my own LabVIEW code which only plots new data whilst leaving old plots on the graph and it really speeds up the process - can you do something similar with Diadem?
Lately there has been a need by many individuals to shift data for one reason or another. Possibly the data was collected without using a trigger to synch everything or just collected with an inevitable delay.
Would R&D look into a function that could mark two points in a customer's data and then align/shift the data so a comparison may be done of one data set against another?
First, major kudos to whoever implemented the Shock Response Spectrum (SRS) in Analysis!! This is a huge step for us in the shock and vibration world! Only one small request: may we have the option of supplying our own frequency channel? Being restricted to only "frequencies per octave distance" may work for some but we have need to use different frequency spacings. Thanks!
I noticed channels can be dragged and drop everywhere but in the calculator. Ths channel list is quite OK when havin a few channel in the Data portal but becomes fast ´a waste of time on bigger projects. Allowing to drag channel in ot would make it faster to use and also a bit more user friendly.
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:). 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 ( ) you can find a link to Matlab code for the Pratt Method ( ), 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.
I am sure that this is far from a 'new idea'. I have been using DiAdem 11.1, and have not looked at the new features of 2010 yet. The new idea...use LabVIEW code to make scripts. I know LabVIEW very well, that is how I make the TDMS files; but the idea of data analysis or automation comes to a standstill when you tell me I need to learn VB to manipulate or work with the data I just gathered beyond the canned toolsets already in DiAdem. DiAdem needs to be like Teststand in this regard. You can use different code types with Teststand, and it works. And this needs to work in all the different categories of scripting or automation (Navigator, View, Analysis, etc.) Any software package NI creates should have LabVIEW as the center point, and always require seamless integration of LabVIEW code. I think that comes down to plain-jane good marketing strategy.
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.