[DEFECT] Static Histories Does Not Work Fully in Debug Dispatch Mode.

[dylanjm]

---

Defect Description

Describe the defect

What did you expect to see happen?

To be able to use static histories and debug mode

What did you see instead?

There are some errors concerning _ROM_Cluster not being found

Also we must deal with reducing the project time despite the CSV containing more years of data. For example, setting macro_steps = 1 and keeping 20 years of data in your CSV causes an error.

Do you have a suggested fix for the development team?

Describe how to Reproduce Steps to reproduce the behavior:

Screenshots and Input Files Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.

Platform (please complete the following information):

• OS: [e.g. iOS]
• Version: [e.g. 22]
• Dependencies Installation: [CONDA or PIP]

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• [x] 1. Is it tagged with a type: defect or task?
• [x] 2. Is it tagged with a priority: critical, normal or minor?
• [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

---

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• [x] 1. If the issue is a defect, is the defect fixed?
• [x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• [x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• [x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• [x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

[PaulTalbot-INL]

No need to email users, as currently this will cause an error and not incorrect operation.

[PaulTalbot-INL]

I think this got solved by #285, @dylanjm can you confirm?

[dylanjm]

Issue approved for closure by #285