Ventana software support forum

Assuming the latter, you could do the following: - Create a metric that is a function of the gap between your target and actual values, like error = (target-actual)^2 weight = {some negative value} - Create a payoff that minimizes the metric *p error/weight - Optimize For this to work, the model and...

Are you looking for a dynamic target that affects the behavior of decisions, or goal-seeking optimization?

Some dynamic variables are implemented as macros, and you can turn on visibility of their internals (Tools>Options>Settings). Check "Show" for "Macro Variables" (near the middle of the dialog pane). However, the discrete or infinite order delays are not among them. If you need th...

We won't revert. This is probably something simple. Thanks for the report.

Something like:

The issue is that storage for results is allocated at the time of the first (ordinary) run, so if FINAL TIME is longer than that in a sensitivity instance, they get truncated. As a workaround, you could set things up such that an ordinary simulation is longer than your sensitivity range. You'd still...

The QUEUE functions aren't available in PLE (or if they are, it's a bug).

Definitely sounds like your version of the files may have been corrupted somehow.

It's not compatible with PLE because it uses macros.

It is compatible with the model reader, but you need to download the .vmf version (marked as for the Reader) from the author's page.

This could also be done in Ventity.

The model is probably incompatible with PLE. Try the Model Reader (also free).

I occasionally work in text mode for special circumstances - search & replace is convenient, for example - but I almost never build a model as text. Two exceptions: - we occasionally generate repetitive equations in Excel or a text processor of some king - translating models from DYNAMO or other...

If you have a working text model, all the variables are there, but they won't appear on the sketch until you place them. That's actually a reasonably quick process if you use the Sketch Varlist and toolbar tools for adding existing variables. See: https://www.vensim.com/documentation/22970.htm To tu...

You could potentially implement something using QUEUE ATTRIBUTE, but we'd have to know a little more about the specific situation to say for sure.

I think you want to leave the stock units alone, and handle it a bit differently. Something like: Overdue calls = INTEG( ... ) ~ calls Desired call rate = new call arrival rate + overdue calls/time to catch up ~ calls/month Desired staff = Desired call rate / Productivity ~ people Productivity = ......

The GET_SUBSCRIPT functions can't dynamically recompile the model with different dimensions, unfortunately.

Generally the constraint to impose is: Stock = INTEG( inflow - outflow, init stock) init stock = ... inflow = ... outflow = MIN( desired outflow, max outflow) desired outflow = ... max outflow = stock/min time to drain stock Often min time to drain stock is equal to time step for convenience, so you...

It's easy to count the 0s:

is zero = IF THEN ELSE( x = 0, 1, 0 )
then integrate is zero/TIME STEP to get the count.

If the max is fixed, you can use the same trick. But if the max is not known until the end of the simulation, there's no easy solution.

Again, I think your best bet would be to have some spare dimensions with a switch to activate/deactivate them. The switch could reside in a corresponding Excel column header, so it would be easy to access.

Ventity, OTOH, can do this easily.

If you have a long vector of "initial infected" parameters, I think it's likely that the data don't say much about them individually. One option would be to change your parameterization, so that you have a "total initial infected" combined with subscripted variables that determin...

The * means that the bounds on the variable in your control file are tighter than the CI. There could be three reasons for this: - the parameter only matters in conjunction with others (the principal axis problem raised in the Dogan paper) - the data don't supply much information about the parameter...

I think you'd need to create a stock or SAMPLE IF TRUE to record the time when the value is first exceeded, then compute the time elapsed since then.

The system is working. Do you get a success message on the form, like this?

I'll check ...