-
Notifications
You must be signed in to change notification settings - Fork 169
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
Move conditional heat port models to Modelica.Thermal.HeatTransfer.Interfaces #359
Comments
Comment by AHaumer on 22 Apr 2010 10:07 UTC |
Comment by AHaumer on 22 Apr 2010 16:46 UTC |
Modified by AHaumer on 27 Apr 2010 19:33 UTC |
Comment by clauss on 29 Apr 2010 12:47 UTC |
Comment by dietmarw on 29 Apr 2010 13:17 UTC |
Comment by clauss on 30 Apr 2010 07:58 UTC |
Comment by dietmarw on 30 Apr 2010 08:35 UTC |
Comment by christiankral on 4 May 2010 13:37 UTC Result: Example The partial original implementation of the heat ports **has to be established! ** |
Comment by clauss on 5 May 2010 07:08 UTC |
Modified by dietmarw on 13 Sep 2010 23:16 UTC |
Comment by dietmarw on 1 Aug 2015 21:36 UTC |
Comment by dietmarw on 1 Aug 2015 21:39 UTC |
There was the duplicate ticket #2312 introduced which summarizes some aspects on the duplicate conditional heat ports. |
Removing milestone for reasons given in #3097 (comment). |
Reported by christiankral on 21 Apr 2010 15:44 UTC
The conditional heat port models
Modelica.Electrical.Analog.Interfaces.ConditionalHeatPort
andModelica.Electrical.MultiPhase.Interfaces.ConditionalHeatPort
are not specific for electrical systems. Since these conditional heat port models can be applied to any model with one or more conditional heatports, the location in the electrical domain is not correct. Therefore, both conditional heat port models shall be moved toModelica.Thermal.HeatTransfer.Interfaces
when the next conversion script is due.Example: Conditional heat port models shall also be applied in
Modelica.Magnetic
.Migrated-From: https://trac.modelica.org/Modelica/ticket/359
The text was updated successfully, but these errors were encountered: