- Therion - speleo.sk

3 Map-connection issue - effect of map-level
by Bruce Mutton 19 Mar '23

19 Mar '23

From: Bruce Mutton <bruce(a)tomo.co.nz> Sent: Tuesday, 12 July 2022 21:08 To: 'List for Therion users' <therion(a)speleo.sk> Subject: Map-connection issue - effect of map-level And noting that map-level progressively chops out the offsets, starting with the level-1 offset. Undocumented feature for export of maps? At least it does not change the map-connection line behaviour. export map -projection plan \ -layout LayoutMapThisCave \ -layout LayoutMapThisCavePlan \ -output ../Output/PlanMap.pdf select PlanMap@Cave -map-level 0 select PlanMap@Cave -map-level 1 select PlanMap@Cave -map-level 2 select PlanMap@Cave -map-level 3 select PlanMap@Cave -map-level 4 (and -map-level basic and -map-level 5 etc) Bruce

3 3

2 Map-connection issue - Going to four levels - Offset tests SAMD-ITF-IS example
by Bruce Mutton 13 Mar '23

13 Mar '23

From: Bruce Mutton <bruce(a)tomo.co.nz> Sent: Monday, 11 July 2022 15:02 To: 'List for Therion users' <therion(a)speleo.sk> Subject: Map-connection issue - Going to four levels - Offset tests SAMD-ITF-IS example I managed to squeeze five levels of maps out of my example, going to 4 levels of offset (offset of offset of offset of offset). All of the offsets are correctly made, relative to their parent maps. However the line created by point map-connection is only correctly originating from its parent map at the most deeply nested level of offset and at the 1st level offset. At all other offset levels, the map-connection line reverts to originating from the top-level map, and not from its direct parent. In the marked up diagram below: * #1, #2 indicates the offset level * The squares indicate the scope of the various maps subordinate to the main map * The extreme left (green) and right (yellow- almost) map-connection lines correctly originate from their parent maps * The map-connection lines highlighted pink and blue originate from the main map, and not from their parent map, even though the offset is correctly made from the parent. The recti-linear lines I have sketched show where I expect the map-connection lines to be drawn. For comparison https://therion.speleo.sk/wiki/mapconnectors?s[]=connection <https://therion.speleo.sk/wiki/mapconnectors?s%5b%5d=connection> describes offsets 2 levels deep, and as I have found and on that wiki page, 2 levels deep behaves as it should. It is only once we get to 3 levels of offset that the behaviour deviates and becomes problematic. So the pattern is clearer, and I am becoming more confident it is a bug. Why a bug? * Because at 2 levels of offset the effective behaviour is that each map-connection line originates from its direct parent. * And at 3 and 4 levels of offset, the effective behaviour is that the only the most deeply nested and the 1st level of offset map-connections originate from their direct parent. The intermediary level offset map-connections originate from the main map location and not from their direct parent. So maybe it is a problem with the definition of point map-connection, or the way that the origin and destination locations are parsed to the map-connection lines? Bruce

1 0

1 map-connection issue - Offset tests SAMD-ITF-IS example
by Bruce Mutton 13 Mar '23

13 Mar '23

From: Bruce Mutton <bruce(a)tomo.co.nz> Sent: Monday, 11 July 2022 10:16 To: 'List for Therion users' <therion(a)speleo.sk> Subject: map-connection issue - Offset tests SAMD-ITF-IS example Tarquin, David The results of our little quiz made me uneasy, so I found an old test project that I believe is structured like Tarquin's, a pattern I call 'scrap and map definitions - inside trip file - inside survey' SAMD-ITF-IS. The outcome I feared (due to my large collection of projects structured differently) is that map-connections with multi-level offsets would work just fine with SAMD-ITF-IS. That has not been the case, I have the same (I think) behaviour with this test project as I have with my other projects. So perhaps a degree of relief but still a mystery to resolve. With my test project: * Offsets work OK. * Offsets of offsets (level 2 offsets) work just fine so long as the most deeply nested offset map is comprised of scraps (and not maps). * Offsets of offsets (level 2 offsets) do not work (connection emanates from grandparent, not the parent) if the most deeply nested offset map is comprised of maps (a necessary prerequisite when preparing for the third level of offsetting). * Offsets of offsets of offsets (level 3 offsets) map-connections correctly emanate from their parent level 2 offset map, but the level 2 map-connection continues to incorrectly emanate from its grandparent. I have not progressed this to a fourth level, brain is starting to hurt and I ran out of scraps associated with the particular sub-survey that I picked on. Re-reading Tarquin's last email mentioning sub-sub-sub-surveys, I wonder if we are at cross purposes a little (or Tarquin is using 'survey' loosely to refer also to maps). In my example below (which I think is structured like Tarquin's) there are two surveys (1 and 2) and a parent cave survey that contains those two surveys, so only two levels of survey. However I have created three levels of map which offset correctly. When I create a fourth level of map in preparation for 3 levels of offset, the map-connection breaks. The code examples below show only to the level 2 and level 3 offset maps, and these are the maps on the left hand side of the diagrams, as annotated. Offset of offset is OK like this map 1-BottomUpPlan-Bottom \ -projection plan 1-BottomUpPlan-s2 break 1-BottomUpPlan-s1 #bottom terminal chamber endmap 1-BottomUpPlan-Bottom Offset of offset is not OK when same as above but map-of-scraps is split into map-of-maps that references maps-of-scraps ##Setup for OffsetLevel 3 map 1-BottomUpPlan-Bottom \ -projection plan 1-BottomUpPlan-B2 # break 1-BottomUpPlan-B1 endmap 1-BottomUpPlan-Bottom map 1-BottomUpPlan-B2 \ -projection plan 1-BottomUpPlan-s2 endmap 1-BottomUpPlan-B2 map 1-BottomUpPlan-B1 \ -projection plan 1-BottomUpPlan-s1 #bottom terminal chamber endmap 1-BottomUpPlan-B1 Offset of offset of offset is OK BUT its parent is not (as above) ##Setup for OffsetLevel 3 map 1-BottomUpPlan-Bottom \ -projection plan 1-BottomUpPlan-B2 # break 1-BottomUpPlan-B1 [0 10] below #OffsetLevel 3 endmap 1-BottomUpPlan-Bottom map 1-BottomUpPlan-B2 \ -projection plan 1-BottomUpPlan-s2 endmap 1-BottomUpPlan-B2 map 1-BottomUpPlan-B1 \ -projection plan 1-BottomUpPlan-s1 #bottom terminal chamber endmap 1-BottomUpPlan-B1 For what it is worth, here is the overall survey file, consistent with my SAMD-ITF-IS pattern: survey Cave map CavePlan -projection plan 2-EntrancePlan@2 1-BottomUpPlan@1 [0 -20] below #OffsetLevel 1 endmap CavePlan input 1-BottomUp.th input 2-Entrance.th centreline equate 1.4@1 <mailto:1.4@1> 1.4@2 <mailto:1.4@2> endcentreline endsurvey Cave So Tarquin, Can you pick any fundamnetal differences? Are we doing the same things? Are we talking about the same things?

1 0

Line convert-to-curve seems to be broken in XTherion
by Mykyta Kozlov 26 Feb '23

26 Feb '23

Looks like converting polylines to beziers in Xtherion stopped working correctly starting from version 6.1.4. With 6.1.3 all works ok. Screenshots attached.

3 2

Convex hall in loch file wall interpolation
by עמרי גסטר 04 Feb '23

04 Feb '23

Hi All, I wondered if there is a possibility to add an option of convex hall to interpolate the walls in the loch file. I really like that option in Topodroid 3d app and I believe it can generate a volume calculation that is more reliable. What do you think about it?

1 0

Therion vs. Proj 9 - Fedora 37
by Bill Gee 12 Jan '23

12 Jan '23

A few months ago when Fedora 37 came out, I found that Therion will not run because of a change in the version of proj. Jim Begley noted that he was taking a stab at getting Therion to compile on Fedora 37 and proj 9. Since then I have heard nothing. If I use dnf install therion on a Fedora 37, it tells me there is no such package. And yes, it has the copr repository file. Is there any update? I have two systems which cannot be upgraded to Fedora 37 because of this issue. Thanks! -- =============== Bill Gee

3 4

new Therion 6.1.6
by Therion 11 Jan '23

11 Jan '23

Hi, there is a new release 6.1.6 of Therion. Check https://github.com/therion/therion/releases/tag/v6.1.6 for more details. Best regards, Therion team

1 0

Upgrade to Fedora 37 - Problems with proj packages
by Bill Gee 04 Jan '23

04 Jan '23

I think this is not really a Therion problem, but it is likely to affect Therion users who run Fedora. The recent release of Fedora 37 does not have the proj package that Therion requires. Attempting an upgrade gives this: Error: Problem: package therion-6.1.2-1.fc36.x86_64 requires libproj.so.22()(64bit), but none of the providers can be installed - proj-8.2.1-6.fc36.x86_64 does not belong to a distupgrade repository - problem with installed package therion-6.1.2-1.fc36.x86_64 -- =============== Bill Gee

3 3

new Therion 6.1.5
by Therion 30 Dec '22

30 Dec '22

Hi, there is a new release 6.1.5 of Therion. Check https://github.com/therion/therion/releases/tag/v6.1.5 for more details. Best regards, Therion team

1 0

new Therion 6.1.4
by Therion 28 Dec '22

28 Dec '22

Hi, there is a new release 6.1.4 of Therion. Check https://github.com/therion/therion/releases/tag/v6.1.4 for more details. Best regards, Therion team

2 1