We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the example landxml file you will find a dataset that is used in the step by step reproduction of the problem defined below.
Same geometry leads to different conclusion of the applications calculation. It is a hard problem to explain, so please just follow the steps below.
This is the end result we would like to achieve:
Example landxml file: Here
Whenever a connection is possible, the application is capable of producing the same result, no mater in what order actions are executed.
So you would now conclude the connection is not possible, the application gives this as error:
CONTROL- AND ERROR-MESSAGES NADB-2101 PROJECT NO. CALC.NO. ACCOUNT REG.DATE CALC.DATE - - - - 25/ 8-2017 ELEMENT 3. OVERLAPPING -8.06 NO CONNECTION BETWEEN ELEMENT 3. - 5. CALCULATION ABORTED AT ELNO 3.
CONTROL- AND ERROR-MESSAGES NADB-2101 PROJECT NO. CALC.NO. ACCOUNT REG.DATE CALC.DATE - - - - 25/ 8-2017 ELEMENT 3. OVERLAPPING -26.66 NO CONNECTION BETWEEN ELEMENT 3. - 5. CALCULATION ABORTED AT ELNO 3.
Now you conclude that the connection is possible, even though we started from the illogical state we had in step 7.
This kind of inconsistency makes it very hard for the user to estimate if something is really impossible or if it is just a bug in the application.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Context
In the example landxml file you will find a dataset that is used in the step by step reproduction of the problem defined below.
Same geometry leads to different conclusion of the applications calculation. It is a hard problem to explain, so please just follow the steps below.
This is the end result we would like to achieve:
![Example of end result](https://camo.githubusercontent.com/d230e05f2ebcf6679c426e459f14d2b7d9b54aa8118bde5f8a904f9fa388bb45/68747470733a2f2f6c68332e676f6f676c6575736572636f6e74656e742e636f6d2f2d7574455378334e49784b4d2f57614153435a5f625976492f41414141414141414871512f726553465f4870676c557377327a44526d6357774c34534236427070506243354143484d5943772f73302f616361645f323031372d30382d32355f31342d30332d32302e706e67)
Information
Example landxml file: Here
Expected Behaviour
Whenever a connection is possible, the application is capable of producing the same result, no mater in what order actions are executed.
Steps to Reproduce
The way it will not work
So you would now conclude the connection is not possible, the application gives this as error:
The way it will work
Now you conclude that the connection is possible, even though we started from the illogical state we had in step 7.
Context
This kind of inconsistency makes it very hard for the user to estimate if something is really impossible or if it is just a bug in the application.
The text was updated successfully, but these errors were encountered: