Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#1735 closed defect (fixed)

Driveline model takes a long time to generate code

Reported by: Per Östlund Owned by: Per Östlund
Priority: critical Milestone: 1.9.0
Component: Backend Version: trunk
Keywords: Cc: Per Östlund, Adrian Pop, Willi Braun, Bill Janssen

Description

The RC_driveline model in the attached file takes a very long time to generate simcode for, where very long means that it looks like it's stuck in an infinite loop but will probably finish some time. This seems to be due to SimCode.extractValuesAndDims being called with 18 discrete variables from SimCode.createOdeSystem (search for "madness" in SimCode to find the place), which has very bad complexity. The reporter of the issue says that replacing LossyGear with IdealGear gets rid of the issue, so the problem might be related to LossyGear (or the fact that extractValuesAndDims is crazy).

Attachments (1)

RC_combined.mo (19.0 KB ) - added by Per Östlund 13 years ago.

Download all attachments as: .zip

Change History (3)

by Per Östlund, 13 years ago

Attachment: RC_combined.mo added

comment:1 by Martin Sjölund, 12 years ago

Cc: Frenkel TUD Bill Janssen added; Jens Frenkel removed
Component: Simulation Code GenerationBackend
Milestone: 1.9.0
Resolution: fixed
Status: acceptedclosed
Summary: Driveline model takes a long time to generate simcode forDriveline model takes a long time to generate code

Seems the changes to enable tearing by default has fixed the problem in this model.

comment:2 by Martin Sjölund, 12 years ago

Cc: Frenkel TUD removed
Note: See TracTickets for help on using tickets.