Opened 4 years ago

Closed 3 years ago

Last modified 3 years ago

#6207 closed defect (fixed)

Mixed under/overdetermined initialization problem in Buildings

Reported by: casella Owned by: Karim.Abdelhak
Priority: critical Milestone: 1.19.0
Component: Backend Version:
Keywords: Cc: mwetter

Description (last modified by casella)

Please check Buildings.Fluid.HeatExchangers.ActiveBeams.Examples.CoolingAndHeating. The backend reports

Error: The initialization problem of given system is mixed-determined.
It is under- as well as overdetermined and the mixed-determination-index is too high. [index > 10]

The root cause should be investigated and resolved.

Change History (11)

comment:1 Changed 4 years ago by casella

  • Milestone changed from 1.17.0 to 1.18.0

comment:2 follow-up: Changed 4 years ago by AnHeuermann

Duplicate of #6199?

comment:3 Changed 4 years ago by casella

I'm not 100% sure, just gut feeling.

I'd keep both tickets open, when one is fixed it is trivial to click on the test report link and see if the other has been fixed as well.

comment:4 follow-ups: Changed 4 years ago by Karim.Abdelhak

I have a strong feeling that this might be connected to #6203 and is caused by missing bindings of parameters. If not caused it should at least be influenced by it, so we should resolve that other ticket first.

Last edited 4 years ago by Karim.Abdelhak (previous) (diff)

comment:5 in reply to: ↑ 4 Changed 4 years ago by casella

Replying to Karim.Abdelhak:

I have a strong feeling that this might be connected to #6203 and is caused by missing bindings of parameters. If not caused it should at least be influenced by it, so we should resolve that other ticket first.

This would be fine, we'd solve mutiple issues in one shot.

comment:6 Changed 4 years ago by casella

  • Description modified (diff)

comment:7 in reply to: ↑ 4 Changed 3 years ago by casella

Replying to Karim.Abdelhak:

I have a strong feeling that this might be connected to #6203 and is caused by missing bindings of parameters. If not caused it should at least be influenced by it, so we should resolve that other ticket first.

Unfortunately, fixing #6203 had no effect here.

comment:8 in reply to: ↑ 2 Changed 3 years ago by casella

Replying to AnHeuermann:

Duplicate of #6199?

I also have this feeling.

Possibly also related to #6200

Last edited 3 years ago by casella (previous) (diff)

comment:9 Changed 3 years ago by casella

  • Cc mwetter added

comment:11 Changed 3 years ago by casella

  • Milestone 1.18.0 deleted

Ticket retargeted after milestone closed

comment:12 Changed 3 years ago by casella

  • Milestone set to 1.19.0
  • Priority changed from high to critical
  • Resolution set to fixed
  • Status changed from new to closed

After PR #7903 was merged in, the examples reported in this ticket

successfully passes the backend phase.

Note: See TracTickets for help on using tickets.