Does Kalman combined with Command Script only handle 16 datasets? (BUG?)

[aliakhavan89]

I'm running a script like this:

Code: Select all

SPECIAL>NOINTERACTION
SPECIAL>LOADMODEL|MG_Kalman.mdl
SIMULATE>DATA|data_v01.vdfx
SIMULATE>RUNNAME|Powell_kalman_v01
SIMULATE>OPTPARM|Powell_Settings_kalman.voc
SIMULATE>PAYOFF|Payoff_kalman.vpd
MENU>RUN_OPTIMIZE|o
MENU>EXIT

SIMULATE>DATA|data_v02.vdfx
SIMULATE>RUNNAME|Powell_kalman_v02
SIMULATE>OPTPARM|Powell_Settings_kalman.voc
SIMULATE>PAYOFF|Payoff_kalman.vpd
MENU>RUN_OPTIMIZE|o
MENU>EXIT

...

going to 100 detests, and I've noticed the Vensim quits entirely after each batch of 16 datasets. it could be related to the max datasets being loaded simultaneously, and it only happens with kalman. I'm now running the cmds in batches of 16 as a workaround (instead of 1 to 100), hoping to avoid the issue, but it would be very helpful if this gets fixed in the source code if it is causing the problem.

[tomfid]

There's a 16-dataset limit for loading into the dataset control. When that's hit, there should be a warning, not a crash.

If you add a CLEARRUNS statement intermittently that should solve the problem.

[aliakhavan89]

Thanks, Tom. The workaround I had worked perfectly, but CLEARRUNS should speed it up even further. I've never seen this behavior when running MCMC without filtering (on single and MC) so I thought it could be related to Kalman (on single core). Thanks again.