Ventana software support forum

If your model is small, hitting Model>Simulate may perform a run so fast that you can't see it.

Reading and writing .cin files is not intended to be enabled in the Model Reader.

Correct - the problem was introduced in 5.11 and is now fixed in 6.0.

READCIN commands should be sticky, so that the setting applies to subsequent runs. However, issuing another READCIN, or a READRUNCHG or LOADMODEL, will overwrite the READCIN setting.

Those are workbench graphs, so they autoscale their ranges. You can set the ranges with a custom graph if you need more control. See the User Guide, Chapter 10 for an example.

We haven't changed anything about external functions in 6.0 so whatever worked before should still work - if not, an example might help us diagnose the problem.

You can use string variables to accomplish this. For example: vehicle stock[Region,Mode]:=get xls data('?filename',Region Sheet Name[region],Time Column,Mode Range Start[Mode]) Region Sheet Name[region] :IS: 'regiona' , 'regionb' , ... Time Column :IS: ' ... ' Mode Range Start[mode] :IS: ' ... ' You...

I can reproduce your problem. I'll take a look in the debugger and see if we can issue a fix soon.

Tom

Are you using 5.11a? There was a problem (briefly) in one earlier version.

Can you describe the problem?

Generally there should be no differences between integer and floating point operations, because integers are stored as floats (or doubles) in Vensim anyway. However, one possible operation that will cause trouble is a negative number to a non-integral power, like (-7.5)^2.334. In your sensitivity co...

You're mixing two approaches here. The .cin file format can be loaded at runtime (Model>Simulate... and name the .cin file on the Changes tab using Load Changes From...). In a venapp, you would use SIMULATE>READCIN and ADDCIN. GET DIRECT calls will execute without specifying a .cin file. Normally th...

There was a bug in the output dialog in the initial release - you might want to download the latest 6.0.0.1 which was posted last Thursday or so.

Tom

To simplify maintenance a bit, you can build up your ranges hierarchically, like a : a1,a2 b : (b1-b10) a and b : a, b This really only makes sense if a and b represent subsets of the same kind of thing, like cities in France, and cities in England. If what you're really after is a two-dimensional m...

In other words
If you're running with Euler integration, you can use SMOOTH in place of DELAY FIXED.

The scripted editing of the mdl approach would not work for interactive changes, but if the models can be generated in advance, you could manually package the results. However, this method is cumbersome, so I would not recommend it if there is another viable option. The basic idea is to write some k...

Constants that are imported from GET XLS CONSTANTS should work in synthesim, at least in recent versions of Vensim. (For example, running the GET XLS CONSTANTS sample model linked in the Functions section of the Reference Manual, all of the constants are editable). The same should be true for .cin f...

The other obvious choice is gcc, which works fine on Mac & Linux. I have no personal experience with it on Windows though.

If it's possible to post a model that demonstrates the error, that's always helpful. Thanks.

If I follow your requirements, you'd like to distribute the model without a linked Excel file, by instead embedding the constant/lookup changes in the model. Are you avoiding the Excel linkage to keep things simple (one file), or to avoid the user expense of acquiring Excel, or some other reason? If...

A likely candidate: on 64 bit systems, viz studio will be in C:\Program Files (x86) rather than C:\Program Files.

Have you checked http://blog.metasd.com/2011/06/setting-up-vensim-compiled-simulation-on-windows/ ? The most likely error is a path problem - perhaps your MSVC 2010 installed to a path that's a bit different from that in mdl.bat. I'd check that first. Specifically, you need the CL command (cl.exe) t...

It would take an external function to do this, which is serious programming.

A simpler approach is to write your output to an Excel-readable file (i.e. use VDF2TAB or VDF2XLS), and link your spreadsheet to that.

That sample model doesn't use aliases, so you'll need to modify the equations first. For each GET XLS call that references 'simpleInputs.xlsx' you need to replace the reference with an alias like '?input' and then define the alias to point to your spreadsheet by running the model or using Model>Sett...

Right. This is probably going to take about 120MB per step. It might run with a long SAVE PER, but that'll make it hard to debug. Sorry.

Typically a model that pushes memory limits will execute extremely slowly anyway.

Just how big is this one (as indicated by Model>Settings>Info)?

Sorry - hasty code writing without actually compiling never works. The loop should be: venVarOffset[0] = vensim_get_varoff("VensimVariable[ID1]") for ( id=1; id<10; id++ ) venVarOffset[id]=venVarOffset[0]+id; I think it should be the case that vensim_get_varoff("VensimVariable[ID2]&qu...