Closed jedwards1211 closed 8 years ago
Hmmm, nevermind, I assume Survex expects the backsights after calibration to be in the opposite direction? Looking at the code, your *calibrate
output was obviously intentional, and surely I would have seen problems with other caves. I think the problem with FRCS data is that there are shots where clino and backclino are both "Down". I'll open a separate issue for that
Survex is a bit backwards when it come to calibrations.
On Friday, January 1, 2016, Andy Edwards notifications@github.com wrote:
Closed #100 https://github.com/Cavewhere/cavewhere/issues/100.
— Reply to this email directly or view it on GitHub https://github.com/Cavewhere/cavewhere/issues/100#event-503872540.
Phi|ip
Sent from Gmail Mobile
I think it's a Survex bug. It's complaining about shots like this, under the above calibration:
HC15 HC16 1.3 - - DOWN DOWN
Cavern is saying:
0kz1lsqn0fg37x3tt94dvdsm0000gn/T/Cavewhere.L39692:11033: CLINO and BACKCLINO readings must be of the same type\n/var/folders/sp/
I'll file a bug on Survex's tracker...
Cool
On Friday, January 1, 2016, Andy Edwards notifications@github.com wrote:
See http://trac.survex.com/ticket/78#ticket
— Reply to this email directly or view it on GitHub https://github.com/Cavewhere/cavewhere/issues/100#issuecomment-168351596 .
Phi|ip
Sent from Gmail Mobile
We might have to omit one of the down in the export.
On Friday, January 1, 2016, Philip Schuchardt vpicaver@gmail.com wrote:
Cool
On Friday, January 1, 2016, Andy Edwards <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:
See http://trac.survex.com/ticket/78#ticket
— Reply to this email directly or view it on GitHub https://github.com/Cavewhere/cavewhere/issues/100#issuecomment-168351596 .
Phi|ip
Sent from Gmail Mobile
Phi|ip
Sent from Gmail Mobile
In a trip with corrected compass and clino, the temp survex file generated by Cavewhere has:
This is what should be used when the backsights are uncorrected, right? I assume it should have output
For some reason I've only seen this with imported Fisher Ridge data.
If you want, I can send a screenshot showing the mismatch, don't want to attach it here for the sake of FRCS data privacy