02-20-2012 02:58 AM
Yes I think this is exactly what I've been looking for ;-). It's particularly interesting to see the "Finding a kneedle in a haystack..." paper. I wish I had asked this question a lot earlier. It could have saved me a lot of heartache.
Looking at your code I like the professional way it is structured.
Thanks very much.
02-21-2012 01:01 AM
regarding the frequency for the filter function, I simply used the preview in the dialog to find a reasonable value. I defined a variable in the script for that frequency s that I can change the frequency without searching in the script where it is used.This is a very "low tech" approach, but sufficient for most cases.
02-21-2012 01:49 AM
As I understand things (all I ever get to see is large volumes of numbers after they have been logged) the purpose of finding the kneepoint is to provide a metric of the running clearance in a brake assembly. Running clearance refers to the physical space between the pads and the diisc.
Could I ask you another question regarding the filter frequency? Say for example that no filtering is required, how do I adapt the code?
Should LowPassFrequency be increased/decreased or are there some other subtleties that I'm missing?
If the dataset was to contain only one hyteresis curve do you envisage that the code will still be able to compute the kneepoint without any error?
Thanks in advance.
Good luck always.
02-21-2012 07:48 AM
I changed the script so that if you set LowPassFrequency to 0, the script skips the filtering step. The change is kind of brute force: If filtering is not required, the script simply copies the data. Not the most efficient way performance wise, but the smallest change to the flow in the script. And for most datasets, I assume filtering will be required.
I created a new dataset based on your example which only contains one hysteresis and the script still works. That's not really a comprehensive test. Depending on you data, it might be necessary to implement the "single hysteresis" as a special case.
Hope that helps
02-22-2012 02:12 AM
Thanks a lot for your input into this thread. It's definitely given me a lot to think about.
I found in the script I wrote myself that sometimes I would have to perform filtering on a dataset and on other times filtering would not be appropriate. The goal is to have a script which does not involve the analyst have to look at the data and produce results with a high degree of accuracy. I think the method you have implemented is probably going to be a lot more reliable than what I "cobbled" together on the fly.
The real eye-opener was seeing in print "How to find a kneedle in a haystack..."
Once again thanks very much for your input.
Good luck always.
04-10-2012 05:09 AM
H there I'm very rusty with my programming.
I'm an engineering student.
Am I right, if I say that this program can also be used in determining Voltage and Current Ct's kneepoints.
When I run your Examplke_KneePoint.vbs script, I get this error. It seems that the data varaiable should be declared, but as what and how? And where and how do I insert my own set of data to determine the knee point?
04-10-2012 06:02 AM
The script is designed to run with a newer version of DIAdem. What version are you currently using ?
"Data" is the main entry point for the scripting API to handle data in the dataportal.
04-11-2012 02:43 AM
Regarding your question how to insert your own data set, look for the following line in the script and edit it accordingly:
Alternatively a couple of lines above it you should see a line which says:
Comment out both these lines and load your dataset manually. Currently the script looks like it is designed to load a file called "knee_point_data_one_cycle.TDM"
Hope this helps.