This is a property of type Text.
Pages using the property "Computation time comments"
Showing 25 pages using this property.
(
previous 25) (
next 25)
D | |
|---|
| DIETER + | depends on model specification (seconds to days) |
| Demod + | 32 households simulated for 1 year with 1 min time resolution |
E | |
|---|
| EMLab-Generation + | Depends on the enabled modules |
| ESO-X + | depends on scenario, e.g., amount of storage capacity |
| Energy Policy Simulator + | Model run is completed in a few seconds for a single run |
| 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. |
F | |
|---|
| Ficus + | Highly dependent on model size |
I | |
|---|
| IRENA FlexTool + | Should be quite fast for linear problems. |
L | |
|---|
| Lemlab + | 50 prosumers, one day |
M | |
|---|
| MOCES + | strongly depends on the modeling depth and model complexity |
| Maon + | dispatch for 8760 coupled hours in full European region with spot, FCR, aFRR, mFRR, emission, renewable, thermal, hydro, battery, CHP, PtG, DSR, FBMC, AHC, HVDC and on-off decision model, without facility-wise aggregations |
N | |
|---|
| NEMO + | runtime depends on # of CPUs devoted to optimisation |
| NEMO (SEI) + | Natively supports parallel processing, so multi-core processors are an advantage |
O | |
|---|
| 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. |
| OpenTEPES + | Computation time will depend on the optimization problem size |
P | |
|---|
| PowerSimulations.jl + | Best in class |
Q | |
|---|
| QuaSi - GenSim + | more with complex geomety of the building |
| QuaSi - ReSiE + | several minutes on business laptop, depending on model complexity and time-step |
R | |
|---|
| Renpass + | varying, 240 minutes is roughly for an hourly computation for one year |
S | |
|---|
| SimSEE + | the 15 min with 8 cpus is for a optimizaion/simulation of the uruguayan system over 10 years horizon with a daily time-step |
| 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 |
(
previous 25) (
next 25)
