LabVIEW
levenberg marquardt slower in LV7
During the conversion, were the L-M vi's converted to LV7 or fully replaced? There appear to be a few changes between 6.1 & 7 LM vis... several of the lower level subvi's go changed to CIN's, vs pure LV. You may want to see if it's just LV 7 running slower (LV 7 uses more resources than 6 in general... I've got both on an old 400 MHz AMD w/ 96 Mb of RAM... 6.1 cruises... 7 is a drag).
You might want to try using the LM vi's from 6.1 (do a save out w/ options to save all vi's), to see if it's LV7 itself or just the newer LM vis that's slogging it down.
You might want to try using the LM vi's from 6.1 (do a save out w/ options to save all vi's), to see if it's LV7 itself or just the newer LM vis that's slogging it down.
It sounds like you have more than enough power:
http://ni.com/labview/requirements.htm
although it could be the OS...
Did you just replace the top level L-M vi's or all of them? Like I said, the majority of the changes appeared to be buried in the lowest level subvis.
You may want to try using the vi profiler to see where the majority of the time is being spent and isolate that vi. (Tools->advanced->Profile vis... at least in LV 6.1 I'm not at a station w/ LV7 presently). You'll want to select Timing details. See if any vi is running a long time or an excessive amount of calls and compare this vi to the LV6 version. If it's different, replace w/ the LV6 version. If it still slogs... hmmmm... maybe format and do a clean LV7 instal
l? 🙂
Lemme know what happens, since I use L-M frequently... just not in LV7 yet.
http://ni.com/labview/requirements.htm
although it could be the OS...
Did you just replace the top level L-M vi's or all of them? Like I said, the majority of the changes appeared to be buried in the lowest level subvis.
You may want to try using the vi profiler to see where the majority of the time is being spent and isolate that vi. (Tools->advanced->Profile vis... at least in LV 6.1 I'm not at a station w/ LV7 presently). You'll want to select Timing details. See if any vi is running a long time or an excessive amount of calls and compare this vi to the LV6 version. If it's different, replace w/ the LV6 version. If it still slogs... hmmmm... maybe format and do a clean LV7 instal
l? 🙂
Lemme know what happens, since I use L-M frequently... just not in LV7 yet.
Ruud,
I just ran the standard Parameter Fit LM.vi (search examples for levenberg) on both LV6.1 and 7 on the same computer (400 MHz AMD, 96 Mb RAM, Win XP Pro) with the default inputs, except I set the total pts to 2000. Both gave equivalent results in 24 s.
Perhaps it's some other conflict on your setup or your modified vi. You may want to run the same experiment to see if it truly is the L-M routine or something else.
I just ran the standard Parameter Fit LM.vi (search examples for levenberg) on both LV6.1 and 7 on the same computer (400 MHz AMD, 96 Mb RAM, Win XP Pro) with the default inputs, except I set the total pts to 2000. Both gave equivalent results in 24 s.
Perhaps it's some other conflict on your setup or your modified vi. You may want to run the same experiment to see if it truly is the L-M routine or something else.
