Custom Query (95 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (88 - 90 of 95)

Ticket Resolution Summary Owner Reporter
#48 fixed cavern: Errors do not say 'ERROR' Olly Betts Wookey
Description

On cavern runs the warnings say 'WARNING' but the errors (which prevent a 3d file being output) do not say 'ERROR', so it can be very hard to find the actual offending issue in the output, especially when there is a lot of it.

This is noticeable in a project with backbearings for example, where a lot of 'mismatched backbearing' warnings can obscure the important ERROR lines.

Can we please just mark errors explicitly with something greppable? (probably 'ERROR:')

This could be described as an enhancement or a bug, but I'm going to file it as a bug as it seems wrong, given the WARNING output.

#77 fixed missing "error: " or "warning: " in front of "CLINO and BACKCLINO readings must be of the same type" Olly Betts Andy Edwards
Description

I recently started contributing to Cavewhere, which uses Survex as a backend. When I tried importing Fisher Ridge data into it, Cavern crashed saying "too many errors -- giving up".

I couldn't find "error" anywhere in its output, but I did see the following message in several places. Is this a warning or an error?

0kz1lsqn0fg37x3tt94dvdsm0000gn/T/Cavewhere.L39692:11033: CLINO and BACKCLINO readings must be of the same type

I think Cavewhere relies on finding "warning" or "error" in Cavern output to mark warnings and errors in its UI.

#2 fixed netbits.c:1074: covariance matrix is singular Olly Betts susscorfa
Description

When i run the all.svx file i get this error

"netbits.c:1074: covariance matrix is singular"

I have no clue where the problem is

Note: See TracQuery for help on using queries.