Opened 8 years ago

Last modified 7 years ago

#3926 accepted defect

Parameter calculation with numerical Jacobian leads to wrong results

Reported by: ptaeuber Owned by: wbraun
Priority: normal Milestone: Future
Component: Backend Version:
Keywords: Cc: casella, lochel

Description (last modified by sjoelund.se)

The non-fixed parameters of the following model are calculated to 0 if calculateStrongComponentJacobians is skipped for initialization, which is obviously wrong:

model foo
  final parameter Real p1 = 1;
  final parameter Real p2 = 2;
  final parameter Real p3 = 3;
  final parameter Real p4 = 4;
  parameter Real q1 (fixed=false);
  parameter Real q2 (fixed=false);
initial equation
  -p1 = 3 * (p3 * q1 + p4 * q2);
  -p2 = 3 * (q1 * p4 - p3 * q2);
end foo;

A testing script is attached.

Attachments (1)

calculateParametersBug.mos (1.5 KB) - added by ptaeuber 8 years ago.

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by ptaeuber

comment:1 Changed 8 years ago by sjoelund.se

  • Description modified (diff)

comment:2 Changed 8 years ago by wbraun

  • Component changed from Run-time to Backend
  • Milestone changed from Future to 1.10.0
  • Priority changed from high to normal
  • Status changed from new to accepted

So the problem is that we have currently no means to handle torn linear system numerically, so the module calculateStrongComponentJacobians is mandatory for them.
So I added a translation error for this case.

comment:3 Changed 8 years ago by sjoelund.se

  • Milestone changed from 1.10.0 to 1.11.0

Ticket retargeted after milestone closed

comment:4 Changed 8 years ago by sjoelund.se

  • Milestone changed from 1.11.0 to 1.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:5 Changed 7 years ago by casella

  • Milestone changed from 1.12.0 to Future

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

Note: See TracTickets for help on using tickets.