User Forum of Software BASEMENT
| BASEMENTBasic Simulation Environment for computation of environmental flow and natural hazard simulationLaboratory of Hydraulics, Hydrology and Glaciology (VAW)ETH Zurich |  |
You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2023-04-07 14:29:23
- Matteo Facchini
- Developer
- From: Trento
- Registered: 2014-09-05
- Posts: 278
No edges found for node string
I report here a post concerning what seems to be a basemesh bug
Cheers
Matteo
EDIT: in my case, it happens for particularly long stringdefs (hundreds of nodes). The work around is to divide the stringdef in shorter segments.
Last edited by Matteo Facchini (2023-04-07 15:38:10)
Offline
#2 2023-04-11 08:18:35
- Lukas Vonwiller
- Developer
- Registered: 2014-09-04
- Posts: 127
Re: No edges found for node string
Ciao Matteo
Nodestrings (NS in the .2dm mesh) are limited to max. 200 nodes.
Cheers, Lukas
Offline
#3 2023-04-19 13:00:52
- Matthias Bürgler
- Developer
- From: Zürich
- Registered: 2019-04-04
- Posts: 150
Re: No edges found for node string
Do I understand the bug report correctly, in that BASEMESH produces meshs with a wrong order of node IDs in the nodestrings?
Offline
#4 2023-04-19 15:03:32
- Matteo Facchini
- Developer
- From: Trento
- Registered: 2014-09-05
- Posts: 278
Re: No edges found for node string
Yes, but I guess it is related to what Lukas wrote: my stringdef was defined by more than 200 nodes. The numbering seems to be correct until a certain node.
Do you want me to send you the shape files to reproduce the issue?
Last edited by Matteo Facchini (2023-04-19 15:04:52)
Offline
Pages: 1