The simplest way to do something like this temporarily might be to add another
field to mpc with the rows corresponding to the branch matrix. That way you can
be sure to avoid breaking any code that uses the branch matrix, but you can
have additional data for each branch. Just remember to use e2i_field() to and
i2e_field() to convert to and from internal indexing as needed.
I am making a list of potential additions to the case format for the next
revision, so (and this is to everyone) please let me know if you have specific
proposals for additions to the MATPOWER case format.
Ray
> On Apr 9, 2019, at 9:38 PM, Jubeyer Rahman <[email protected]> wrote:
>
> I have temporarily done it by adding one extra column to the branch data but
> later before I run the OPF , I have removed it. It was a required for a loop
> operation which I was intending to do to modify some of the parameters.
>
> On Tue, Apr 9, 2019 at 9:27 PM John Cynn <[email protected]
> <mailto:[email protected]>> wrote:
> Dear Ray,
>
> Thanks for your response.
>
> I am curious if anyone in the community has extended the input format by
> adding more information like IDs, owner/area informatiom etc. For e.g. adding
> another column in branch data for IDs.
>
> John
>
>
> On Apr 9, 2019 1:28 PM, "Ray Zimmerman" <[email protected]
> <mailto:[email protected]>> wrote:
> Currently, MATPOWER has no such identifier, so the only way to identify a
> branch uniquely is by its row number in the branch matrix … or something
> derived from that. I agree all devices need some unique identifier
> independent of the order in the input data. At some point I expect we’ll
> update the input format again and add things like that.
>
> Ray
>
>
> > On Apr 9, 2019, at 12:42 PM, John Cynn <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> > Hi All,
> >
> > I wanted to check if there is a way to identify and differentiate
> > transmission lines that have the same "from" and "to" buses. For example,
> > if there are two lines, it is probably not possible to retrieve the line
> > information of one of the two lines unless we know the exact row number in
> > the branch data.
> >
> > Any ideas to do this? Some other tools like PSSE use some kind of an ID to
> > do so.
> >
> > Thanks.
> > John
>
>
>
>
