NatLabRockies / NatLabRockies/SAM

Physical Trough model "hangs" during a parametric with dispatch enabled

Open
#1,077 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

bug csp
Dominant language
C++
Stars
486
Forks
219
Avg merge
10h 10m
Merged PRs (30d)
2

Description

Describe the bug

The physical trough model will not progress in a reasonable time when conducting a parametric study on hours of storage and solar multiple with dispatch optimization enabled.

To Reproduce

Steps to reproduce the behavior:

  1. Open the Parabolic Trough - Physical Single Owner Model
  2. Click on System Control and "Enable dispatch optimization"
  3. Click on Parametrics and Quick setup...
  4. Add Hours of storage at design point {'tshours'} and Solar multiple {'specified_solar_multiple'}
  5. Edit there values as follows: Hours of storage 4-18 using a 2 hour interval and solar multiple 1-4 using a 0.5 interval
  6. Click Run simulations
Expected behavior

The model should solve for all combinations. However, some simulations do not solve (see screen) where simulation 19 failed (8 tshours and 2 solar multiple) and two cores are "hanging" making no progress after an extended period of time (about an hour). I will try to narrow down which simulations are causing the issue.
This csp solver hanging occurs with the following configurations about 33% through the simulation:

  • 6 hours of storage, 4 solar multiple
  • 4, 6 hours of storage, 3.5 solar multiple
  • 4 hours of storage, 3 solar multiple

These are obviously "bad" designs but maybe it might be worth understanding why this causes the solver to hang and if the reason leads to a more stable solver.

Screenshots

image

Operating System and Version
  • OS: [Windows]
  • Version [SAM 2021.12.2]
Additional context

This is problematic for some analysis completed within HOPP using the physical trough model.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.