#5202 closed defect (fixed)
NFCeval.evalBuiltinAbs gets invalid vector input in Buildings model
| Reported by: | casella | Owned by: | perost |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.16.0 |
| Component: | New Instantiation | Version: | |
| Keywords: | Cc: |
Description
Please check Buildings.Examples.Tutorial.SpaceCooling.System2. The following error is reported
[OMCompiler/Compiler/NFFrontEnd/NFCeval.mo:1562:20-1562:79:writable]
Error: Internal error NFCeval.evalBuiltinAbs got invalid arguments
({6000.0, 0.0, 0.0, 0.0})
Change History (6)
comment:1 follow-up: ↓ 2 Changed 5 years ago by perost
- Summary changed from NFCeval.evalBuiltinAbs should also accept array input arguments to NFCeval.evalBuiltinAbs gets invalid inputs for System2 Buildings model
comment:2 in reply to: ↑ 1 Changed 5 years ago by casella
Replying to perost:
NFCeval.evalBuiltinAbs should not accept array inputs, NFCeval assumes that function calls are vectorized correctly. In other words, this is not an error in NFCeval, but a sanity check that fails because NFCeval is given bad input. Most likely due to an array modifier being treated incorrectly.
OK. Unfortunately I have no easy means to access the intermediate results of the flattening process if it does not terminate, so I can't help you with that.
comment:3 Changed 5 years ago by casella
- Priority changed from high to blocker
- Summary changed from NFCeval.evalBuiltinAbs gets invalid inputs for System2 Buildings model to NFCeval.evalBuiltinAbs gets invalid vector input in Buildings model
comment:4 Changed 4 years ago by perost
- Resolution set to fixed
- Status changed from new to closed
Fixed in 4cf73067.
comment:5 Changed 4 years ago by casella
- Milestone changed from 2.0.0 to 1.16.0
comment:6 Changed 4 years ago by casella
Backported to 1.14.0 and 1.15.0
Note: See
TracTickets for help on using
tickets.
NFCeval.evalBuiltinAbs should not accept array inputs, NFCeval assumes that function calls are vectorized correctly. In other words, this is not an error in NFCeval, but a sanity check that fails because NFCeval is given bad input. Most likely due to an array modifier being treated incorrectly.