GrainSpotter provides information on indexing statistics in its log file. Things can become tricky, however, if you ran series of GrainSpotter indexings as described in the Advanced GrainSpotter indexing section.

If you merged the results of your indexings in a single log file, the number of experimental g-vectors assigned to your grains is the number of g-vectors listed in the log file.

The number of g-vectors that could have been assigned depends on

• the number of g-vectors measured in the experiment,
• the η, ω, and 2θ ranges defined in the GrainSpotter init file,
• the 2θ, η, and ω tolerances as well as nσ in the GrainSpotter init file.

GrainSpotter does write this number out to the screen, but it depends on the init file. As your indexing loop start, you have strict tolerances and ranges, hence, this number is lower than with looser tolerances. Later, once you use looser tolerances in GrainSpotter, assigned g-vectors should be removed from the original list. It is hence difficult to evaluate indexing performances.

The script timelessGSIndexingStatistics, part of the TIMEleSS tools is meant to help. You have to provide

• The original g-vectors file,
• The GrainSpotter init file with the loosest tolerances (typically, the last you used),
• The merged grain file (obtained with timelessGrainSpotterMerge, for instance,
• The wavelength.

It will read the g-vectors file, remove g-vectors

• that do not fall within the defined η, ω, and 2θ ranges,
• that can not be from your sample, based on the list of theoretical g-vectors in the gve file as the 2θ tolerance and nσ in the GrainSpotter init file,

and calculate indexing statistics.

An example of output is shown below