Custom Query (95 matches)
Results (7 - 9 of 95)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#77 | fixed | missing "error: " or "warning: " in front of "CLINO and BACKCLINO readings must be of the same type" | ||
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. |
|||
#48 | fixed | cavern: Errors do not say 'ERROR' | ||
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. |
|||
#10 | fixed | cad3d and export from Aven should produce identical .dxf files | ||
Description |
There are two ways to produce .dxf files from a .3d file, producing different results: cad3d produces a .dxf file which preserves the absolute co-ordinates used in the .3d file export from Aven produces a .dxf file in which the origin of the co-ordinate system has been moved (probably to the centre of the network, haven't checked...) Both are valid .dxf files, but the difference seems arbitrary and confusing. Perhaps both methods should give a choice of outputs. |