True Database Storage and Display for SMT200, SMT300 and SMT400 Results
As with the old version, with SMTAN2, you can
  • Save SMT200 Files to an SQLite database
  • Retrieve the results you want - by day, week, month etc.
  • Display Histograms, scatter plots, cross plots and more
  • Easily configure the program
  • Access a Maintenance module
  • Perform Single String Queries
  • Display Time Analysis
  • Show Database Statistics
  • Display Pending Retests (new to SMTAN2)
Contracts often state that a database of Geophone test results must be kept.
Most crews simply create a large Excel spreadsheet, which sort of meets the minimum requirements, but a proper database has distinct advantages :
  • You can query it
  • It is a standard format that can be archived
  • It is harder to tamper with
SMTAN2 provides all this and more.

SMTAN2 is a complete rewrite of the earlier SMT Analyser. It uses a newer Database technology and builds on learnings from the earlier version.

The old Databases are NOT compatible - you will need to reload your data if you wish to use this version

This version handles SMT200, 300 and 400 datasets. It assumes dates are in a sensible format - if you insist on using the mindless American format, you get what you deserve - SFA!.

Scatter Plots
Cross Plots
Maintenance Module
Easily Add Records
Easy Configuration
Single String Queries and Time Analysis

It is a good idea to look at Tester performance over a period of time. The easiest way to do this is to set aside a reference string which is tested each day by each tester before routine testing begins. After a month or so, the results from this string can be examined to see if the tester is behaving, and if there are any radical differences in testers.

The Single string display function found under 'Utilities' makes this quite easy:
You can select the period to query, and the string number (two reference strings may be specified). Each tester is displayed in a different colour. An analysis of the SMTs in use can be performed to detect issues:
For reports, it is often useful to display the number of tests per day. This and more is available from  'Time Analysis' under Utilities:

As with the Single String Display, you can specify the period to query, and the type of result.
Output of Graphics is now only PNG

Easy Project Creation and  Selection
Pending Retests is a new function with SMTAN2. It allows you to track strings that have failed and not shown up as retested after repair.
You can remove strings that are obviously a lost cause.

** with release 257, Pending updates are much much faster, but for this to happen, you need to recreate your database and reload the data.

** with release 257, you can sort by clicking on a column header
  • Update 31-Oct-2012    - Improved Statistics
  • Update March 2013    - Support for Sercel's SGT-II
  •                                          - Sort options in Pending Retest
  •                                          - Selection Buttons in Pending Retest
  •                                          - Improved handling of bad dates
  • Update August 2013  - Unseen Strings. You MUST check your
  •                                           configuration after upgrading. Some
  •                                           settings will be messed up!
A common issue is some moron resetting the system resulting in dates reverting back to 1 Jan 2000 or some such.
With release 257, comes better handling of bad dates. Dates with a year less than specified are corrected based on the specified rule.
With release 257, SGT-II is supported
Release 311 adds the  'Unseen Strings' Function

You can count and list strings that have not been seen for a specified period.
Very useful to check on the effectiveness of rotational testing - the number of
tests reported by the contractor often bears no relationship to the number of
strings tested - many are repeats.

When upgrading from a previous version, you MUST check your configuration. Some entries will be messed up. If you don't set them correctly, you will get strange looking results. The databases are not affected.