Ventana software support forum

STEP, PULSE etc. do create discrete responses. You may be getting the impression of a slope from plots that show a change happening over a TIME STEP, which is finite. The connecting line in these cases is a little misleading, because nothing is really defined between time steps. What are you seeing ...

Another long shot idea would be to move it to your Documents folder or something like that.

I assume your system is running in English?

I'll try this new copy on my Win10 desktop.

I've followed both your sequences exactly, and unfortunately can't replicate the crash in either.

Can you try repeating one or both after setting a new, unique run name? That might give some hint as to whether this is a file access issue.

You can also use stream 0 for all the function calls, then set the global NOISE SEED parameter with the sensitivity control file.

Not quite sure what you're trying to do. Do you want to reuse the same structure in a different context (Paste as New, like Vensim's Replicate), or use a reference to existing structure (ordinary Paste)? Or reuse an entire entitytype?

I think that's the problem - you need the new June build 1123 - just visit http://vensim.com/ventity.html again.

What build date do you see in Help>About Ventity?

Also: https://www.vensim.com/documentation/usr15.htm

The Help system also includes sample models for the GET XLS functions, including subscripts.

https://www.vensim.com/documentation/usr16.htm
https://www.vensim.com/documentation/usr17.htm

I looked at your sample. It seems that column A of the widget tab of your spreadsheet was hidden, with junk in it. Therefore no entities were created. This works: test group widget2b (3).zip If you want your lookup to vary by shape, you could add a Shape entitytype and define the lookup there, then ...

Here's an example of the format.

The purpose of the negative seed would be to serve as a flag indicating that results should be randomized (to the clock, or to system crypto sources) with every new run.

I'll take a look at the vdf code.

Very clever, JJ.

If there's demand, we could potentially introduce a new convention for randomizing the streams - perhaps a negative seed value?

Generally you can't call a 32 bit dll from a 64 bit application, unless there's some kind of bridge process. But the HWND error looks like the first issue.

This thread is six years old, and all the software involved has changed - I think you're unlikely to get useful answers here. I'd suggest composing a new question.

Using arrays would also dramatically simplify model maintenance. If you change a few equations, you could do it once, not 50-100 times.

Sorry for the delay, but it's available now.

I can't get this to happen either. On an unrelated note: I don't think you need RK4 integration here. If you revert to Euler, you won't be bothered by the integration warning, which is likely arising from the discontinuities in the random process for emergency costs. Also, conceptually, I think you ...

Good to hear. I tried to beat the heck out of the new code yesterday, but there are always things we miss, so it's good to have some independent testing. Thanks for that. Glad to hear it's working out.

I have a working fix, I think. I just need to do a little more testing before posting. A day?

There's a reason for this incidentally. Numbers in an equation that have dimensions are often implicit parameters that should be exposed to scrutiny and testing. Admittedly, the number of meters in a kilometer is not up for discussion. For conversion factors like that, you can set the "unchange...

Strange. This works perfectly for me, even when I edit the death rate.

I see a red flash between Df .68 and .69 - that's the IRE graph rescaling, not an FP error (an error would turn the status bar yellow).

We'll have to do a new build with the fix. Need to test a little further, but should be fairly quick.

I think the FP error is something else. Are you seeing this in Synthesim mode? What parameter change causes it?