Ventana software support forum

There are two options: 1. Replace the IF THEN ELSE structure with a VECTOR LOOKUP over time (I think the sample model for VECTOR LOOKUP illustrates this). Then you will have an array of time points, like decisionTime : (t1-t10) with gValue[decisionTime] = 3.5, 2.4, 1.9, 4.2 ... You can then specify ...

In a custom graph, change the x-division and y-division settings.

For the graph tool, you can change the global setting on the Scaling tab of the Control Panel.

Presumably you want to remove all but one. :) Without a legend, it's hard to be sure what this is. You need to do one of the following: - unload datasets using the Control Panel's datasets tab - deactivate subscripts using the Subscript Control - edit the custom graph definition using the Control Pa...

Got it - thanks! I'll put in a ticket and we'll investigate.

I'll see if we can get a different skin from the Help system vendor.

Thanks. Two requests:
- can you post a screenshot of the save dialog, showing the Excel filename to be used? (Email to us at info at ventity.biz if easier.)
- the text of the extended error message - this will be on the clipboard after you click OK on the "path is not of legal form" dialog.

Speculation: the path error has something to do with the location where you're saving the file.

The M is definitely a bug - I've put in a ticket for it.

How did you generate the "path not of legal form" error? The export command is working for me.

Where do you need these numbers? (Charts, tables, data grid?)

If you copy-paste or export the values to Excel or csv, you'll get the raw numbers.

Or this:
https://www.researchgate.net/profile/Ro ... alysis.pdf

This is something we're exploring but it's not on the road map yet.

Unfortunately knowing the number of loops isn't helpful, because many weak loops could be dominated by one strong loop.

You might try this link instead: https://papers.ssrn.com/sol3/papers.cfm ... id=3114407

If the problem persists after a fresh download, let us know.

Use the Comment tool:

You can use the loops tool to count the total number of loops, but not their polarity.

Can you describe your purpose for doing this?

I think what you may really need is eigenvector analysis: https://pdfs.semanticscholar.org/58b4/c ... 845f28.pdf

I can't view the model remotely, but you probably just need to change the type of the variable to "lookup".

See:
https://vensim.com/lookups-in-vensim/
http://vensim.com/documentation/usr08.htm

Chapter 18 of the User Guide is a good example of a model calibrated against data:
http://vensim.com/documentation/usr18.htm

Same file for sure. What you want is a dynamic structure that replicates the data over the historical period, then runs into the future for projections.

I'm on the road and can't modify the model, plus I don't have the data. But the structure you already have for "fit degression rate" is exactly what you need. "FIT degression rate DATA" is the lookup and "FIT degression rate" is the value looked up from the data, by time.

Is this a data variable? If so, the line won't extend past the end of the data.

I think the "wrong type" error only occurs if a variable is not a constant (the "not found" is misleading). Most likely causes are setting the constant subtype to unchangeable (with ==), setting the type to initial(), or simply specifying a nonnumeric expression for the variable, like x*y or 3/4.

I think the second error is a consequence of the first. It's not finding Yearly Depreciation Factor, and therefore not adding it as an input. Are there other parameters in the vsc?

Does Yearly Depreciation Factor have an array dimension? It's not set to "Initial" type by accident?

Sounds like your control file (.vsc) specifies a variable that doesn't exist or isn't constant.

It would be exactly the same structure as you have for FIT Degression Rate.

Normally you would specify the data file in the Data Sources... field, on the Advanced tab of the simulation control dialog (Model>Simulate menu).

However, PLE doesn't do data variables, so you'd have to use another lookup.