#5202 closed defect (fixed)
NFCeval.evalBuiltinAbs gets invalid vector input in Buildings model
| Reported by: | Francesco Casella | Owned by: | Per Östlund |
|---|---|---|---|
| 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)
follow-up: 2 comment:1 by , 6 years ago
| Summary: | NFCeval.evalBuiltinAbs should also accept array input arguments → NFCeval.evalBuiltinAbs gets invalid inputs for System2 Buildings model |
|---|
comment:2 by , 6 years ago
Replying to perost:
NFCeval.evalBuiltinAbsshould 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 by , 6 years ago
| Priority: | high → blocker |
|---|---|
| Summary: | NFCeval.evalBuiltinAbs gets invalid inputs for System2 Buildings model → NFCeval.evalBuiltinAbs gets invalid vector input in Buildings model |
comment:5 by , 5 years ago
| Milestone: | 2.0.0 → 1.16.0 |
|---|
Note:
See TracTickets
for help on using tickets.
NFCeval.evalBuiltinAbsshould 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.