[Therion] log extend

[Bruce Mutton]

>It looks there was a copy/paste error in the code :/ In the latest commit, it should be fixed I hope.

> Could you please check it once again?  therion-setup-dev-5119596

 

And with this more complicated example things unravel a little more.  Nothing has changed in this project since logs below from 4 December.  The pdf outputs are fine, but the log still starts where there is no START (and not honouring the START 1.0 as in the image below), and there seem to be even more strange artefacts.

Near the beginning there is a lot of bouncing around between 4.23 at 4 and - at 4...

 

calculating basic statistics ... done

processing extended elevation ... 

START 4.24 at 4.MrTPot

LEFT 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

RIGHT - at 4.MrTPot

BACK 4.23 at 4.MrTPot

LEFT 4.22 at 4.MrTPot <mailto:4.22 at 4.MrTPot> 

 

It goes on like this gradually stepping along the survey .  Seems it is tracking every single splay shot.

In some of the subsurveys it seems like it is not tracking the splays, and in others only one splay per leg, even though there are many splays.  So not consistent.

 

Also after about 7200 lines, it seems like it has stopped logging early.

 

Bruce

 

From: Therion <therion-bounces at speleo.sk> On Behalf Of Bruce Mutton
Sent: Wednesday, 4 December 2019 22:35
To: 'List for Therion users' <therion at speleo.sk>
Subject: [Therion] log extend

 

Here is what happens with a real project that I did a year ago.

As far as extended elevations go, it is a well-behaved project, that was built incrementally, starting with survey 1, then 2 etc.

While the extended network behaves well, the log does not do so well.  Here is a small sample.

Curiously the extend log shows it starting in the middle of the survey sequence (it goes to survey 6 or 7) at a random entrance.  There is no start 4.24 in the data, only a start 1.0!

 

And yet…

 



 

Two more things:

The sequence from 4.20 to 4.19 all the way to 4.15 is extending right, but the log says it is left.

I deduce that the sequence then steps back along the same network until it is time to extend along a new branch.  That is what the BACK refers to (nice).

 

Here is what the specified extended network that generates both of the images above look like.



 

and much further down the table it gets to the bit of passage in the image above…

 



 

So, the extend log, although following a credible path along the survey network, has some directional errors, and is nothing like the specified path.

 

Curiously, this log, like the logs for some other projects of mine, end with some apparently random non-existent STARTs and stations that don’t necessarily exist, like - at 1 in the sequence below.

 



 

So, this feature has real promise, but I wonder if there is a bug, and now I am really interested how the extend specifications and logs compare in Tarquin’s short oxbow examples.

 

Bruce

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20191207/b84bba65/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 131819 bytes
Desc: not available
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20191207/b84bba65/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 94184 bytes
Desc: not available
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20191207/b84bba65/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 121389 bytes
Desc: not available
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20191207/b84bba65/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 123342 bytes
Desc: not available
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20191207/b84bba65/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 68111 bytes
Desc: not available
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20191207/b84bba65/attachment-0004.png>