Model simulation not showing up

[hazhirr]

Hi,
In trying to get the following model to work with SDeverywhere (thanks Chris for all the earlier fixes on earlier version of this model), I can get to the graphs, but they seem to initialize but not simulate:
https://www.dropbox.com/scl/fi/6kkga6pu68locs5rh96oa/SimpleCity-V07_5.mdl?rlkey=9ia86i684obsbpvif429hnqyk&dl=0
Based on the small dots at the beginning of time (which are correctly initialized):

The config file for graphs is here:
https://www.dropbox.com/scl/fo/pw1723sizt55os608v0j9/AJd5V817bhBh3cURsvdMmiQ?rlkey=mzbrgesbpg8i0588d3puaum24&dl=0
Does this indicate some errors in simulation that do not show up in Vensim but happen in web assembly? If so, what is the approach to diagnose them? In another note @chrispcampbell noted a "Model Explorer" app that allows for seeing some errors, but I couldn't find that, is that something I can use for tracing the cause, and how can I access that?
Thanks a lot for any insights!
hazhir

[chrispcampbell]

Hi @hazhirr, I followed these steps to try to reproduce the issue:

• I took the mdl file and config folder that you linked above and dropped them into a new folder
• I did the usual "Quick Start" step of npm create @sdeverywhere@latest
• I selected the default template and said "yes" to WebAssembly like before (since you're using ALLOCATE AVAILABLE, which isn't yet ported to the JavaScript code generator)
• I did npm run dev and got the output below

---

Is that the expected output?

I'm not sure the cause of the blank graph you were seeing above. It's possible that a change to your model parameters could have made the generated model out of sync with some other part of the SDE runtime, but I'm not sure about that. One thing you can do to be certain is to start with a fresh (re)build by stopping the local builder process (you can type Control+C in the Terminal to kill the builder you started with npm run dev), then remove the sde-prep directory (or type npm run clean), then start the local builder again with npm run dev.

Unfortunately the tracing tool I mentioned the last time we did some tracing/debugging hasn't been merged yet. It's integrated into the model-check tool on a work-in-progress branch I have, but I haven't had time to finish that work. It would be useful in diagnosing cases like this so I'll try to carve out some time to get that finished up.

[chrispcampbell]

The other thing I'll note is that attaching FINAL TIME to a slider is not guaranteed to work at this time. I'd suggest removing that from inputs.csv for now just to remove one potential source of issues while you diagnose.

[hazhirr]

Thanks a lot Chris for checking on this; the process I used should have been similar (I just didn't do the optional git part), so don't know what may explain the difference; I will try again and hopefully it works this time. best, hazhir

…

On Tue, Apr 29, 2025 at 8:24 PM Chris Campbell ***@***.***> wrote: The other thing I'll note is that attaching FINAL TIME to a slider is not guaranteed to work at this time. I'd suggest removing that from inputs.csv for now just to remove one potential source of issues while you diagnose. — Reply to this email directly, view it on GitHub <#636 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AORHR5XOCSMR7X5I3MAB5X324AJY7AVCNFSM6AAAAAB4BO26DWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYGY3TSNI> . You are receiving this because you were mentioned.Message ID: <climateinteractive/SDEverywhere/repo-discussions/636/comments/12986795@ github.com>

[hazhirr]

It did work when I re-generated the project, so all set. Thank you!