-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing new stanify - replicated? datastructure? #42
Comments
In the Vensim model you've provided, I couldn't find any instances of |
In addition, I request that you provide the Vensim file with |
I don't follow; don't you have the following in the zipped mdl file?
|
Nah, it's there. It's just that |
From below, exog demand's type is datatype and time series vector is supplied (perhaps through python @ in stanify). in vensim, I recall we implemented as interpolate/lookup structure. Does thie make sense to you? Is everyting good? exog demand:INTERPOLATE: |
Then is the default assumption for Vensim data variables is they exist as a time-vector? |
yes |
@Dashadower compare_vensim_stan.mdl.zip below is a vensim file with the datastructure you've requested -- Light blue variable
exog demand
is datastructure and dark bluetable for order fulfillment ratio
is the table function. Could you please check the below?setting value for
exog demand
makes this variable no longerdatastructure
. If my memory is correct, you were trying to receive data only from vensim. However, I don't know how this can be implemented other than the original method (supplying value in python after declaring datastructure in vensim). Happy to be corrected!time series patterns are replicated in the result from stan's draws2data. For easy comparison, I've set
exog demand
is 2 * Time + 100 (this requires changingexog demand
type (so it's not datastructure anymore ) as shown below.With the value above, please make sure the overshoot of

adj ss
and smooth adjustment ofadj s
are visible in the stan-generated time series.compare_vensim_stan.mdl.zip
The text was updated successfully, but these errors were encountered: