Networks : connections tables

[Solange]

Hello Cyril,

I think that I have found another mistake in the Amelet-HDF doc (v
1.5.0 and v 1.5.1) !!!

- For a network/$net1/connections" table for a simple network ($
12.2.1),
It's written that the table is an integer table, that means that
"idJunction", "idPort", "idTube" and "idWire" are all integers .....
But in practice (in $ 12.2.1.3 - connections table example and in h5
networks we validated),
"idJunction" is string (lenght = 20) and the value is the name of id
declared in the table network/$net1/junctions,
"idTube" is string (lenght = 20) and the value is the name of id
declared in the table network/$net1/tubes,
"idPort" is an integer and is the port number of the multiport model
(number in the matrix),
"idWire" is an integer and is the wire number of the tube (or number
in the matrix defined in transmissionLine).

- For a network/$net1/connections" table for a compound network ($
12.2.2),
"idJunction", "idPort" and "idTube" are defined as in the practice I
explained before, so for me it's OK
"idWire" is defined as a string ( "a wire/transmission line element
name" ..... Why ??? For me It would be the same as for a simple
network ... and it's the case in my h5 networks we validated ....

If you agree with me, I think that Amelet-HDF doc would :
- be more precise in connections table definition for simple network
(just before the example given in $ 12.2.1),
- be changed in connections table definition for compound network
(just before the example given in $ 12.2.2).

Regards,

Solange

[cyril giraudon]

Hi,

You are right. Errors are typo (copy/paste ) issues.

It will be fixed in the next release :

Network connections table :

(idJunction, idPort, idTube, idWire) as (String, Integer, String, Integer)

Regards,

Cyril.