GenerateFibers

[mikymike]

I am currently having a problem with The GenerateFibers command. In fact, in the case of 2 different "EmbeddedFibers", I receive the following error:

Lists 4 and 9 have same type [nd] and same name [FiberNodes]
0: list[3] tag = nd name = MODL
1: list[4] tag = nd name = FiberNodes
2: list[5] tag = ee name = Fibers
3: list[6] tag = tt name = PRTC
4: list[8] tag = nd name = MODL2
5: list[9] tag = nd name = FiberNodes
6: list[10] tag = ee name = Fibers
7: list[11] tag = tt name = PRTC2
Lists 5 and 10 have same type [ee] and same name [Fibers]
0: list[3] tag = nd name = MODL
1: list[4] tag = nd name = FiberNodes
2: list[5] tag = ee name = Fibers
3: list[6] tag = tt name = PRTC
4: list[8] tag = nd name = MODL2
5: list[9] tag = nd name = FiberNodes
6: list[10] tag = ee name = Fibers
7: list[11] tag = tt name = PRTC2
* * * * FATAL ERROR * * * *


Is it a possible bug? Maybe is due to the fact that GenerateFibers command creates automatically both edge and node lists with the same name ("Fibers" and "FiberNodes" respectively). Thus, in the case of more embedded fibers, one can have that error.

Best regards,
Michele

[zhouxinwei]

This not a bug. Any two lists can not have both the same type and name. In both mesh.mrs and mesh2.mrs, there is a node list MODL, you need to rename one of them.

[mikymike]

I am sorry. I forgot to use a different name both for material (MASONRY) and nodeList (MODL) in the example file "mesh.mrs" and "mesh2.mrs" attached in the previous post.
By the way, unfortunately, I am still receiving the same error using the mesh file attached here (using: two different material name "MASONRY" and "MASONRY2"; two different nodeList name "MODL" and "MODL2").

[zhouxinwei]

When the fibers are generated, the name for the node list is called Fibers by default. When there are two LDPM tet lists both having fibers, there is a name collision. This bug is fixed in 2018.09.09, which can be found under Hotfix folder on our server.

Thanks for reporting the issue.