This is a property of type Text.
Pages using the property "Computation time comments"
Showing 20 pages using this property.
|Backbone +||The implementation leads to reasonable computation time, but we plan to improve calculation time in future.|
|DIETER +||depends on model specification (seconds to days)|
|EMLab-Generation +||Depends on the enabled modules|
|ESO-X +||depends on scenario, e.g., amount of storage capacity|
|Energy Transition Model +||From input to output, including communication with the server the calculation takes less than a second (except with very slow internet connections).|
|EnergyNumbers-Balancing +||runtime ~1ms to simulate 4.5 years half-hourly|
|EnergyScope +||Depends on the case complexity. Rarely exceeds 5 minutes.|
|Ficus +||Highly dependent on model size|
|MOCES +||strongly depends on the modeling depth and model complexity|
|Maon +||backtesting 2018 with detailed hydro, CHP, DSR and FBMC model in hourly resolution with all ENTSO-E bidding zones|
|NEMO +||runtime depends on # of CPUs devoted to optimisation|
|OSeMOSYS +||Depends on solver used (glpsol/CPLEX/Gurobi etc.)|
|Oemof +||Depends strongly on use of modeling framework. Typically if investment decisions are enabled, a model run takes a multiple of minutes to compute.|
|Renpass +||varying, 240 minutes is roughly for an hourly computation for one year|
|SimSES +||20 years with 5 minute time step resolution|
|Switch +||computation time is roughly cubic with the spatial and temporal resolution selected; users typically adjust resolution to achieve 2-10 min solution time in testing phases, 10-60 min solution time for final optimizations|
|Temoa +||varies with chosen solver|
|TransiEnt +||The Library can be used to simulate single components as wells as complete systems. The values above apply to a coupled example whith a district heating network and a gas network.|
|URBS +||Highly dependent on model size (esp. storage) and solver (CPLEX, GLPK, Gurobi)|