I am trying to clarify to myself how often the power flow solvers are called during simulation time.
I have observed during certain experiments simulating a 15’ bid market that the sync functions are called every minute and I am wondering if the power flow solvers are also called every minute. If this is what actually happens, taking into account the computation time, is this kind of inefficient?
Of course the general question is when SHOULD I call the power solver but I guess the answer depends on the configuration and the various parameters involved. Or maybe not?
Thanks in advance
Last edit: Rafik Fainti 2015-04-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The core of GridLAB-D handles all of the synchronization aspects. Each object determines how long it will remain in steady state if no external conditions change, and returns that value to the core. The core aggregates all of the return times, then determines how far the simulation can advance (the shortest interval of all the return times). When the simulation advances in time, all of the objects move together to the next time and all objects re-calculate their state.
So, likely some other object (maybe a schedule or a recorder? are you using a minimum timestep of 60s?) is requiring a system update and is forcing the re-iteration.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear all,
Of course the general question is when SHOULD I call the power solver but I guess the answer depends on the configuration and the various parameters involved. Or maybe not?
Thanks in advance
Last edit: Rafik Fainti 2015-04-10
Rafik,
The core of GridLAB-D handles all of the synchronization aspects. Each object determines how long it will remain in steady state if no external conditions change, and returns that value to the core. The core aggregates all of the return times, then determines how far the simulation can advance (the shortest interval of all the return times). When the simulation advances in time, all of the objects move together to the next time and all objects re-calculate their state.
So, likely some other object (maybe a schedule or a recorder? are you using a minimum timestep of 60s?) is requiring a system update and is forcing the re-iteration.