Known Issues

Licensing error on FIPS-enforced networks

  • Issue: A licensed BTField will not start up on FIPS-enforced networks. The FIPS policy causes a failure in the licensing file encryption.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: low

Dig List Stage 1 lock producing extra secondary digs

  • Issue: A user’s Stage 1 lock point is sometimes not persisted to the database causing extra secondary digs to be flagged. This is an infrequent, intermittent occurrence, and its effect is conservative: extra digs are flagged rather than any being omitted.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: medium

Dig List models straddling a Stage lock point

  • Issue: For a target whose models span a Stage lock point (some above and some below the lock), the models below the lock could be handled inconsistently, producing incorrect or extra secondary digs and stop-dig / closure discrepancies in multi-stage dig lists. This is an edge case that arises only in multi-stage dig lists, and only for the few targets whose models happen to straddle a stage lock point.
  • Mitigation: Setting a conservative lock point (so that borderline models fall on the dig side rather than straddling the lock) avoids any serious problem.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: medium

Cumulative Distance and Velocity can stop being calculated during data collection

  • Issue: During data collection, out-of-spec UTM and NaN values can cause the Cumulative Distance and Velocity calculations to stop being performed. This is triggered only by out-of-spec UTM or NaN GPS values (for example during a brief GPS dropout) and affects the on-screen distance/velocity display, not the recorded position data.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: medium

Midnight time crossing during data collection

  • Issue: During data collection, the data stream timestamping will reset to zero seconds after a midnight crossing. This occurs only when a single data collection session runs across the midnight (00:00) boundary, which is uncommon in practice.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: medium

Library Match not handling NaN

  • Issue: The library match calculation can generate an NaN value when fed extremely small polarizability values. This error condition is not handled properly by setting the match value to zero. The NaN value can prevent Dig List flows from running. This is a rare edge case, triggered only by extremely small polarizability values, and it stops the flow visibly rather than producing a silently incorrect result.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: medium

Within Boundary Processing

  • Issue: Polygon boundary determination can be off by one pixel, which can cause targets located directly on top of the boundary to be incorrectly excluded from the selection. This is a rare edge case affecting only targets that fall exactly on the boundary pixel; targets clearly inside or outside the boundary are unaffected.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: low

Function Test with no data

  • Issue: Unreferenced-object error when running Calc on Function Tests that contain no data.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: low

HDF5 export fails when Lat/Lon missing

  • Issue: HDF5 export failing on 2Fb (SLAM) surveys that contain no Lat/Lon data.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: low

IMLI position error

  • Issue: When inverting with the IMLI option, the final predicted source position can sometimes be inaccurate when a contributing VLine has only a few observations in the cell. This is an edge case limited to cells where a contributing vehicle line has very few observations, and does not occur with normal data coverage.
  • Versions affected: 15.3.29 and lower
  • Sensor platforms affected: all
  • Severity: medium

Lost data reference on indicator

  • Issue: Under certain conditions an data view indicator can lose its reference to the data after running a processing flow.
  • Versions affected: 15.3.25 and lower
  • Sensor platforms affected: all
  • Severity: low

Metrics Navigator not populating

  • Issue: The Metrics Navigator View does not populate with models on the first load of a survey.
  • Versions affected: 15.3.25 and lower
  • Sensor platforms affected: all
  • Severity: low

Client machine cannot access Project Settings

  • Issue: When BTField is networked, a client machine cannot access the Project Settings to switch its AQ Cfg.
  • Versions affected: 15.3.25 and lower
  • Sensor platforms affected: all
  • Severity: low

Auto-Pick not ignoring SRA polygons

  • Issue: The Targ Detect function will pick targets inside SRA polygon types.
  • Versions affected: 15.3.25 and lower
  • Sensor platforms affected: all
  • Severity: low

Tx-Rx pairs setting not retained

  • Issue: The Tx-Rx pairs setting in the Targ Detect function is not retained after saving the PROCESSING interface
  • Versions affected: 15.3.25 and lower
  • Sensor platforms affected: all
  • Severity: medium

Extra Merge function in Flow

  • Issue: When restoring the AQ interface, an extra Raw-to-Merged step gets added to the P Flow1.
  • Versions affected: 15.3.25 and lower
  • Sensor platforms affected: all
  • Severity: medium

Stretched plots on Function Test Report

  • Issue: The Function Test report has stretched plots and fonts.
  • Versions affected: 15.3.19 and lower
  • Sensor platforms affected: all
  • Severity: low

Installer not updating CompilerServices.UnSafe.dll

  • Issue: When upgrading to v15.3.19 some machines may get a message saying BTField cannot find the CompilerServices.UnSafe.dll. The workaround is to:
    1. Uninstall the BTField application in Windows Start/Installed apps. Do NOT uninstall SQL Server. Also, do NOT delete the c:\BTG Workspace folder.
    2. Run the v15.3.19 msi installer again.
  • Versions affected: 15.3.19 only
  • Sensor platforms affected: all
  • Severity: low

Elevation Offset in Merged H5 V1 Exports

  • Versions affected: 15.3.19 and lower
  • Sensor platforms affected: all
  • Severity: Small elevation offset in exported sensor positions; effect is negligible under low-roll survey conditions and increases with terrain-induced roll.

Description

When BTField exports merged H5 V1 data in v15.3.19 or lower, the Elevation field is written at the position of the first receiver (Rx #0) rather than at the GPS antenna. This introduces a lever arm offset that includes a lateral (cross-track) component. Because the offset is attitude-dependent, it produces spurious sensor height variation that cannot be removed by a simple constant correction.

When BTField re-imports this data, the import assumes Elevation is at the GPS antenna location and applies the lever arm correction a second time. This results in a double lever arm correction on the elevation values.

UTM coordinates (Easting, Northing) are not affected: they are computed directly from GPS Lat/Lon without a lever arm offset.

Affected Datasets

This issue affects any dataset exported as merged H5 V1 from a multi-receiver array where the first receiver is not co-located with the GPS antenna.

Any hdf5 dataset that has already been exported and re-imported into BTField v15.3.19 or lower contains incorrect elevation values that cannot be corrected in place. Users should re-import affected merged H5 V1 data using BTField v15.3.24 or higher as it will apply the correction during import.

Additional Note

The merged H5 V1 export of v15.3.19 or lower also writes a hardcoded Geoid Separation value (−33.9 m) that may not match the actual survey location. This does not affect sensor Elevation but will produce an incorrect Height Above Ellipsoid (HAE) value in the file.

Recently Fixed

Issues resolved in recent releases. See the Release Notes for details.

Metric Navigator not populating on first survey load

  • Issue: The Metric Navigator could fail to populate on the first load of a survey, and could raise a null-reference error when the Metric Navigator view was not present.
  • Sensor platforms affected: all
  • Fixed in: 15.4.2

IMLI inversions incorrect under certain conditions

  • Issue: In the inversion configuration, if the IMLI option and the “all lines” option were both checked, the IMLI inversions were incorrect when the inverted cell contained 4 or more lines.
  • Sensor platforms affected: all
  • Fixed in: 15.3.32

Secondary Digs not getting selected

  • Issue: Under certain conditions, secondary digs could fail to be selected due to an unused database row lock that intermittently blocked secondary dig selection.
  • Sensor platforms affected: all
  • Fixed in: 15.3.49 and 15.3.51 (dig-list Stage 1 lock loss and stage-progression / stop-dig persistence)

hdf5 import not updating survey extents

  • Issue: The hdf5 import did not update the survey extents, which prevented hdf5-imported surveys from being included in an SU survey.
  • Sensor platforms affected: all
  • Fixed in: 15.3.29
Tags: