Skip to content

Robert Woodall

My feedback

11 results found

  1. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall shared this idea  · 
  2. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall supported this idea  · 
  3. 34 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    ON ROADMAP  ·  pascal.lang responded

    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 Woodall supported this idea  · 
  4. 27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall supported this idea  · 
  5. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    IN DISCUSSION  ·  pascal.lang responded

    Hello,

    Thank you for this, there is already a mechanism available for achieving something very similar to this. If you have a network and then go to the simulation parameters for this network via Model > Model parameters > Simulation parameters then within these there is an entry for “Max number of timestep halvings”. Depending on the timestep in the run dialog and the entry in the simulation parameters here you will be able to determine the minimum computational timestep that the engine goes to before failing a simulation.

    Hope this helps.

    Robert Woodall supported this idea  · 
  6. 84 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall supported this idea  · 
  7. 28 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall supported this idea  · 
  8. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall supported this idea  · 
  9. 26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall supported this idea  · 
  10. 23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall supported this idea  · 
  11. 19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Robert Woodall supported this idea  · 

Feedback and Knowledge Base