I am trying to use the Kraken in a exercise that will be done on foot in a small campus. I tried to reduce the grid size to 0.1km and it appears that there is a hard limit in the Android Kraken app that the grid size must be larger than 1km. I could successfully set it to 1.001km. This seems like an arbitrary limit that could be reduce to something more like >= 0.1km. There are some related setting that also appear to have arbitrary lower limits. They should be reduced as well.
Speed thresholds etc. need to be settable for someone walking, not driving.
Is there any reason why a total grid size below 1km would be useful? Even if you’re only searching a space of 100m, the total grid size doesn’t really matter.
Reducing the total grid size does increase the cell resolution, but at the default setting of 100 cells per axis, you’re getting a cell size of 10m. And at that scale the limiting factor isn’t really the cell size but rather the accuracy of the direction finding system.
When working on foot and searching for potenitally hidden transmitters, getting cell size down below 100 sq meters can be very helpful. My experience with this human portable version suggests that accuracy is not materially different even at a distance of 10 meters, and if you consider the mathmatics/physics, once you get out of the near-field (10-20 meters, but dependent on wavelength), it should be as accurate as it is at 2km. or more.
So, I am requesting a smaller grid size so when my area of interest is quite small, I can have better cell resolution without increasing the cells per axis, which can have a dramatic impact on compute requirements. Is this hard?
So, maybe the setting isn’t grid size, but grid resolution? Also, the target location (hexagon that goes from red to green), can we be able to make that smaller as well? the “man portable” version of the kraken worked really well, but the map was unusable and relied on the DOA compass for DF’ing.
P.S. we probably convinced about 12 different agencies to purchase 2 or more krakensdr’s
That’s an excellent point about the hexagon size relative to the map for smaller search areas. That would definitely be desirable to shrink in these scenarios.
So Carl, have we been able to convince you of the utility of a smaller grid?
If this was in the Kraken code in the Pi, I would do the change myself, but we don’t have access to the Android app source.
