#2721 closed defect (fixed)
initialization and dynamic state selection
Reported by: | Volker Waurich | Owned by: | Lennart Ochel |
---|---|---|---|
Priority: | normal | Milestone: | 1.9.4 |
Component: | Run-time | Version: | trunk |
Keywords: | initialization, dynamic state selection | Cc: | Lennart Ochel |
Description
Hi,
The model ComparisonQuasiStationary2 in testsuite\simulation\modelica\resolveLoops fails at initialization with the error:
Error: Model error. 0^(-2) is not defined
This comes from the jacobian of the linear system:
{6,3}:simpleSolenoid2_1.g_mFePole.G_m ^ -2.0,
It should not be initialized with zero. I think this has something to do with dynamic state selection. Could you please check if the start values are computed or initialized with default 0 if there is a stateSet?
Change History (8)
comment:1 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → accepted |
comment:2 by , 10 years ago
Milestone: | 1.9.1 → 1.9.2 |
---|
comment:3 by , 10 years ago
Initialization of DSS should be fixed in the meanwhile. Unfortunately, I cannot test this particular example, since the symbolic jacobians break compilation:
ComparisonQuasiStationary2_03lsy.c: In function ‘ComparisonQuasiStationary2_initialLinearSystem’: ComparisonQuasiStationary2_03lsy.c:347: error: ‘ComparisonQuasiStationary2_functionJacNLSJac2_column’ undeclared (first use in this function) ComparisonQuasiStationary2_03lsy.c:347: error: (Each undeclared identifier is reported only once ComparisonQuasiStationary2_03lsy.c:347: error: for each function it appears in.) ComparisonQuasiStationary2_03lsy.c:348: error: ‘ComparisonQuasiStationary2_initialAnalyticJacobianNLSJac2’ undeclared (first use in this function) make: *** [ComparisonQuasiStationary2_03lsy.o] Error 1
comment:4 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:6 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).