We can control whether Therion or Survex loop closures are used, and the default is Survex, if it is installed on the same machine as far as I recall. Mine is using Survex loop closures and I am getting log reporting from Survex 1.2.6

My inference from warnings I get on other occasions is that Survex reports fixed stations that are not connected to any survey leg.  I have many of these in other files – gps locations of surface features for example.  I imagine the ‘equate’ part of the processing is different, and in any case neither Survex nor Therion are reporting the anomaly when Therion is run.

This is different, and I believe it should be reported by Therion as either a warning or perhaps preferably should stop execution.  When equates are defined, I would have expected that it would be required that all equated stations have been defined elsewhere, and if they are not, it should be an exception that should raise and exception or at least a warning.

Bruce

---

From: therion-bounces@speleo.sk [mailto:therion-bounces@speleo.sk] On Behalf Of Footleg
Sent: Saturday, 30 November 2013 10:55 p.m.
To: List for Therion users
Subject: Re: [Therion] equate to non-existant station does not raise error

Does the log file contain a warning? I thought that it was using Survex under the hood, and that warns of stations referred to but not used in any fix or leg.

On 29 Nov 2013 20:07, "Bruce" <bruce@tomo.co.nz> wrote:

This may have been raised before.

 If a typing error is made in a station equate statement, no error is raised.

For example in the following station kb51.29@kb does not exist, therefore the loop is not closed as the user intended.

    equate kb51.29@kb kb51.29@57

Can an error be raised in this circumstance please.

Regards

Bruce Mutton