-
Notifications
You must be signed in to change notification settings - Fork 164
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
Made engine designs consistent w.r.t. the whole design scenario #3133
Conversation
Goal: Integrate the Modelica_Synchronous library into the MSL 4.0.0 under the name Modelica.Clocked. Reference to the code which is the starting point of this integration task: modelica/Modelica_Synchronous@0416c85
Manually fix remaining text occurences related to the switch from "Modelica_Synchronous" to Modelica.Clocked.
The models in WorkInProgress.mo are experimental and nobody worked at them for a long time. Should be moved out of the main repository (may preserve the package in a feature branch in my fork of the main repo).
Fixes modelica#2949#discussion_r286627826.
Using the suffix _der to denote a derivative is more idiomatic Modelica code
Removed as requested in review, related to discussion in modelica#2494.
Replaced assert(not trigger_interval==0, "...") by assert(trigger_interval > 0 or trigger_interval < 0, "...")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice.
…e now diagramatically represented, improved diagram layout, improved documentation, eliminated rotational clock duplicate and use of engine synchronization instead as single source of sampling).
…e now diagramatically represented, improved diagram layout, improved documentation, eliminated rotational clock duplicate and use of engine synchronization instead as single source of sampling).
Please rebase on current master. |
@christoff-buerger Can we please have two separate fixes here:
|
…lings are now diagramatically represented, improved diagram layout, improved documentation, eliminated rotational clock duplicate and use of engine synchronization instead as single source of sampling)." This reverts commit 9dc348d. As requested in modelica#3132 by @beutlich.
…lings are now diagramatically represented, improved diagram layout, improved documentation, eliminated rotational clock duplicate and use of engine synchronization instead as single source of sampling)." This reverts commit ad35571. As requested in modelica#3132 by @beutlich.
…-thiele/ModelicaStandardLibrary" This reverts commit b2d0067, reversing changes made to 11fd222.
@beutlich: I am sorry for the chaos; I merged the synchronous stuff in by accident due to missing rights. It should be alright now again (I reverted the problematic commit for the pull-request). |
I'll do a squash-merge later such that the back-and-forth commits will be removed from history, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, some consistency requirements are really tough, e.g.
- Consistent piston <-> cylinder connections:
Engine1b: connected pistion.a with cyclinder.b instead of rod3.a (the connection of Engine1a)
But fine to me. Now I even changed Engine1a to extend from Engine1bBase as well.
For the future, it is safer if you do not create PRs from master. You should use dedicated branches instead. |
@tobolar: I do not understand how that can be done? I think your commit fa75454 is wrong and should be undone! |
I checked now the version with the last changes of @tobolar, particular fa75454. We should revisit this. The now common base model I see two approaches to fix this:
or the following steps
@beutlich: How do you like us to proceed? New branch and pull request? |
Exactly. Thank you. |
Fix for last-minute errors of #3133 pull request
This pull request fixes the inconsistencies between the
Engine1a
,Engine1b
andEngine1b_analytic
models ofMechanics.MultiBody.Examples.Loops
. For details about these, please cf. Section 4.2 of Modelica language extensions for practical non-monotonic modelling: on the need for selective model extension.The pull request fixes #3132.
The changes are: