Is it possible to disable loop closure in Therion to export a 3d model? I want to compare two 3d models in Aven: one with loop closure and other without loop closure, to find where has the error loop.
If there is active Survex loop closure on the end of log of compilation is the list of loops and their errors there. m.s.
19. 1. 2018 v 13:06, Evaristo Quiroga via Therion <therion@speleo.sk>:
Is it possible to disable loop closure in Therion to export a 3d model?
I want to compare two 3d models in Aven: one with loop closure and other without loop closure, to find where has the error loop.
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
You can also let aven viewer display the loop errors by color, so you get the information quickly graphically. Am 2018-01-19 15:19, schrieb Martin Sluka via Therion:
If there is active Survex loop closure on the end of log of compilation is the list of loops and their errors there.
m.s.
19. 1. 2018 v 13:06, Evaristo Quiroga via Therion <therion@speleo.sk>:
Is it possible to disable loop closure in Therion to export a 3d model?
I want to compare two 3d models in Aven: one with loop closure and other without loop closure, to find where has the error loop.
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Thanks Martin and Benedikt, I know I can see the loop error in the compilation log and display the loop errors by colors in Aven. With this information I can find the loops with errors, but after I want to search the more suspected data with blunder error. Now what I want is to do is the same I do in Compass. Run a compilation with loop closure and another without, breaking the loops. If you see side by side the two models is more easy to understand the error origin. Evaristo. El 19/01/2018 a las 17:00, Benedikt Hallinger via Therion escribió:
You can also let aven viewer display the loop errors by color, so you get the information quickly graphically.
Am 2018-01-19 15:19, schrieb Martin Sluka via Therion:
If there is active Survex loop closure on the end of log of compilation is the list of loops and their errors there.
m.s.
19. 1. 2018 v 13:06, Evaristo Quiroga via Therion <therion@speleo.sk>:
Is it possible to disable loop closure in Therion to export a 3d model?
I want to compare two 3d models in Aven: one with loop closure and other without loop closure, to find where has the error loop.
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
19. 1. 2018 v 17:59, Evaristo Quiroga via Therion <therion@speleo.sk>:
Now what I want is to do is the same I do in Compass. Run a compilation with loop closure and another without, breaking the loops. If you see side by side the two models is more easy to understand the error origin.
Not very correct by the way I think. You may compile your file with parameter „debug on“ in layout. It will show you where are errors graphically. Or you may manually disconnect particular loop simple by commenting „equate“ in data file. Martin
Ok. Thanks Martin. Disconnect manually the loop by commenting "equate" is the same COMPASS do automatically. Looking in COMPASS documentation I have found It rename the loop close station (example: "station3" and "[station3]"), to can see the gap between the stations. El 19/01/2018 a las 18:54, Martin Sluka via Therion escribió:
19. 1. 2018 v 17:59, Evaristo Quiroga via Therion <therion@speleo.sk>:
Now what I want is to do is the same I do in Compass. Run a compilation with loop closure and another without, breaking the loops. If you see side by side the two models is more easy to understand the error origin. Not very correct by the way I think.
You may compile your file with parameter „debug on“ in layout. It will show you where are errors graphically.
Or you may manually disconnect particular loop simple by commenting „equate“ in data file.
Martin
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
You may comment - endcomment all equate lines as a block. But I’m afraid the structure of centerline would be broken. It is the reason I wrote that it is not very correct. How an algorithm may determine which equate is for loop closure and which one not. Martin
19. 1. 2018 v 19:30, Evaristo Quiroga via Therion <therion@speleo.sk>:
Ok. Thanks Martin.
Disconnect manually the loop by commenting "equate" is the same COMPASS do automatically. Looking in COMPASS documentation I have found It rename the loop close station (example: "station3" and "[station3]"), to can see the gap between the stations.
El 19/01/2018 a las 18:54, Martin Sluka via Therion escribió:
19. 1. 2018 v 17:59, Evaristo Quiroga via Therion <therion@speleo.sk>:
Now what I want is to do is the same I do in Compass. Run a compilation with loop closure and another without, breaking the loops. If you see side by side the two models is more easy to understand the error origin. Not very correct by the way I think.
You may compile your file with parameter „debug on“ in layout. It will show you where are errors graphically.
Or you may manually disconnect particular loop simple by commenting „equate“ in data file.
Martin
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Hi Evaristo! If commenting-out some equate statements breaks centerline structure, you can provide 'fake' fixed station. Or do the loop closure, determine stations where you cut centerline by commenting equate command, get its coordinates (cartesian or latlong by exporting to kml), and use fix command with those coordinates, that will preserve 'compilation' ability of whole your centerline. You can also Introduce that fake fixed stations iteratively, i.e. first one will be closer to centerline beginning on a surface, second deeper and so on, than you can see how loop clousure moves that junction points loop-by-loop. While introducing fixed points, you can allow them to be 'not so fixed', i.e. by providing values of standart deviation around them. Look at fix command syntax: fix <station> [<x> <y> <z> [<std x> <std y> <std z>]] when all 8 parameters entered, that construct an ellipsoid around point (x,y,z) with (stdx stdy stdz) dimensions.
That above is true if loop closure done manually by using equate command. There are also loops with silent closure, or chains of stations like: 1-2-3-4-5-1 If you need to automate that kind of loop closures, need to rename last station '1' to something else, and use 'equate' command through all your centerline data.
Hi Nikita, Yes, I have overcome the problem renaming the closure station or other station, to break the loop and see the legs without error correction deformation, to detect better the error origin. Evaristo. El 20/01/2018 a las 10:23, Nikita Kozlov via Therion escribió:
That above is true if loop closure done manually by using equate command. There are also loops with silent closure, or chains of stations like:
1-2-3-4-5-1
If you need to automate that kind of loop closures, need to rename last station '1' to something else, and use 'equate' command through all your centerline data.
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
participants (4)
-
Benedikt Hallinger -
Evaristo Quiroga -
Martin Sluka -
Nikita Kozlov