Opened 9 years ago

Closed 5 years ago

#3882 closed defect (fixed)

record parameter binding

Reported by: Volker Waurich Owned by: Per Östlund
Priority: blocker Milestone: 1.16.0
Component: New Instantiation Version:
Keywords: Cc: Per Östlund, Adrian Pop, Rüdiger Franke

Description

Hi,

I would like to point to a bug regarding record parameter binbdings in power systems.

In PowerSystems.Examples.Spot.GenerationAC3ph.PowerAngle
within the component PowerSystems.AC3ph.Machines.Synchron3rd_ee generator that extends Partials.Synchron3rdBase the protected final parameter Coefficients.Synchron3rd c = Basic.Precalculation.machineSyn3rd(par,top.scale); exists.

The binding of this record is lost when printing +d=dumpdaelow.
Is there any possibility to forward the binding to the backend even if it is not yet evaluated?

Thank you.

Change History (4)

comment:1 by Francesco Casella, 6 years ago

Component: FrontendNew Instantiation
Milestone: Future2.0.0

That model no longer exists. The PowerSystems.Examples.AC3ph.Generation.PowerAngle model is reported to be under- and over-determined at the same time, maybe the root cause is still what is reported here.

comment:2 by Francesco Casella, 6 years ago

Priority: highblocker

in reply to:  1 comment:3 by Per Östlund, 5 years ago

Replying to casella:

That model no longer exists. The PowerSystems.Examples.AC3ph.Generation.PowerAngle model is reported to be under- and over-determined at the same time, maybe the root cause is still what is reported here.

That model now gives the same result as with the old frontend, which is that the backend claims that it's structurally singular. The machineSyn3rd call is also evaluated and all the generator.c fields are given bindings from the evaluated call (and if it couldn't be evaluated it would be moved to an equation, not just disappear).

So this now seems to be more of a backend issue rather than frontend, but regardless it might be a good idea to close this ticket and possibly open a new for the remaining issues.

comment:4 by Francesco Casella, 5 years ago

Milestone: 2.0.01.16.0
Resolution: fixed
Status: newclosed

Agreed!

Note: See TracTickets for help on using tickets.