...
| Code Block |
|---|
| title | geolocate.m |
|---|
| borderStyle | solid |
|---|
|
if constraintType
warning('Trying speed of light')
constraintType = 0;
% switch the constraint type and try again
[locest,actual,error,regarea,distNearestLandmark,target_id,constraintType,inRegion\] = geolocate(file,extension,hullbool, constraintType, bestlineTable);
return;
else
% find the badPairs that lead to no region, write them to stdout
badPairs = analyzeNoRegion( measurements )
%error(\['No SOL intersection region for ', char(file)\])
region = \[NaN NaN\];
locest = \[NaN NaN\];
error = NaN;
regarea = NaN;
results = \[target_id error; distNearestLandmark regarea; locest; actual; region\];
dlmwrite(\[char(file),char(extension)\],results,' ');
return;
end;
|
A sample of "bad pairs" from target file of "132.248.120.214" is below. Each line contains four values separated by white-space and are in order: Apart from this another reason for NaNs is unavailability of sufficient non-duplicate landmark estimates. This is also a reason why NaNs occur for 11 targets lat long rtt id
| Code Block |
|---|
| title | Target-132.248.120.214.txt |
|---|
| borderStyle | solid |
|---|
|
42.3424 -71.0878 0.5 167
47.1544 -88.6471 0.5 119
42.6442 -73.2463 0.5 165
40.4249 -86.9162 0.5 150
28.0631 -82.4128 0.5 142
38.0287 -84.5075 0.5 145
40.7855 -111.737 0.5 166
|
2. Some results have enormous errors (|error|>1000)
...