Ventana software support forum

Can you upload your test case?

Maybe this setting is what you need?

It should be summed - I think SO was created with the mindset of policy optimization rather than calibration. A possible response would be to inflate the floor temperature in the MCMC settings to = the number of runs in the ensemble. I'll take a look at the code.

Try View>Export as svg - that will give you a vector image in .svg format.

The Action Recorder generates the needed command when you do one manual export.

You can write a .cmd script to do it using the VDF2CSV command.

No.

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.

The proximate cause of the FP error is that the real cost ratio becomes large, which causes sales to grow at an astronomical rate. The conceptualization of sales as a stock is conceptually questionable here. Consider, for example, what happens if you fix the real cost ratio at 1.1: sales would grow ...

I think 'S/1e-10/1e-10 is enough. The default assumption for off-diagonal covariance is 0. You only want to specify this term if there's plausible correlation between the noise affecting two states, which is not that common. I'm not fully up on the math, but one situation might be as follows: [stock...

You could set the driving noise for that stock to a very small value (not 0).

I think "data list" is what you want. You can automate with a command script if you're doing it repeatedly. https://www.vensim.com/documentation/vdf2dlist.html and if you want it to happen after every run, load the cmd script into the pre/post field https://www.vensim.com/documentation/pre...

You might also check out this:
https://vensim.com/video/#DS1_Discrete_Events

I'm traveling so I can't share the code until the 20th unfortunately.

Another workaround would be to change your time unit to 1 hour - then the problem of large flows per fractional time unit goes away (assuming 1hr is enough precision).

You can then define a day as an alternate TIME BASE for display on graph axes, if needed.

Multiples of 16 are expected because your time step is 1/16 day. By convention, SD flows are continuous, so 16 people/day causes an accumulation of (16 people/day) * (1/16 day) = 1 person. You can see this in the Euler update for a stock: people in ER = INTEG( admitting-discharging, ...) is implemen...

This is an example of how I'd tend to do it:

I've messaged them.

Can't run this without the data spreadsheet.

Could use units.

The downside is that Poisson/binomial processes make the model stochastic, so you need to do regular sensitivity runs to appreciate the diversity in behavior.

I think to do this right, you need to randomize the small flows rather than accumulating fractional people until you have a whole one.

Examples:
https://vensim.com/2017/01/discrete-stochastic/
https://metasd.com/2017/10/bernoulli-poisson-bar/

I think you'll find some error logs in
C:\Users\yourname\AppData\Roaming\Vensim (shorthand %AppData%\Vensim )

You've found a glitch that will be fixed in the upcoming release. You can't literally write, Price[sector,sector] = blabla but you can define subscript equivalents, fromSector <-> sector toSector <-> sector and then write, Price[ fromSector, toSector ] = blabla However, the equation editor glitch cu...

IF THEN ELSE(fluid=1, fluid1 lookup(input), fluid2 lookup(input))

X IF MISSING is also more convenient if you have multiple data inputs in the equation.