You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a annual frequent process (say marriage), the process is simulated every year during the same month.
That can produce an irrelevant seasonality. We could draw a random month of event in such case.
Won't be a piece of cake:
the process is done during month 1 then the result must be saved somewhere until the month k selected.
That's not obvious because of the internal structure of the simulation keeping only last period in direct memory.
That's not the biggest issue
How can we deal with processes order. If divorce is run after marriage, just married couple are allowed to divorce but if the random month event for marriage is unfortunately after the divorce month, a bug is going to be generated.
The text was updated successfully, but these errors were encountered:
For a annual frequent process (say marriage), the process is simulated every year during the same month.
That can produce an irrelevant seasonality. We could draw a random month of event in such case.
Won't be a piece of cake:
That's not obvious because of the internal structure of the simulation keeping only last period in direct memory.
That's not the biggest issue
The text was updated successfully, but these errors were encountered: