- Therion - speleo.sk

Grid and Label clipping
by Andrew Atkinson 16 Nov '11

16 Nov '11

Hello From reading the therion book, if I have the grid bottom should it not be clipped by labels so the attached should not happen. The text should be on top of the grid. and therefore the grid not be seen at this point. Label appear to clip the passage. thanks Andrew

3 6

Cross section line error
by Andrew Atkinson 12 Nov '11

12 Nov '11

On returning from today's trip and duly settling down to draw up the survey I go the error below. Well it did not give me many clues, but eventually found the problem. I had drawn a cross section line, and then clicked closed, somehow, which gave a double line. (Having 3 points and closed does not seem to cause the error) Anyway, I was hoping that if I sent this maybe it would be possible to say in the error message what caused the error, even if it was only a line number from the th2 file, or the type of line, possibly it does and I jsut do not know how to read it. Luckily this is a small file so it was easy to delete things until it worked. Attached is the file with the error within it. It is the section line for section PalmersSX1.2, #################### end of cavern log file #################### done calculating basic statistics ... done processing extended elevation ... done processing references ... done selecting export objects ... done processing projection plan ... done average distortion: 0.09% writing Palmers.pdf ... processing projection none ... done ####################### metapost log file ######################## This is MetaPost, version 1.208 (kpathsea version 5.0.0) (mem=mpost 2011.10.19) 12 NOV 2011 18:46 **data.mp (./data.mp [4001] [4002] [4003] [4004] [4005] [4006] [4007] [4008] [4009] [4010 ] [4011] [4012] [1] [2] ! angle(0,0) is taken as zero. <for(0)> ...rotated.angle(thdir(Q,(EXPR0)))shifted (point(EXPR0)of.Q);pickup.... l_section->...(0.1u,0.55u);fi;exitif.pnt=-1;endfor ; l.5349 ),0,2) ; The `angle' between two identical points is undefined. I'm zeroing this one. Proceed, with fingers crossed. ! angle(0,0) is taken as zero. <for(2)> ...rotated.angle(thdir(Q,(EXPR0)))shifted (point(EXPR0)of.Q);pickup.... l_section->...(0.1u,0.55u);fi;exitif.pnt=-1;endfor ; l.5349 ),0,2) ; The `angle' between two identical points is undefined. I'm zeroing this one. Proceed, with fingers crossed. [3] [4] [5] [6] [7] [8] [9] [10] [11] (./mptextmp.mp) (./mptextmp.mp) (./mptextmp.mp) (./mptextmp.mp) (./mptextmp.mp) (./mptextmp.mp) [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] ) Here is how much of MetaPost's memory you used: 1019 strings out of 1162 12416 string characters out of 15838 60569 words of memory out of 3000000 1320 symbolic tokens out of 16384 9i,75n,12p,199b,4f stack positions out of 300i,84n,10000p,200b,15f 51 string compactions (moved 448697 characters, 36984 strings) 33 output files written: data.1 .. data.4012 #################### end of metapost log file #################### therion: error -- metapost exit code -- 512 writing xtherion file ... done therion: warning -- error deleting temporary directory -- /tmp/th4359

1 0

Loch 5.3.8 not displaying models on Debian wheezy
by Andrew Atkinson 12 Nov '11

12 Nov '11

Hello all I started on this problem before the summer, but then I went away for a few weeks. But I am working on surveys again so I could really do with loch. (One plus from before the summer is that aven is upgraded to 1.2.2 and that now works again, so I am not completely blind) So trying to open a lox or 3d file in loch just gives a blank screen (grey to go with the border) Runing it from terminal does the same with no errors. Below is the useful information that aven gives you when you look at help Andrew Linux 3.0.0-1-amd64 x86_64 wxWidgets 2.8.10 (GTK+ >= 2.6) Display Depth: 24 bpp (colour) OpenGL 2.1.2 NVIDIA 275.28 NVIDIA Corporation GeForce 7300 GS/PCI/SSE2 GLX 1.4 R8G8B8 Max Texture size: 4096x4096 Max Viewport size: 4096x4096 Smooth Point Size 1.000-63.375 (granularity 0.125) Aliased point size 1.000-63.000 Double buffered: true GL_ARB_color_buffer_float GL_ARB_copy_buffer GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_robustness GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_shading_language_include GL_ARB_shadow GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_gpu_program_parameters GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_sRGB GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_x11_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KTX_buffer_region GL_NV_alpha_test GL_NV_blend_minmax GL_NV_blend_square GL_NV_complex_primitives GL_NV_copy_depth_to_color GL_NV_depth_clamp GL_NV_fbo_color_attachments GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragdepth GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_lod_clamp GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_OES_depth24 GL_OES_depth32 GL_OES_depth_texture GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object GL_OES_vertex_half_float GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum

4 13

Text statement bug
by Bruce 10 Nov '11

10 Nov '11

I've just discovered the text statement for tweaking the standard texts that appear in therion outputs. A small play with three examples led me to find that two worked as expected and the last one does not work. text en "line u:rope" "rope" #text to appear in legend text en "title topo (plural)" "Explored & Surveyed by" text en "line border" "ground, tree" If I try small variations of "line border" I get and error (as expected), but with the example as above there is no error, but the legend text remains as 'border'. A bug, or something I don't understand? Bruce

2 2

Extra ... in map-comment result
by Bruce 10 Nov '11

10 Nov '11

Not sure I've noticed this problem before, and I have done this sort of thing regularly in the past. Using 5.3.8 why is it that in a layout, this entry. map-comment "Developed Elevation Projection\ TBA featured prominently on the 2011 NSG trip list, meaning \ 'to be advised' - month after month it appeared trips were \ going to 'TBA '. So when this cave was discovered, it was so \ named to retrospectively make the trip list look good." produces text like the below in my output map? Developed Elevation Projection TBA featured prominently on the 2011 NSG trip list, meaning ... 'to be advised' - month after month it appeared trips were ... going to 'TBA '. So when this cave was discovered, it was so ... named to retrospectively make the trip list look good. The odd things are the . at the end of the middle three lines. What makes it especially odd is that there is no . after the first line. How can I prevent the . from being produced? Bruce

2 2

Is it possible to not use the equate command when all stations are unique
by Torstein Finnesand 10 Nov '11

10 Nov '11

Hi, "Equate" is used to set the survey stations equivalence, i.e: equate 2@first 1@second. The cave I survey has only unique station names (about 3000). But still I have to use the equate command for a station that is located in 2 surveys. If not, the loops will not be closed. So I do like this: equate TA40@first TA40@second. I have to use this command many times, since the cave has a lot of surveys. Question: Is it possible to not use the equate command, since all stations are unique? For instance by another command that tells Therion/survex that the station names are unique even if there are two or more surveys or by arranging data in another way. Torstein Finnesand Norway

3 4

Standard deviation of estimated station coordinates from least-squares loop correction?
by Xavier Pennec 06 Nov '11

06 Nov '11

I have a large graph of archaeological sites (medieval mines) connected by multiple surface surveys. The ensemble counts more than 120 sites ("entrances") with 28km of survey including about 5000 stations connected by 500 legs with 187 loops and 297 connected components. Of course the surveys were done by different teams with different accuracies and the fixed points are GPS points with very different accuracy (from more than 30m to 1m for the professional GPS points by a geometer). I have heavily used the sd command to correctly weight the different measures in the least-squares loop correction estimation, which means that internally the system should have a pretty good idea of the accuracy of each station location. What I would like is to extract the standard deviation of the entrance locations when I export the coordinates in the cave-list export. Does anybody has an idea of how to extract this standard deviation information? Xavier -- > ------------------------- > Xavier Pennec > Senior Research Scientist / Directeur de recherche > Asclepios project-team, INRIA Sophia-Antipolis > 2004 Route des Lucioles, BP93 > F-06902 Sophia-Antipolis Cedex, France > +33 4 92 38 76 64 > +33 6 78 35 16 90 > http://www-sop.inria.fr/asclepios/ > -------------------------------

1 0

therion up side down
by Martin Sluka 05 Nov '11

05 Nov '11

Bruce, you forgot one more: simple: way the water area on right side is inverted. My mistakes, of course. m. _______________________________________ Therion mailing list Therion(a)speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion

2 1

therion up side down
by Bruce 05 Nov '11

05 Nov '11

The funny ones I have not kept, so two easy ones. 1. The red line - why is it red? 2. The purple-brown question mark at bottom left. What does it signify and in what data structure (clue first five sections of 'data format' in Therion Book) is it probably defined in? Bruce

1 0

therion up side down
by Martin Sluka 04 Nov '11

04 Nov '11

just a bit fun with therion ;o) My mistakes, of course. m.

2 5