same Problems with piston on beta1 and beta2
- admin
- Topic Author
- Visitor
18 years 3 months ago #599
by admin
Replied by admin on topic Re:I have the same problem
Concerning the PISTON tutorial with CAELinux Beta 2, unfortunately with Salome 2.2.8, you cannot mesh it with 5 mm element size, but you need to decrease the Average Length hypothesis to 3 mm and it should work fine.
- rusty
- Topic Author
- Visitor
18 years 3 months ago #601
by rusty
Replied by rusty on topic Re:same Problems with piston on beta1 and beta2
I have changed the Average Length to 2mm (Max Volume = 100), but I still get the error message and the mesh contains no Volume elements. Any other ideas?
- JMB
- Topic Author
- Visitor
18 years 2 months ago #621
by JMB
Replied by JMB on topic Re:I have the same problem
Hello Admin / Others,
I am using Salome 3.2.1 to tetrahedron mesh a fairly complex solid imported via Catia V's STEP translator. On one occassion I was able to successfully mesh using:
1. Wire Discretization; Av Length = 3
2. Triangle (Mefisto); Length from Edges ...
3. Tetrahedron (Netgen); Max Vol = 100
But I am finding that subsequent attempts on the same model, on the same PC, result in failures. It is this inconsistent behavior that puzzles me. I am very certain that it had worked successfully that one time, because I was carefully documenting every variation I was using and I was careful to check the meshes \"Detailed Mesh Info\" to confirm the existance of 3D elements.
Has anybody else encountered a similar experience? If so were you able to find a work around or a tweak? Is it the \"Mefisto algorithm fails occassionally\" bug documented in the release notes that I am encountering?
Thanks
I am using Salome 3.2.1 to tetrahedron mesh a fairly complex solid imported via Catia V's STEP translator. On one occassion I was able to successfully mesh using:
1. Wire Discretization; Av Length = 3
2. Triangle (Mefisto); Length from Edges ...
3. Tetrahedron (Netgen); Max Vol = 100
But I am finding that subsequent attempts on the same model, on the same PC, result in failures. It is this inconsistent behavior that puzzles me. I am very certain that it had worked successfully that one time, because I was carefully documenting every variation I was using and I was careful to check the meshes \"Detailed Mesh Info\" to confirm the existance of 3D elements.
Has anybody else encountered a similar experience? If so were you able to find a work around or a tweak? Is it the \"Mefisto algorithm fails occassionally\" bug documented in the release notes that I am encountering?
Thanks
Moderators: catux
Time to create page: 0.118 seconds