Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#3490 closed defect (fixed)

Initialization scales badly

Reported by: Lennart Ochel Owned by: Lennart Ochel
Priority: critical Milestone: 1.9.4
Component: Backend Version:
Keywords: Cc:

Description

It seems that the initialization scales badly for large systems.

Change History (8)

comment:1 by Lennart Ochel, 9 years ago

This are some time measurements using ScalableTestSuite.Electrical.TransmissionLine.ScaledExperiments.TransmissionLineModelica_N_XXX as scalable model:

time [s] for
N pre optimization initialization simulation
10 0,037472811 0.041285136 0.01164375
20 0.071433869 0.079462691 0.020607123
40 0.217333943 0.166757507 0.04152687
80 0.432273499 0.454853872 0.164011598
160 1.17030325 2.267705213 0.37920847
320 5.0227649 20.62593407 1.766217402
640 32.85928258 285.9040669 12.47769637

comment:2 by Francesco Casella, 9 years ago

Some models (including the one mentioned above) in the library do not have fully specified initial conditions. Maybe the problem is that the algorithm that selects them automatically doesn't scale well with the system size. Wheteher this is an intrinsic property of tha problem, or just due to an inefficient implementation of the current algorithm, might be worth investigating.

However, it is likely that for reasons of efficiency, large-scale systems are provided with fully specified initial conditions.

I will do so and commit a new revision of the library asap for testing.

comment:3 by Lennart Ochel, 9 years ago

Status: newaccepted

comment:4 by Francesco Casella, 9 years ago

The new version of the ScalableTestSuite library with fully specified initial conditions is 1.2.0. It was released today on GitHub, should end up automatically in the testsuite tomorrow

in reply to:  1 comment:5 by Lennart Ochel, 9 years ago

Replying to lochel:

This are some time measurements using ScalableTestSuite.Electrical.TransmissionLine.ScaledExperiments.TransmissionLineModelica_N_XXX as scalable model:

time [s] for
N pre optimization initialization simulation
10 0,037472811 0.041285136 0.01164375
20 0.071433869 0.079462691 0.020607123
40 0.217333943 0.166757507 0.04152687
80 0.432273499 0.454853872 0.164011598
160 1.17030325 2.267705213 0.37920847
320 5.0227649 20.62593407 1.766217402
640 32.85928258 285.9040669 12.47769637

I speeded up the initialization for all models that are not over-determined, which is most common.
This are the new time measurements for exactly the same model as above:

time [s] for
N pre optimization initialization simulation
10 0.037948374 0.018084288 0.011952443
20 0.073691972 0.036116253 0.02039135
40 0.192043867 0.071482219 0.040158798
80 0.428354136 0.192928505 0.128823696
160 1.085886028 0.706097062 0.366486381
320 5.003769767 3.933397942 1.841361654
640 33.40780092 29.00988272 12.99646612

comment:6 by Lennart Ochel, 9 years ago

Milestone: Future1.9.4
Resolution: fixed
Status: acceptedclosed

The general issue is fixed. We could open a new ticket for over-determined models, since they will still scale badly.

comment:7 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.4-1.9.x

Milestone renamed

comment:8 by Martin Sjölund, 9 years ago

Milestone: 1.9.4-1.9.x1.9.4

Milestone renamed

Note: See TracTickets for help on using tickets.