[leonardo-frid]

Hi David,

Yes, that’s possible. You would use the Flow Spatial Multipliers. See https://docs.stsim.net/reference/prop_stockflow_flow_spatial_mults.html

Cheers,
Leonardo

[leonardo-frid]

Hi Audrey,

You can define State Class groupings using State Attribute Values. However, there is currently no way to define probabilities or probability multipliers across State Class groupings.

Probabilities can be defined at the level of individual State Classes in the Transition Pathways.

Probabilities can also be defined at the level of State Class and/or Strata in Transition Multipliers.

[leonardo-frid]

There is a new release of the stsimecodep package (version 3.3.1) that fixes this problem. This was an incompatibility with the most recent version of SyncroSim. You can install this version of the package from the Windows interface by going to “File | Packages | Install” or update from an older version using “File | Packages | Update”.

[leonardo-frid]

The amount of memory that a SyncroSim/ST-Sim run will require depends on a number of factors including: Landscape size, model complexity, number of concurrent jobs being used for multiprocessing. The latter is something an end user has control over, with the tradeoff being between run times and memory usage. Something I often do when trying to decide how much memory to allocate to a VM for a particular simulation is to run a test simulation for a single realization of my model for a couple of timesteps. After starting the simulation I fire up the resource monitor and track it to identify peak memory use. This will allow me to calculate memory required per job, and decide on the amount of memory to allocate to my VM and how many multiprocessing jobs I should be targeting. Users can set the maximum number of concurrent jobs from the Windows interface under “File | Library Properties | Multiprocessing” or by editing the core_Multiprocessing datahseet with rsyncrosim, pysyncrosim, or the console.

[leonardo-frid]

Hi Brian,

You can try the following:
In the Windows Interface: File | Compact [note that this can take a few minutes for a large library]

Cheers,
Leonardo

[leonardo-frid]

Q: Is there a way, other than using try and except( for when the datasheet call fails), to determine which datasheets are active in a scenario – ala replicate the datafeeds tab in the GUI?
A: This is a good idea for a feature. It does not currently exist but we will consider implementing it.

Q: Also is there a crosswalk between the datafeed names and the datasheet names?
A: Another good idea. We will also consider implementing.

Thanks for the great suggestions!

[leonardo-frid]

Hi Audrey,

There currently is no way to output deterministic transitions. One thing you could do is setup your succession transitions as probabilistic transitions with a minimum age at the age when the succession transition occurs and a probability of 1. These would then essentially be deterministic and you would get output for them.

Regards,
Leonardo

[leonardo-frid]

Just a quick follow-up that there actually was a bug in stsim sf whereby the limits are not properly checked when the cell size is not equal to 1 area unit. Absolute stock amounts on a cell were being compared to limits on stock density per unit area. A fix will be ready shortly in the package stsimsf v3.3.5.

[leonardo-frid]

Great question. See the these pages for details:
https://docs.stsim.net/reference/prop_prob_transitions.html#age-reset-optional
https://docs.stsim.net/reference/prop_prob_transitions.html#age-shift-optional

Basically, If Age Reset is set to ‘Yes’ then the age of the simulation cell is reset to the minimum age of the destination state class after a transition occurs. In your case, that would be 41 years. If Age Reset is set to ‘No’ then the age will be set to the nearest value to the current age of the cell that still satisfies the age constraints of the destination state class. In your case, the age would be set to 70 years. Note that you could use Age Reset in combination with Age Shift. For example if you set Age Reset to ‘No’ and Age Shift to -40 a cell that was age 90 before the transition would be Age 50 after the transition. If you set Age Reset to ‘Yes’ and Age Shift to 10, a cell that was any age before the transition would be 51 (41+10) after the transition.

[leonardo-frid]

Thanks Beth for pointing out this issue and sharing your library. After reviewing your library we were able to determine that the use case that leads to this problem is a “Flow Pathway” where the “Target Type” is “From Stock” and your limit is on the “From Stock” for that pathway. In this case “Stock Limits” on the “From Stock” do not get observed. We will work on fixing this issue. In the meantime for users experiencing the same problem the workaround is to reverse the “Flow Pathway” From/To Stocks and set the “Target Type” as “To Stock”.

[leonardo-frid]

Hi Beth,

Thanks for sharing this observation. My initial response is that you may have discovered a bug in the stock limit feature in the software. Would you be able to share your library with us so we can understand your use case better? If the file is not too large, you could sent it to info@apexrms.com. Otherwise, you could post it somewhere for us to download.

Thanks,
Leonardo

[leonardo-frid]

Hi Louis, your intuition is correct. If you would like initial TST for cells to be randomized between one and three years, you should setup “Initial TST Min” = 1, and “Initial TST Max” = 3.

[leonardo-frid]

HI Louis, the answer is yes. The way I would set this up is something like the following using the same disturbance type “All Fire” for all pathways. Note the values used for proportions are just examples.
Destination State Class | TST Min | TST Max | Proportion
[Post Surface Fire] | 0 | 14 | 1.0
[Post Surface Fire] | 15 | [Blank] | 0.5
[Post Mixed Fire] | 15 | [Blank] | 0.2
[Post Replacement Fire] | 15 | [Blank] | 0.3

Note that proportions will be respected amongst rows that meet the TST criteria for a specific cell. Because the 0-14 and > 14 conditions are mutually exclusive, this configuration would work fine. Within 15 years of a disturbance only surface fire is possible. After 15 years all three are possible and proportions add to 1.0.

[leonardo-frid]

Thanks Kevin,

Can you please upgrade rsyncrosim to the latest CRAN version (1.3.2 as of January 5, 2022) and let me know if that resolves your problem? There may be some version compatibility issues with the current SyncroSim version and the old version of rsyncrosim that you are running.

[leonardo-frid]

Hi Kevin,

Can you please let us know what versions of SyncroSim, ST-Sim and rsyncrosim you are currently using?

Thanks,
Leonardo

[Author]

Posts