It would be great if detectors just didnt see the ground at all ... just turn them on and detect away.
Here is a thought experiment.
One way of looking at this mathematically : a detector is working by "solving" a set of simulateous equations.
for example
f(T) = yes or no : funtion of ( Target ) = 1 for target present OR 0 for no target present
f(GR, GB) = 0 : function of ( Ground Response GR ) = 0 (if target = 1 OR 0) and GB = b where b is the Ground Balance variable control setting and GR is the actual "ground target" ie ground intensity ( sand, clay, ferric oxides etc )
Now the usual way a detector solves the f(GB) aka "ground balance" is by bringing the detector coil near a ground with no target ( f(T) = 0 ) and adjusting manually or automatically the GB setting till f(GR, GB) = 0 ie ground balanced.
BUT and it turns out its actually a big BUT.
Once the detector is balanced and GB is set to some value and there is no ground and no target near the coil ( ie holding detector off ground in mid air ) the equation for f(GR, GB) = 0 is still being solved by the detector even though GR = 0 ( no ground present ).
A mathematician looks at this and says to himself "hang on -- you mean the equation still solves if one of the supposed key dependant variables is zero ??? and not only that but when the detector is near a real ground and f(GR, GB) = 0 the equation is solved for a whole range of grounds ( ie the detector is moving across variable ground ).
So this means in short you dont need that variable ( ie the GR value ) because when balanced f(GR, GB) = 0 for a whole range of grounds including no ground at all ( ie the detector is balanced )
In summary where this is leading is that you can ground balance a detector without the ground ! It was just a matter of realising the above.
Yup you could say that using lookup tables or "canned" data could be used "preset" the detector so that you an "predict" the GB setting .... that is not the optimal solution.
I can say that I can prove the GB point can be solved algorithmically without going anywhere near a ground.
so the new formula is now f(GB) = 0 where a method is used that solves only for GR = 0 ( ie no ground near the coil ) and that GB ( the GB setting ) is thus solved for all GR ( all grounds) within practical limits.
You just turn on your detector and it just is ground balanced alerady. No pumping LOL.
There is a f(GB) function running to solve the GB setting all the time ... it just does not need to be "calibrated" against a ground.
So thats the maths ! The methods ( two proposed ) well they might be patents .... I will be testing it out for real.
If I am wasting my time or "it was already done" then let me know.
How did I find this .... I actually dreamed it .. believe it nor not. I was working on a coding bug for the auto ground balance on the FPGA detector and I saw the solution in a dream and I am writing this at 5.20 AM. The bug was not a bug! Its working on the hardware. Time will tell.
Here is a thought experiment.
One way of looking at this mathematically : a detector is working by "solving" a set of simulateous equations.
for example
f(T) = yes or no : funtion of ( Target ) = 1 for target present OR 0 for no target present
f(GR, GB) = 0 : function of ( Ground Response GR ) = 0 (if target = 1 OR 0) and GB = b where b is the Ground Balance variable control setting and GR is the actual "ground target" ie ground intensity ( sand, clay, ferric oxides etc )
Now the usual way a detector solves the f(GB) aka "ground balance" is by bringing the detector coil near a ground with no target ( f(T) = 0 ) and adjusting manually or automatically the GB setting till f(GR, GB) = 0 ie ground balanced.
BUT and it turns out its actually a big BUT.

Once the detector is balanced and GB is set to some value and there is no ground and no target near the coil ( ie holding detector off ground in mid air ) the equation for f(GR, GB) = 0 is still being solved by the detector even though GR = 0 ( no ground present ).
A mathematician looks at this and says to himself "hang on -- you mean the equation still solves if one of the supposed key dependant variables is zero ??? and not only that but when the detector is near a real ground and f(GR, GB) = 0 the equation is solved for a whole range of grounds ( ie the detector is moving across variable ground ).
So this means in short you dont need that variable ( ie the GR value ) because when balanced f(GR, GB) = 0 for a whole range of grounds including no ground at all ( ie the detector is balanced )
In summary where this is leading is that you can ground balance a detector without the ground ! It was just a matter of realising the above.
Yup you could say that using lookup tables or "canned" data could be used "preset" the detector so that you an "predict" the GB setting .... that is not the optimal solution.
I can say that I can prove the GB point can be solved algorithmically without going anywhere near a ground.
so the new formula is now f(GB) = 0 where a method is used that solves only for GR = 0 ( ie no ground near the coil ) and that GB ( the GB setting ) is thus solved for all GR ( all grounds) within practical limits.
You just turn on your detector and it just is ground balanced alerady. No pumping LOL.
There is a f(GB) function running to solve the GB setting all the time ... it just does not need to be "calibrated" against a ground.
So thats the maths ! The methods ( two proposed ) well they might be patents .... I will be testing it out for real.
If I am wasting my time or "it was already done" then let me know.
How did I find this .... I actually dreamed it .. believe it nor not. I was working on a coding bug for the auto ground balance on the FPGA detector and I saw the solution in a dream and I am writing this at 5.20 AM. The bug was not a bug! Its working on the hardware. Time will tell.
Comment