Ventana software support forum

It's a separately priced item (email us for a quote). However, it may not immediately help you - its multithreading supports server usage, but doesn't paralellize the opt/sensi algorithms.

The advance in hardware performance is argueably only part of the reason software has gotten faster, the other side to it being algorithmic advances. To my knowledge, Ventity for example, will follow modern solver strategies and use a variable time step, loosely speaking making "bigger steps&q...

I'll have to take a look at the code - I suspect that the limit only gets checked between passes, not at every single iteration, in order to avoid a lot of if-then testing when normally not needed.

Some thoughts on model speed here: http://blog.metasd.com/2011/01/optimizing-vensim-models/ CPU speed hasn't improved that much with respect to what matters for Vensim, https://www.cpubenchmark.net/singleThread.html However, if your existing machine is not an i7 with a high clock speed (>3GHz), ther...

I think I've found the bug - should be OK in the next release.

FWIW, with SHOWMACRO|1 I do get consistent behavior (showing "#modelFractionalRate>CONTINUOUSRATE#" from either end).

There is an inconsistency for SHOWMACRO|0 - for some reason it doesn't suppress the macro variable in the uses direction.

Reorder your dimensions as x[Range2-element1,Range1] - it always iterates over the last dimensions first, so this should be the same as before.

I'd try SHOWMACRO|1 - in the meantime I'll take a look in the debugger.

NewModel_Oct27b-restore3.mdl NewModel_Oct15-Reorg.mdl The bad news: I still don't know why this happened. The good news: I was able to restore the diagram from the Oct_15 version. First, I edited to the 15 file to break up the large diagram into several chunks. Then, using a text editor, I copied t...

You might try including an .ini file in the .vpm that you're feeding to the .dll, with Tools>Options>Settings>Show Macro Variables set. My first guess would be that it's set to Hide (which is the default), but the Uses call is forgetting to check the attribute. Otherwise I'll have to take a look in ...

The 22b version looks corrupted as well. Only about 10-20% of the first Reservoir view loads. It's still not clear what the problem really is. The diagram is large, but I've seen bigger, so I don't think that's the issue. Generally, switching back and forth between text and sketch view can cause sma...

I can see the problem, but not sure how it happened. Do you have any earlier versions, in which they're still present on the diagram, that we could compare?

NobugToo.mdl Good question. The difference is in the initialization. See attached, to which I've added an instance of the DELAY1i function, which corresponds with your explicit structure. The simple DELAY1 function is initialized in equilibrium, so that the initial outflow equals the initial inflow...

I can't replicate this - it works fine for me. Usually this kind of thing indicates a failure to find the dataset, or a bad/empty dataset. Where is the model file when you're _not_ running it in the Samples directory? You could try pinning your custom graph on the sketch as an I/O object, and see if...

You can open two instances of the application and run independently in those, but they won't have any connection.

We don't generally permit this because it bypasses the license agreement, but if you're setting up a computer lab, contact us at vensim@vensim.com and we may be able to work it out.

A small word of caution: A formulation that tests for Time = Value can fail unexpectedly due to roundoff error, especially when TIME STEP is not a power of 2. To protect against this, you can check against Value <= Time < Value + TIME STEP, or use the PULSE function with width TIME STEP as your even...

Also, using "1" for the runname is theoretically OK, but potentially troublesome, because that means your vdf will be named 1.vdf, which might have side effects. Can't say as I don't do it.

It seems to have died for no reason before the last 26 mails went out, and you were among the unlucky. Sorry. Should come now.

Strange. The server thinks the announcement went out. I'll check the details, and forward to both of you separately.

SEED=0 is new, with the new random number generator in 6.3. http://www.vensim.com/documentation/optimizationoptions.htm?zoom_highlightsub=seed Note that random number stream IDs and NOISE SEED within a model behave differently. http://www.vensim.com/documentation/noise_seed.htm?zoom_highlightsub=seed

You missed something ... Did you put yourself on the list at ventity.biz? I'll check, but take a look in your spam folder perhaps.

Are you using a recent version? There were some problems in the ODBC example prior to 6.2 or 6.3, as I recall.

I think you don't want RESUME; that resumes at a time. http://www.vensim.com/documentation/25345.htm Instead you can either use BASED|previousrun.vdf or READCIN|previousrun.out (BASED expects a vdf and is probably simpler if there are other change inputs; otherwise you'd have to use READCIN/ADDCIN t...

it would be nice if there were a condition which would make Vensim always use a different seed when beginning an optimization

There is - set the :SEED to 0.