how does a global variable affect the runtime of optimisation-function fminsearch?

[tracetemp]

Hi,

my function "fmintest" needs 254s ~ 4min to finish calculation in Mathscript, while Matlab needs
3s!!! I need the sorfware for data processing in a real time measuring system, where the calculation have to be done within 5 seconds.

In the Mathscript-help I found the following (global -> details):

If you call this function from a MathScript Node, LabVIEW operates with slower run-time performance for the MathScript Node. To optimize the performance of the MathScript Node, remove this function from scripts.

How can I remove needed global variables in the fminsearch function handle? Is the system faster if I would/can remove the global variables?

How can I avoid Mathscript-breakdown after saving changes to m-files and restarting them again?

regards

[MikeS81]

please start only one thread per topic. duplicate post -- continue here

[RamonaL]

Hi,

can you provid a VI and not only your m-files? It will be easier to help you!

Can the customer provide a VI that demonstrates this behavior, rather than just providing the m files?

Also, the Help file says fminsearch is not supported by the LabVIEW Run Time engine, so please take that in mind. If you want to build an application you cant use this function.

Regards, RMathews