ROBERT.DICKINSON
My feedback
71 results found
-
16 votes
ROBERT.DICKINSON supported this idea ·
-
12 votes
ROBERT.DICKINSON supported this idea ·
-
76 votes
ROBERT.DICKINSON supported this idea ·
-
4 votes
ROBERT.DICKINSON supported this idea ·
-
8 votes
ROBERT.DICKINSON supported this idea ·
-
17 votes
ROBERT.DICKINSON supported this idea ·
-
2 votes
ROBERT.DICKINSON supported this idea ·
-
16 votes
ROBERT.DICKINSON supported this idea ·
-
6 votes
ROBERT.DICKINSON supported this idea ·
-
2 votes
ROBERT.DICKINSON supported this idea ·
-
12 votes
ROBERT.DICKINSON supported this idea ·
-
6 votes
ROBERT.DICKINSON supported this idea ·
-
24 votes
ROBERT.DICKINSON supported this idea ·
-
31 votes
The approach which we are looking to leverage here is one which deviates a little from the original request but gives the same ability to interrogate results part way through a simulation. After investigating options, the best appears to be to have a run for the total duration you are interested in, then set a state saving checkbox in the run and when you wish to interrogate simulation results stop the simulation. We will then make use of ICMLive developed concatenation of results to allow us to tie in the “continuation run” with the results which were stopped earlier. There is a lot more detail to this than I can add here, but it should meet the need.
ROBERT.DICKINSON supported this idea ·
-
6 votes
Demand patterns/direct demands in WS Pro can be updated from Live Data by right-clicking on the demand diagram and selecting Update→From Live Data. Incrementing the number of demand categories within the demand diagram it has proven not to be expensive in terms of computational resources (different to the actual “pattern update” which could take long when performed against a wide spectrum of customers).
ROBERT.DICKINSON supported this idea ·
-
7 votes
To be clear, changes to the parent can cascade to all child scenarios as long as the same data set is used.
To inheret changes where datasets are different would introduce complexity and room for error in model management.
This seems to be specifically a request for a new parent-child relationship among data sets which could exist parallel and independent of the scenario relationships. This way a child scenario could use a child dataset that varies at certain nodes, but still inherets changes from the parent as long as they're still matching - the same way that InfoWorks software handles scenarios. I see large benefits of this approach but it could certain confuse many modelers.
This is valuable feedback as we discuss model data management in the cloud. Thank you.
ROBERT.DICKINSON supported this idea ·
-
8 votes
ROBERT.DICKINSON supported this idea ·
-
2 votes
ROBERT.DICKINSON shared this idea ·
-
4 votes
ROBERT.DICKINSON supported this idea ·
-
2 votes
ROBERT.DICKINSON supported this idea ·