Make sure solving for a variable always solves the equation

[Martin Sjölund]

model M
  Real r[3];
equation
  r[1] = 1;
  r[integer(time)] = 2;
  r[2] = time;
end M;

We get r[3] is solved by:

Variables (1)
========================================
1:  r[3]:VARIABLE() .M, .Real type: Real [3]


Equations (1, 1)
========================================
1/1 (1): {1.0, time, r[3]}[integer(time, 0)] = 2.0

Add an assertion integer(time) == 3, and use r[3] = 2.0.

[Martin Sjölund]

Postponed until 1.9.1

[Martin Sjölund]

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).

[Martin Sjölund]

Milestone changed to 1.9.3 since 1.9.2 was released.

[Martin Sjölund]

Moved to new milestone 1.9.4

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Ticket retargeted after milestone closed

[Martin Sjölund]

Milestone moved to 1.12.0 due to 1.11.0 already being released.

[Francesco Casella]

I expect that this model should be rejected because it is not possible to guarantee its solvability in general.

As of v1.13.0-dev-155-g68350e9 we get

[1] 23:04:31 Symbolic Error
An independent subset of the model has imbalanced number of equations (1) and variables (0).
variables: equations:
1 : r[integer(time)] = 2.0

[2] 23:04:31 Translation Error
pre-optimization module clockPartitioning (simulation) failed.

I'm not sure if this is the expected output, but I guess not generating code for simulation in this case is a good idea.