| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| extend [2018/06/08 22:13] – [extend] ignore breaks loop, better terminology brucemutton | extend [2018/08/08 02:19] – [Extended elevation scrap drawing considerations] add -flip none brucemutton |
|---|
| There should only be one 'start' specification I think, but there seems to be no ill effect if there are multiple starts.\\ | There should only be one 'start' specification I think, but there seems to be no ill effect if there are multiple starts.\\ |
| \\ | \\ |
| ''extend right <leg>'' - extend this leg only, to the right, then continue extending subsequent legs, left or right, as per the leg immediately previous.\\ | ''extend right <leg>'' - extend this leg only, to the right, then continue extending subsequent legs, left or right, as per the leg immediately previous. But sometimes it continues generating all legs, as per the next entry below!\\ |
| ''extend right <station>'' - continue generating all extended centreline legs from this station onwards, towards the right. Usually this option will not work as described, unless it is preceded by one or two ‘extend right <leg> statements.\\ | ''extend right <station>'' - continue generating all extended centreline legs from this station onwards, towards the right. Usually this option will not work as described, unless it is preceded by one or two ''extend right <leg>'' statements. And sometimes it can appear to extend the wrong way. If this happens, use ''extend ... <leg>'' rather than ''extend ... <station>''\\ |
| ''extend left <leg> or <station>'' - same as for extend right, but extending left!\\ | ''extend left <leg> or <station>'' - same as for extend right, but extending left!\\ |
| \\ | \\ |
| ''extend reverse <station>'' - continue generating all extended centreline legs from this station onwards, in the opposite direction to the leg immediately previous.\\ | ''extend reverse <station>'' - continue generating all extended centreline legs from this station onwards, in the opposite direction to the leg immediately previous.\\ |
| \\ | \\ |
| ''extend vertical <leg>'' - do not extend this leg horizontally, extend only the vertical component of this leg, then continue extending subsequent legs as per leg immediately previous.\\ | ''extend vertical <leg>'' - do not extend this leg horizontally, extend only the vertical component of this leg, then continue extending subsequent legs as per leg immediately previous. The order of stations in your vertical statement should usually match the direction of extended elevation centreline generation. However if Therion seems to ignore this vertical statement, try reversing the order of the stations in your vertical statement, and it might work!\\ |
| ''extend vertical <station>'' - continue generating only the vertical components all extended centreline legs from this station onwards.\\ | ''extend vertical <station>'' - continue generating only the vertical components all extended centreline legs from this station onwards.\\ |
| \\ | \\ |
| ''extend ignore <station>'' - where <station> is one leg past a junction in the direction of generation. The generation of extended centreline shall not take this leg. I have found this syntax unreliable, and the following may explain why. Marco Corvi says (if I understand correctly) this does not work where there are only three legs meeting at a junction ie the usual case. So only for use where 4 or more legs meeting at junction(?). | ''extend ignore <station>'' - where <station> is one leg past a junction in the direction of generation. The generation of extended centreline shall not take this leg. I have found this syntax unreliable, and the following may explain why. Marco Corvi says (if I understand correctly) this does not work where there are only three legs meeting at a junction ie the usual case. So only for use where 4 or more legs meeting at junction(?). |
| Also do not use this syntax where <station> IS the junction station, obviously that will have unpredictable results. \\ | Also do not use this syntax where <station> IS the junction station, obviously that will have unpredictable results. \\ |
| Extend break is mentioned in some Therion posts, presumably as an alias for extend ignore (Survex terminology). It will trigger a Therion error “unknown extend flag – break”.\\ | <del>''extend break''</del> is mentioned in some Therion posts, presumably as an alias for extend ignore (Survex terminology). It will trigger a Therion error “unknown extend flag – break”.\\ |
| Sometimes branch centrelines will be ignored (hidden?) by default, and an extend right (or similar) statement will be required to stimulate it’s generation.\\ | Sometimes branch centrelines will be ignored (hidden?) by default, and an extend right (or similar) statement will be required to stimulate it’s generation.\\ |
| \\ | \\ |
| |
| ====Extended elevation scrap drawing considerations==== | ====Extended elevation scrap drawing considerations==== |
| If you have drawn a scrap with the opposite orientation to the extended centreline generation, it will tend to plot inside out. You need to compensate for this by including ''-flip horizontal'' in the definition of your scrap. Or you can add ''-revise scrap-id -flip horizontal'' in your Extend-CaveName-ElevEXT.th file. | If you have drawn a scrap with the opposite orientation to the extended centreline generation, it will tend to plot inside out. You need to compensate for this by including ''-flip horizontal'' in the definition of your scrap. Or you can add ''-revise scrap-id -flip horizontal'' or ''-flip none'' in your Extend-CaveName-ElevEXT.th file. |
| |
| If you include in your scrap drawing a ''point station -name <station>'' where that <station> is at a survey leg junction AND is offset in the extended centreline due to extended loop misclosure, then it will force the extended station to plot, incorrectly, in its original location, distorting the scrap in the vicinity of that leg. This can be vexing, as \\ | If you include in your scrap drawing a ''point station -name <station>'' where that <station> is at a survey leg junction AND is offset in the extended centreline due to extended loop misclosure, then it will force the extended station to plot, incorrectly, in its original location, distorting the scrap in the vicinity of that leg. This can be vexing, as \\ |