Opened 11 years ago
Closed 6 years ago
#2467 closed defect (fixed)
Inner outer functions do not work properly
Reported by: | Adrian Pop | Owned by: | Per Östlund |
---|---|---|---|
Priority: | high | Milestone: | 2.0.0 |
Component: | Frontend | Version: | trunk |
Keywords: | Cc: |
Description
package gravityPackage model ParticleField inner function gravity = TwoBodyField; Particle p1(x_init = {2,-2,0}, v_init = {0.7,0,0}); Particle p2(x_init = {0,0.5,0}, v_init = {-1,-1,0}); Particle p3(x_init = {0.5,2,0}, v_init = {-1,-0.5,0}); end ParticleField; function TwoBodyField extends GravityField; protected Modelica.SIunits.Position b1[3],b2[3]; Modelica.SIunits.Velocity n1[3],n2[3]; algorithm b1:={0,0,0}; b2:={0,1,0}; n1:=-(x - b1) / sqrt((x - b1) * (x - b1)); n2:=-(x - b2) / sqrt((x - b2) * (x - b2)); g:=n1 / ((x - b1) * (x - b1)) + n2 / ((x - b2) * (x - b2)); end TwoBodyField; partial function GravityField input Modelica.SIunits.Position x[3]; output Modelica.SIunits.Acceleration g[3]; end GravityField; model Particle parameter Modelica.SIunits.Position x_init[3]; parameter Modelica.SIunits.Velocity v_init[3]; protected outer function gravity = GravityField; //outer function gravity=ParticleField; //outer function gravity=TwoBodyField; Modelica.SIunits.Position x[3](start = x_init); Modelica.SIunits.Velocity v[3](start = v_init); Modelica.SIunits.Acceleration a[3]; equation v = der(x); a = der(v); a = gravity(x); end Particle; end gravityPackage;
Change History (10)
comment:1 by , 10 years ago
Milestone: | 1.9.1 → 1.9.2 |
---|
comment:2 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:7 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:8 by , 7 years ago
Milestone: | 1.12.0 → Future |
---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
comment:9 by , 7 years ago
Milestone: | Future → 2.0.0 |
---|---|
Owner: | changed from | to
Status: | new → assigned |
This should work in the new front-end, but currently doesn't.
comment:10 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This example now runs successfully with the new front end. Will be the default in 2.0.0.
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).