Opened 11 years ago

Closed 11 years ago

#2630 closed defect (invalid)

stateSelect propagation

Reported by: Willi Braun Owned by: Adrian Pop
Priority: high Milestone: 1.9.1
Component: Frontend Version: trunk
Keywords: Cc: Lennart Ochel

Description

It seems that the stateSelect attribute is not propagated correctly in one of the examples of the AVM guys. I've changed some of them on the top level but this change doesn't occur after instantiateModel(SystemDesignTest). (e.g. try to add StateSelect.always to the variable driveLineDesign.cross_Drive_with_TC_PTOSteer.inertia_test1.w).

Change History (3)

comment:1 by Lennart Ochel, 11 years ago

Cc: Lennart Ochel added

comment:2 by Adrian Pop, 11 years ago

I cannot reproduce this bug.

I changed DriveLineDesign driveLineDesign; to

DriveLineDesign 
  driveLineDesign(
    cross_Drive_with_TC_PTOSteer(
      inertia_test1(
        w(stateSelect = StateSelect.always))));

and get this:

  Real driveLineDesign.cross_Drive_with_TC_PTOSteer.inertia_test1.w(
    quantity = \"AngularVelocity\", 
    unit = \"rad/s\", 
    stateSelect = StateSelect.always) \"Absolute angular velocity of component (= der(phi))\";

The difference in flattening between the changed one and the original:

<   Real driveLineDesign.cross_Drive_with_TC_PTOSteer.inertia_test1.w(quantity = \"AngularVelocity\", unit = \"rad/s\", stateSelect = StateSelect.always) \"Absolute angular velocity of component (= der(phi))\";
---
>   Real driveLineDesign.cross_Drive_with_TC_PTOSteer.inertia_test1.w(quantity = \"AngularVelocity\", unit = \"rad/s\", stateSelect = StateSelect.default) \"Absolute angular velocity of component (= der(phi))\";

So it seems it is propagated correctly. How did you do it?

comment:3 by Willi Braun, 11 years ago

Resolution: invalid
Status: newclosed

Too stupid, I edit the wrong model.

Note: See TracTickets for help on using tickets.