• 138 views | 3 messages Discussion: LEAP
    Topic: Hourly time slice optimization errorSubscribe | Previous | Next
  • Hyungsik Choi 9/1/2021

    Like
    1 Like

    I tried to solve LEAP-NEMO in hourly time resolution (8760 hours), while optimizing capacity expansion and energy storage.
    I used the solver MOSEK, CPU Intel i5-9500 3GHZ, RAM 48GB. It took a long time (2~3 hours) to reach the model objective define, but it failed to solve it finally.
    A message is shown as following

    ""

    I wonder if it is related to RAM shortage. Please, I need your help.

    Best,
    Hyungsik
  • Jason Veysey 9/16/2021
      Best Response

    Like

    Hi, Hyungsik –


    This probably is related to an out-of-memory error; we’ve seen this sometimes with Mosek. Could you try solving for one year only? You can do this by changing the model end year or by calculating results for selected years only. If it works in this case, I would say memory is the issue.


    We have noticed that Gurobi and CPLEX seem to do a better job managing memory with large models. If you have access to one of them, I'd suggest testing with it.


    Thanks,


    Jason

  • Hyungsik Choi 9/17/2021
      Best Response

    Like

    Thanks for the tip. I reduced the time steps from every year to 10 years. The model was solved in the same setting. This is the only solution I can use with MOSEK. I'd like to change to Gurobi and CPLEX later on.

    Best, hyungsik