Opened 15 years ago

Closed 4 years ago

Last modified 4 years ago

#1235 closed task (fixed)

Error messages for expressions does not have a context, resulting in very hard to understand error messages for large models

Reported by: Peter Aronsson Owned by: Peter Aronsson
Priority: critical Milestone: 1.16.0
Component: *unknown* Version:
Keywords: Cc: Peter Aronsson, AlexeyLebedev

Description

All error messages generated in Static (elabExp) does not have a context, because the Prefix is not passed as argument to elabExp. This results in error messages which are hard to read, like for instance

Warning: Parameter L has no value, and is fixed during initialization (fixed=true)

Here you do not know where (in which component) the L parameter comes from.

Either the error message should read:
Warning: In component inductor1: Parameter L has no value, and is fixed during initialization (fixed=true))
or it should read:
Warning: Parameter inductor1.L has no value, and is fixed during initialization (fixed=true))

I am setting this to high priority and severity critical, since for large models the error messages becomes almost useless.
Note: There is some implementation done for supporting which componentis currently being instantiated (implemented by Bjozac I think) but I belive it is not good enough.

Change History (4)

comment:1 by AlexeyLebedev, 14 years ago

I have uploaded improvements at revision 5949. Their are not complete, though - the functions in Inst.mo now call Static functions with corresponding prefices, but the functions in Interactive, Cevalfunc and Exp use NOPRE. Could somebody please check whether the prefix information included in error messages is correct now? I don't know which examples to test it on.

comment:2 by Dietmar Winkler, 9 years ago

Milestone: Future

comment:3 by Per Östlund, 4 years ago

Component: *unknown*
Resolution: fixed
Status: newclosed

This isn't really an issue anymore since most error messages from both the old and the new frontend includes the source code location of the error, and the new frontend often gives several locations to point out both where and why an error occured.

comment:4 by Francesco Casella, 4 years ago

Milestone: Future1.16.0
Note: See TracTickets for help on using tickets.