Jump Grid Survey baseline bug?
Posted: Thu Aug 09, 2012 7:50 pm
Just finished doing a jump grid survey and ran into an issue related to the baseline.
We surveyed ABCD and 30m check balls and entered the values. Our grid uses balls at 10m and 30m along the 15st 15et line and balls about the same distance the other side of the jump centerline parallel to 15st 15et.
Looking at the output it was failing the sanity check. the 10m ball along the 15st 15et line should show as x 10m and y 15m and they were way out of whack.
Finally dawned on us that we forgot to enter our 15st 15mt 15et values into the grid survey.
Did that, still the same issue... Even just looking at B alone something was out of whack.
Of course the issue turned out to be we had failed to set what the baseline we wer using (labelled X Axe I believe, should that be X Axis?) in the dropdown. We needed to set that to us the 15st 15et points.
The whole point of this message is that a lot of lost time would have been avoided if there was some way in the program to NOT display output values when there is something completely wrong in the input area. In our case we had values for 15st 15mt and 15et but were using one of the other baseline settings and there were NO values entered for those (I think Cam1 CAM2 CAM3 was selected by default), so how could it possible calculate values from no input.
Either forgetting to enter the measured values for the selected baseline or entering values and having the incorrect baseline selected results in erroneous output values where the reality is that no output should be possible.
We surveyed ABCD and 30m check balls and entered the values. Our grid uses balls at 10m and 30m along the 15st 15et line and balls about the same distance the other side of the jump centerline parallel to 15st 15et.
Looking at the output it was failing the sanity check. the 10m ball along the 15st 15et line should show as x 10m and y 15m and they were way out of whack.
Finally dawned on us that we forgot to enter our 15st 15mt 15et values into the grid survey.
Did that, still the same issue... Even just looking at B alone something was out of whack.
Of course the issue turned out to be we had failed to set what the baseline we wer using (labelled X Axe I believe, should that be X Axis?) in the dropdown. We needed to set that to us the 15st 15et points.
The whole point of this message is that a lot of lost time would have been avoided if there was some way in the program to NOT display output values when there is something completely wrong in the input area. In our case we had values for 15st 15mt and 15et but were using one of the other baseline settings and there were NO values entered for those (I think Cam1 CAM2 CAM3 was selected by default), so how could it possible calculate values from no input.
Either forgetting to enter the measured values for the selected baseline or entering values and having the incorrect baseline selected results in erroneous output values where the reality is that no output should be possible.