Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chapter on expandable connectors needs clarification; rearranging lists #1330

Closed
modelica-trac-importer opened this issue Nov 4, 2018 · 4 comments
Assignees
Labels
bug Something isn't working P: high
Milestone

Comments

@modelica-trac-importer
Copy link
Collaborator

Reported by hansolsson on 23 Oct 2013 12:39 UTC
In #1279 there was a decision to rearrange some lists for 3.4; and to close that ticket a new ticket was created for that.

The rules currently are:

Then connections containing expandable connectors are elaborated:

•Augmenting when connecting two expandable
The following rules apply to expandable connectors

•expandable connectors can only be connected to other expandable connectors.
•Additional rules for added variables.
•Need source
•Everything is a connector
•no flow
•Introduction by connection

Rearrange to:

•Introduction by connection
•Augmenting when connecting two expandable
•Additional rules for added variables.
•Need source
•Everything is a connector
•no flow
•expandable connectors can only be connected to other expandable connectors.

Wait with rearrangement until 3.4.


Migrated-From: https://trac.modelica.org/Modelica/ticket/1330

@modelica-trac-importer
Copy link
Collaborator Author

Comment by eshmoylova on 11 Feb 2014 14:30 UTC
The current set of rules on how expandable connectors are elaborated and what rules are applied and when continues to confuse people and cause a lot of debates. See tickets #1311, #1312, #1409#comment:29, #1409#comment:32, #1409#comment:36 (and other comments in this ticket), #428, and #829. It shows that the clarification is needed sooner.
I am increasing the priority and severity, and propose to change the milestone to 3.3r1.

@modelica-trac-importer
Copy link
Collaborator Author

Comment by pharman on 12 Feb 2014 21:54 UTC
I agree, I too think this should be in 3.3r1 (setting to discuss in Lund).

We have seen some user models where, due to expandable connector use, submodels are illegal in isolation (either due to referencing of a potentially present variable in an expression; or simply unbalanced), and yet the combined model is balanced and simulates in multiple Modelica tools. This is not surprisingly confusing for users.

@modelica-trac-importer
Copy link
Collaborator Author

Comment by hansolsson on 14 Mar 2014 13:37 UTC
Include already in 3.3r1
Favor: 3
Against: 0
Abstain: 10

@modelica-trac-importer
Copy link
Collaborator Author

Comment by hansolsson on 22 Mar 2014 10:25 UTC
Updated in r7444

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P: high
Projects
None yet
Development

No branches or pull requests

2 participants