faq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
faq [2018/03/23 08:13] – [How do I specify a main entrance, and also the other entrances?] brucemuttonfaq [2023/10/16 10:27] (current) – Visualising drawing errors and distortion - clarify debug dots and colours brucemutton
Line 150: Line 150:
  
 Xtherion "normal": {{therion:join_scraps_normal_xtherion.gif?120}} pdf "normal": {{therion:join_scraps_normal_pdf.gif?120}} Xtherion "tricky": {{therion:join_scraps_tricky_xtherion.gif?120}} pdf "tricky": {{therion:join_scraps_tricky_pdf.gif?120}} //Click on picture to see original size// Xtherion "normal": {{therion:join_scraps_normal_xtherion.gif?120}} pdf "normal": {{therion:join_scraps_normal_pdf.gif?120}} Xtherion "tricky": {{therion:join_scraps_tricky_xtherion.gif?120}} pdf "tricky": {{therion:join_scraps_tricky_pdf.gif?120}} //Click on picture to see original size//
 +
 +There is much simpler way - just by join command. Create in one scrap invisible line wall on open end with just tree not smooth points. Join the middle point of this line (l_line:1) to end or beginning of appropriate line of one of another scraps.  
  
 see also [[tips#joining_scraps_together]] see also [[tips#joining_scraps_together]]
Line 381: Line 383:
 ====How do export centerline only?==== ====How do export centerline only?====
  
-There are two types of maps definitions - one from scraps and other maps and second only from surveys. There is not possible to combine these two definitions in Therion.+There are two types of maps definitions - one from scraps and other maps and second only from surveys. You can also create a map of both maps and surveys, which will show both the scraps within the maps, and the centreline for the surveys (allowing you to show the surveys for parts where you have not yet drawn the scraps) - note that you now cannot hide the centreline.
  
     survey index_survey -title "Perlová jaskyňa"     survey index_survey -title "Perlová jaskyňa"
Line 472: Line 474:
  
 Imagine the plan view of the cave straightened so that all of the passages lie on a single line from left to right (or vice versa). Imagine the plan view of the cave straightened so that all of the passages lie on a single line from left to right (or vice versa).
-Now imagine viewing this straightened cave from the side - this is an extended elevation (often called a developed, or unrolled elevation).  The passages are all shown with their true slope as you would experience it travelling through the cave.  Very good for producing a route guide elevation for a vertical cave.+Now imagine viewing this straightened cave from the side - this is an extended elevation (often called a developed, or unrolled elevation).  The passages are all shown with their true slope as you would experience it travelling through the cave.  Very good for producing a route guide elevation for a vertical cave.  Check out [[extend|Extended Elevations]] page.
  
  
Line 563: Line 565:
 If you create an object outside the //scrap ... endscrap// construction, you can use //Move up, Move down// or //Move to// buttons in the map editor window to move the object to the desired place. See the attached picture.\\ {{therion:move_object_to_scrap.gif?120}} //Click on image to see original size// If you create an object outside the //scrap ... endscrap// construction, you can use //Move up, Move down// or //Move to// buttons in the map editor window to move the object to the desired place. See the attached picture.\\ {{therion:move_object_to_scrap.gif?120}} //Click on image to see original size//
  
-====How do I use Debug Mode in Layout?====+====How do I use Debug Mode in Layout?  Visualising drawing errors and distortion====
  
 If your map is coming out distorted or joins are not connecting in the right place then debug mode is a very useful way to see what is going on. Indeed it is generally useful to get a visual display of the distortions in the map. If your map is coming out distorted or joins are not connecting in the right place then debug mode is a very useful way to see what is going on. Indeed it is generally useful to get a visual display of the distortions in the map.
  
-You turn it on by putting ''debug on'' or ''debug all'' in your layout command for the map.+You turn it on by putting ''debug on'' or ''debug all'' (which each have the same effect) in your layout command for the map.  The default is ''debug off''. 
 + 
 +You can also choose individual debug components, for more refined control;  ie 
 + 
 +''debug first'' # first transformation, red lines - scrap rotated and scaled only \\ 
 +''debug second'' # second transformation, blue lines - scrap morphed according to station positions \\ 
 +''debug scrap-names'' \\ 
 +''debug station names'' \\ 
 +  
 +This enables you to obtain only the particular information you require.
  
   layout debug   layout debug
Line 582: Line 593:
   * **blue-lines** - scraps adjusted to survey stations (before processing joins)   * **blue-lines** - scraps adjusted to survey stations (before processing joins)
  
-  * **red points** - original positions of survey stations +  * **small red points** - original positions of survey stations 
-  * **yellow points** connected by yellow line - original position of two points in scrap with maximal distortion                                                                   +  * **large yellow points** connected by yellow line - original position of two points in scrap with maximal distortion                                                                   
-  * **black points** connected by black line - final position of two points in scrap with maximal distortion +  * **large black points** connected by black line - final position of two points in scrap with maximal distortion 
-  * **orange points** - the points with distance changed most during transformation                                                                              +  * **large red points** - the (station) points with distance changed most during transformation                                                                              
  
   * **yellow lines** connecting black and yellow points indicate how these points were shifted                                                                         * **yellow lines** connecting black and yellow points indicate how these points were shifted                                                                      
Line 596: Line 607:
    - The size of the maximum distortion (for a scrap) is proportional to the distance between the black point from it's corresponding yellow point (black and yellow joined by yellow).    - The size of the maximum distortion (for a scrap) is proportional to the distance between the black point from it's corresponding yellow point (black and yellow joined by yellow).
    - If the black points are obscured under the corresponding yellow points, then the maximum distortion is not very much at all.    - If the black points are obscured under the corresponding yellow points, then the maximum distortion is not very much at all.
-   - Spacing of matched pairs of yellow points, or black points is of little significance, perhaps it is an indication of the size of area in the scrap that has 'maximum distortion'.+   - Spacing of matched pairs of yellow points, or black points is of little significance. Perhaps it is, together with the large red point (if present), an indication of the size of area in the scrap that has 'maximum distortion'.
  
 We can create a special layout to hide distracting features, and emphasize the debug characteristics we are interested in. We can create a special layout to hide distracting features, and emphasize the debug characteristics we are interested in.
Line 612: Line 623:
   colour preview-below 80    colour preview-below 80 
   colour preview-above 80     colour preview-above 80  
 +  ## Consider invoking 'maps off' in your thconfig file to suppress offsets and previews due to map definitions
   opacity 10 #mostly transparent   opacity 10 #mostly transparent
      
   debug all #turns on all debug options, for visible entities only   debug all #turns on all debug options, for visible entities only
 +  #or for more refined control...
 +  # debug first   # red lines
 +  # debug second  # blue lines
 +  # debug scrap-names
 +  # debug station-names
      
 ## Options to control text size   ## Options to control text size  
Line 646: Line 663:
  
 TO DO: Add some pictures TO DO: Add some pictures
 +
 +See also [[faq#how_to_solve_the_incorrectly_determined_interior_of_the_scrap]] below
 +
 +====How do I find miss-drawn holes in scraps?====
 +Each scrap defines a piece of cave passage, which (almost) always is defined by walls, being the boundary between a rock mass and the open space of the passage.  There will be open ends of scraps, with no walls, where the open space (passage) continues beyond the scrap.
 +
 +If these openings are very wide, then you may have to close the opening with a wall line with ''-visibility off'' or ''-subtype invisible''.\\
 +If you want to draw a wall 'inside' a scrap, you must disable its passage defining properties, by setting ''-outline none''.\\
 +If you have an oxbow, or large pillar, then you need to set ''-outline in''.\\
 +
 +If you follow these rules, Therion can correctly determine what is 'cave' and what is 'rock', at least for pdf outputs.  Sometimes it is a bit tricky, especially if adjacent scraps are 'joined' and as drawn they overlap or have significant gaps (you should never do this intentionally).
 +
 +And beyond this, if you want your kml __maps__ and 3d outputs to be generated correctly, you will also need to get the wall line orientations correct.  The yellow tick mark on the left of the line as you draw it must point towards the passage side of the line.  More on this on the [[drawingchecklist#wall|drawing checklist]] page.  You can adjust it with ''-reverse on|off''.
 +
 +If you get it wrong, you can get significant distortion and incorrect colouring in your 2d and 3d outputs. 
 +
 +Here is a layout that you can apply to your export statement. ie ''export map -output cave.pdf ... -layout LayoutCheckScrapsForHoles''
 +
 +  layout LayoutCheckScrapsForHoles
 +  ## Martin Sluka Nov2019
 +  ## Hides most objects and emphasises passage interiors and walls
 +  ## Does not check for correct line orientation (-reverse on|off). You need to export a map to kml to check line wall orientations
 +    symbol-hide group all
 +    symbol-show line wall
 +    debug station-names
 +    debug scrap-names
 +    colour map-bg 85
 +  endlayout LayoutCheckScrapsForHoles
 +  
 + Here is what it looks like.  Grey areas inside or between scraps mean there is a problem that you need to fix.\\
 +{{therion:LayoutCheckScrapsForHoles.png?120}} //Click on picture to see original size//
 +
 +====How to solve the incorrectly determined interior of the scrap====
 +
 +  Warning: scrap outline intersects itself in bmb3_s3@fake. 
 +
 +  Warning: invalid scrap outline in bmb3_s3@fake. 
 +
 +//I have this warning in a few scraps in that survey - I wondered how serious it was, and what I should do about it. But without more details of _where_ it intersects itself (and why this is a problem), I could not do anything but ignore it.//
 +
 +The only information we can give here is the scrap name. There is no way how to find out in MetaPost where exactly the closed path intersects itself :-(
 +
 +//I have several more scraps which I cannot include in the overall survey at the moment because if I do I get cryptic metapost errors. We have to work out a way of getting better feedback to the user about _where_ the problem lies as it is currently extremely difficult to fix as you don't know which of many lines is at fault.//
 +
 +We think it's doable to give a line number in th2 file where the error occurs. It would be perhaps possible to also identify area border lines which don't intersect.
 +
 +//How did you find the above problem. If I understood the process you used to find this it might help me next time.//
 +
 +We got this error (incorrectly determined interior of the scrap) long time ago in Dead Bats Cave map. There was some strange clipping by the scrap border, which we couldn't explain. In that time there was no MP warning, no map colouring. We don't remember exactly but it took quite long till we identified that the problem is in the border and than what is wrong with the border. After reading thoroughly the appropriate chapter of the Metafont book we knew that problem is in the loop -- but even than we couldn't find any -- so small it was, in fact very similar to yours.
 +
 +We added the MP warning to point to this problem. When we see it now, we first check scrap ends if something could cause the problem. The biggest problem is if the loop is introduced only after morphing the scrap ends before joining scraps. We can only recommend to move control point in the last bezier arc of wall just before the scrap end, run therion, undo the change by pressing Ctrl+Z and repeat with other walls until the problem remains.
 +
 +The loop may occur also in the middle of the wall, but it should be visible, at least in 400% zoom.
 +
 +We are sorry that there is no cleverer algorithm to find the loop :(
 +
 +see also [[faq#What_constitutes_a_"pillar"_in_therion?|What constitutes a "pillar" in therion?]]
 +
 +(There are some other scrap drawing tips in [[tips#avoiding_invisible_or_misshapen_scraps_in_loch_and_google_earth|Avoiding Invisible or Misshapen Scraps in Loch and Google Earth]])
 +
 +This warning can sometimes happen if you have two wall lines joining on a single point, where Bézier curve controls pull the lines into a very acute angle (where the "back" facing Bézier controls are pulled beyond the arc of the other line). The solution is to reduce the angle of the join, or insert more linepoints so that the angle can be produced without needing to use Bézier controls to pull the lines so far that Metapost thinks they overlap. Check any such places in your scrap outline, and test whether removing the Bézier back or forward controls fixes it. If so, then this is the location of your error.
 +
 +It can also happen if a wall line has one of its Bézier controls pulled far enough to cross the opposite wall of the passage. Basically, even though the rendered walls might not actually touch because of the curves, you still need to be able to draw a line that connects all of the line points *and control points* in sequence, without crossing the far wall of the passage.
 +
 +It can also happen if you have inserted a point along a wall line, with its Bézier controls oriented backwards compared with the rest of the line, so that the backwards one points forwards, or vice versa. The rendering looks normal, but Metapost has had to flip the orientation of the line twice, so it complains.
 +
 +It can also happen if you have accidentally added two linepoints at the same location - this also causes Metapost to flip directions in order to get from one point to the next. Step through each linepoint in turn (in the "Lines" section of XTherion), and see if two ended up in the same place.
 +
 +It can also happen on a closed wall line, when the ends join, and you pull the wrong Bézier control past the junction - this causes a combination of the two problems mentioned above.
 +
 +
 ====How to solve strange errors?==== ====How to solve strange errors?====
  
Line 699: Line 787:
  
 There is actually nothing wrong with that arrow -- that is the reason why it took so long to find it :) It has the last control point identical with the last point, which is perfectly acceptable in metapost. Unfortunately there is some bug in the arrow definition, which doesn't allow this. I hope it will be possible to fix it. In the meantime you may change the line either to a straight segment (no control points) or add a control point different from the endpoint. There is actually nothing wrong with that arrow -- that is the reason why it took so long to find it :) It has the last control point identical with the last point, which is perfectly acceptable in metapost. Unfortunately there is some bug in the arrow definition, which doesn't allow this. I hope it will be possible to fix it. In the meantime you may change the line either to a straight segment (no control points) or add a control point different from the endpoint.
- 
-====How to solve the incorrectly determined interior of the scrap==== 
- 
-  Warning: scrap outline intersects itself in bmb3_s3@fake.  
- 
-//I have this warning in a few scraps in that survey - I wondered how serious it was, and what I should do about it. But without more details of _where_ it intersects itself (and why this is a problem), I could not do anything but ignore it.// 
- 
-The only information we can give here is the scrap name. There is no way how to find out in MetaPost where exactly the closed path intersects itself :-( 
- 
-//I have several more scraps which I cannot include in the overall survey at the moment because if I do I get cryptic metapost errors. We have to work out a way of getting better feedback to the user about _where_ the problem lies as it is currently extremely difficult to fix as you don't know which of many lines is at fault.// 
- 
-We think it's doable to give a line number in th2 file where the error occurs. It would be perhaps possible to also identify area border lines which don't intersect. 
- 
-//How did you find the above problem. If I understood the process you used to find this it might help me next time.// 
- 
-We got this error (incorrectly determined interior of the scrap) long time ago in Dead Bats Cave map. There was some strange clipping by the scrap border, which we couldn't explain. In that time there was no MP warning, no map colouring. We don't remember exactly but it took quite long till we identified that the problem is in the border and than what is wrong with the border. After reading thoroughly the appropriate chapter of the Metafont book we knew that problem is in the loop -- but even than we couldn't find any -- so small it was, in fact very similar to yours. 
- 
-We added the MP warning to point to this problem. When we see it now, we first check scrap ends if something could cause the problem. The biggest problem is if the loop is introduced only after morphing the scrap ends before joining scraps. We can only recommend to move control point in the last bezier arc of wall just before the scrap end, run therion, undo the change by pressing Ctrl+Z and repeat with other walls until the problem remains. 
- 
-The loop may occur also in the middle of the wall, but it should be visible, at least in 400% zoom. 
- 
-We are sorry that there is no cleverer algorithm to find the loop :( 
- 
-see also [[faq#What_constitutes_a_"pillar"_in_therion?|What constitutes a "pillar" in therion?]] 
- 
-(There are some other scrap drawing tips in [[tips#avoiding_invisible_or_misshapen_scraps_in_loch_and_google_earth|Avoiding Invisible or Misshapen Scraps in Loch and Google Earth]]) 
  
 ====What are the limits for map and for atlas PDFs?==== ====What are the limits for map and for atlas PDFs?====
Line 776: Line 838:
 Options                 Options                
   * on   - sorts by length and shows the length with each persons name (same as 5.3.10)   * on   - sorts by length and shows the length with each persons name (same as 5.3.10)
 +  * hide - sorts by length but does not show the lengths (new syntax in 5.3.11-was 'off' in 5.3.10).  If some people have equal lengths, then they sort alphabetically
   * off  - sorts alphabetically (behaviour changed from 5.3.10 to implement new feature)   * off  - sorts alphabetically (behaviour changed from 5.3.10 to implement new feature)
-  * hide - sorts by length but does not show the lengths (new syntax in 5.3.11-was 'off' in 5.3.10) 
- 
 ====How do I add peoples names if they have more than two words / names?==== ====How do I add peoples names if they have more than two words / names?====
 The Therion Book says... The Therion Book says...
  • faq.1521789223.txt.gz
  • Last modified: 7 years ago
  • by brucemutton