warning -- equate used to define new station
Hello Is there a way to suppress a warning about new station? I'm trying to simplify the stations binding such way: 1.th: equate Fixed@cave Fixed@some.path.at.cave 2.th: equate Fixed@cave Fixed@other.path.at.cave -- WBR, Vasily
Vasily
From memory this behaviour was improved some time ago. In 5.3.12 * warning raised, if equate statement creates new station in some subsurvey
Provided all three stations in your example exist already, you should get no warning. If one or two of the stations do not exist, you will get a warning message to the effect that you have created a new station by using an equate statement. This is appropriate behaviour I think. I have checked through half a dozen of my therion.log files for projects where I have done exactly what you appear to have done below (although mostly for 2 stations, not 3), and there are no warnings about new stations. So, to clarify my understanding of your example. Fixed@cave = is for example a gps coordinate, defined elsewhere with a fix statement. Fixed@some.path.at.cave = is a survey station that is defined in a survey, for that same location. Fixed@other.path.at.cave = is another survey station that is defined in, perhaps, some other survey. All three stations represent exactly the same physical location. Bruce -----Original Message----- From: Therion [mailto:therion-bounces@speleo.sk] On Behalf Of Vasily Vl. Suhachev via Therion Sent: Tuesday, 1 August 2017 10:45 PM To: List for Therion users <therion@speleo.sk> Cc: Vasily Vl. Suhachev <v_su@inbox.ru> Subject: [Therion] warning -- equate used to define new station Hello Is there a way to suppress a warning about new station? I'm trying to simplify the stations binding such way: 1.th: equate Fixed@cave Fixed@some.path.at.cave 2.th: equate Fixed@cave Fixed@other.path.at.cave -- WBR, Vasily _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Hi, Bruce Fixed@cave is a nonexistent station (nor defined nor fixed). Therion is right with warning but it is exactly what I need. I'm try to define station in upper namespace for link to it from other places. It is worked proper but throw a warning... After the experiments I found a workaround. This code removes warning but it a bit verbose and not obvious... survey cave centerline data nosurvey from to Fixed Fixed@some.path.at.cave equate Fixed Fixed@some.path.at.cave endcenterline endsurvey 02.08.2017 02:53, Bruce Mutton via Therion пишет:
So, to clarify my understanding of your example. Fixed@cave = is for example a gps coordinate, defined elsewhere with a fix statement. Fixed@some.path.at.cave = is a survey station that is defined in a survey, for that same location. Fixed@other.path.at.cave = is another survey station that is defined in, perhaps, some other survey. All three stations represent exactly the same physical location.
-- WBR, Vasily
Vasily, I don’t understand the reason of such solution. If you know gps coordinate of a station, you may use fix for it. And than equate those fixed stations. Way you need to add third virtual station with GPS coordinates? Are you trying to create a survey with only one station with GPS coordinates? Martin
2. 8. 2017 v 8:35, Vasily Vl. Suhachev via Therion <therion@speleo.sk>:
Hi, Bruce Fixed@cave is a nonexistent station (nor defined nor fixed). Therion is right with warning but it is exactly what I need. I'm try to define station in upper namespace for link to it from other places. It is worked proper but throw a warning...
After the experiments I found a workaround. This code removes warning but it a bit verbose and not obvious... survey cave centerline data nosurvey from to Fixed Fixed@some.path.at.cave equate Fixed Fixed@some.path.at.cave endcenterline endsurvey
02.08.2017 02:53, Bruce Mutton via Therion пишет:
So, to clarify my understanding of your example. Fixed@cave = is for example a gps coordinate, defined elsewhere with a fix statement. Fixed@some.path.at.cave <mailto:Fixed@some.path.at.cave> = is a survey station that is defined in a survey, for that same location. Fixed@other.path.at.cave <mailto:Fixed@other.path.at.cave> = is another survey station that is defined in, perhaps, some other survey. All three stations represent exactly the same physical location.
-- WBR, Vasily _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Hi, Martin I'm trying to create synonym with short name for station defined in deep hierarchy of namespaces (in purpose for more readable sources) 02.08.2017 13:58, Martin Sluka via Therion пишет:
Are you trying to create a survey with only one station with GPS coordinates?
-- WBR, Vasily
Vasily Looks like what you are calling a solution is what I would call a bug. Assuming that the warning is the correct response from Therion when a new station is defined using ‘equate’… You have broken that by adding a ‘no-survey’ shot between the new station and the original station, and making your survey data more complicated in the process. Surely it is reassuring to have Therion confirm to you that you have created a new station simply by equating to a non-existent station. Usually this would not be an intended action, so the warning is appropriate and reassuring. I suggest this be added to the list of bugs to be fixed – ie ensure that no-survey does not supress ‘equate used to define new station’ warning. Bruce From: Therion [mailto:therion-bounces@speleo.sk] On Behalf Of Vasily Vl. Suhachev via Therion Hi, Bruce Fixed@cave is a nonexistent station (nor defined nor fixed). Therion is right with warning but it is exactly what I need. I'm try to define station in upper namespace for link to it from other places. It is worked proper but throw a warning... After the experiments I found a workaround. This code removes warning but it a bit verbose and not obvious... survey cave centerline data nosurvey from to Fixed Fixed@some.path.at.cave <mailto:Fixed@some.path.at.cave> equate Fixed Fixed@some.path.at.cave <mailto:Fixed@some.path.at.cave> endcenterline endsurvey 02.08.2017 02:53, Bruce Mutton via Therion пишет: So, to clarify my understanding of your example. Fixed@cave = is for example a gps coordinate, defined elsewhere with a fix statement. Fixed@some.path.at.cave <mailto:Fixed@some.path.at.cave> = is a survey station that is defined in a survey, for that same location. Fixed@other.path.at.cave <mailto:Fixed@other.path.at.cave> = is another survey station that is defined in, perhaps, some other survey. All three stations represent exactly the same physical location. -- WBR, Vasily
Ok Have we a legal way to define a station to "equate" to? Or recipe to export already defined station to upper namespace as in Survex with its (deprecated) global prefix "\"? 02.08.2017 15:00, Bruce Mutton via Therion пишет:
Looks like what you are calling a solution is what I would call a bug.
-- WBR, Vasily
Hi Vasily A warning does not make what you were doing ‘illegal’. The warning message is Therion providing helpful feedback about your dataset. Looks like your original post was achieving exactly what you wanted, simply and explicitly. You just have to be relaxed about the warning message. Some of my projects have hundreds of warning messages. I look at them from time to time to make sure there is nothing unexpected, then I accept and forget about them. Bruce From: Therion [mailto:therion-bounces@speleo.sk] On Behalf Of Vasily Vl. Suhachev via Therion Sent: Wednesday, 2 August 2017 8:43 PM To: therion@speleo.sk Cc: Vasily Vl. Suhachev <v_su@inbox.ru> Subject: Re: [Therion] warning -- equate used to define new station Ok Have we a legal way to define a station to "equate" to? Or recipe to export already defined station to upper namespace as in Survex with its (deprecated) global prefix "\"? 02.08.2017 15:00, Bruce Mutton via Therion пишет: Looks like what you are calling a solution is what I would call a bug. -- WBR, Vasily
On Wed, Aug 02, 2017 at 03:42:47PM +0700, Vasily Vl. Suhachev wrote:
Have we a legal way to define a station to "equate" to? Or recipe to export already defined station to upper namespace as in Survex with its (deprecated) global prefix "\"?
You don't need to use deprecated features to achieve this in Survex, you can pretty much just do what it seems you are trying to do with Therion: *begin cave *equate fixed some_path.fixed *begin some_path fixed 2 10.00 090 00 *end some_path *equate fixed other_path.fixed *begin other_path fixed 2 12.34 180 00 *end other_path *end cave Survex doesn't warn about using *equate to create a "well-known" alias for a station. That's one of the intended uses for *equate. Cheers, Olly
Hi Olly, it is clear, that there are very useful features in Survex which are not in Therion and vice versa. Isn’t the right time to make a developer conference of both clans together? ;) m.s.
3. 8. 2017 v 3:04, Olly Betts via Therion <therion@speleo.sk>:
On Wed, Aug 02, 2017 at 03:42:47PM +0700, Vasily Vl. Suhachev wrote:
Have we a legal way to define a station to "equate" to? Or recipe to export already defined station to upper namespace as in Survex with its (deprecated) global prefix "\"?
You don't need to use deprecated features to achieve this in Survex, you can pretty much just do what it seems you are trying to do with Therion:
*begin cave *equate fixed some_path.fixed *begin some_path fixed 2 10.00 090 00 *end some_path *equate fixed other_path.fixed *begin other_path fixed 2 12.34 180 00 *end other_path *end cave
Survex doesn't warn about using *equate to create a "well-known" alias for a station. That's one of the intended uses for *equate.
Cheers, Olly _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
On 2017-08-02 20:00 +1200, Bruce Mutton via Therion wrote:
Vasily
Looks like what you are calling a solution is what I would call a bug.
Doesn't look like a bug to me.
Assuming that the warning is the correct response from Therion when a new station is defined using ‘equate’…
agreed.
You have broken that by adding a ‘no-survey’ shot between the new station and the original station, and making your survey data more complicated in the process.
No, he's done exactly what he wanted, which is to explicitly define a new station name and equate it to an existing one (without distorting the network). There is no reason why therion should issue an 'accidentally created station' warning about this.
Surely it is reassuring to have Therion confirm to you that you have created a new station simply by equating to a non-existent station. Usually this would not be an intended action, so the warning is appropriate and reassuring.
It's not non-existant - that's the point. It exists, but has no explicit position.
I suggest this be added to the list of bugs to be fixed – ie ensure that no-survey does not supress ‘equate used to define new station’ warning.
I disagree. This is a rather odd use of 'no-survey', but it seems to me to be valid. I wouldn't go to all this trouble just to make the names shorter, but if one wants to do that I see nothing wrong with it. It would perhaps be better to invent an 'alias' command for simple alternative name of existing points, which is what Vasily actually wants (except that Survex has already defined an alias command which does something slightly different, so maybe it would have to be altname or something). Vasily - you might want to file this as a 'wishlist' item on the therion github. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
participants (5)
-
Bruce Mutton -
Martin Sluka -
Olly Betts -
Vasily Vl. Suhachev -
Wookey