Using the NIST26 Tandem Demo with Spectra Imported from Vendor Software
- Photo: Mass Spec Interpretation Services/James Little: Using the NIST26 Tandem Demo with Spectra Imported from Vendor Software
- Video: Mass Spec Interpretation Services/James Little: Using the NIST26 Tandem Demo with Spectra Imported from Vendor Software
The NIST26 Tandem Demo provides a way to explore library searching and chromatogram-based analysis of tandem mass spectra using NIST MS Search 4.0. Its built-in workflow is the simplest starting point, but laboratories may also want to send accurate-mass LC-MS/MS spectra directly from their instrument software to NIST. A practical demonstration by James Little and O. David Sparkman shows how this can be achieved with Agilent MassHunter, which configuration files are involved, and what users should check to avoid problems during spectrum import.
Start with the integrated NIST26 workflow
The 2026 release of the NIST Mass Spectral Library introduces NIST MS Search 4.0, which supports the analysis of tandem mass spectra and chromatographic data. The software offers chromatogram review, examination of MS1 and MS/MS information, spectral library searches, and Hybrid Search capabilities.
For most users evaluating the NIST26 Tandem Demo, the recommended approach is to begin with the software as installed. Its integrated workflow provides an introduction to the search tools without requiring changes to vendor-specific interfaces, Windows configuration files, or executable names.
This distinction is important because the demonstration program and a fully configured commercial NIST26 installation are not identical in their vendor-interface arrangements. Although the demo contains functioning NIST search software, additional setup may be necessary when a separate data system attempts to launch it and send spectra for searching.
Why import spectra from instrument software?
Many analytical laboratories process LC-MS/MS data in software supplied with their mass spectrometers. Users may prefer to inspect chromatograms, select precursor and product-ion spectra, and perform initial data processing within that familiar environment.
A vendor-to-NIST connection makes it possible to transfer a selected spectrum to NIST MS Search for comparison with compatible reference libraries. This allows analysts to combine the data-handling features of their instrument software with NIST's spectral identification tools.
The presentation demonstrates this approach using Agilent MassHunter and accurate-mass LC-MS/MS spectra. The underlying principles may apply to other software packages that support NIST library searching, but individual interfaces can differ. A configuration that works with one vendor application should therefore not be assumed to work unchanged with another.
The authors also emphasize that vendor import and NIST's integrated chromatogram-processing functions are complementary approaches. Neither needs to replace the other.
Connecting the demo to Agilent MassHunter
A vendor interface may look for NIST software in a particular location and expect a specific executable filename. Those expectations can differ from the default installation of the NIST26 Tandem Demo.
The illustrated configuration involves several related components:
- Program folder: The demonstration uses a shorter directory name, such as
C:\NISTDT, instead of the default demo installation folder. Changing the folder requires corresponding updates to shortcuts and configuration paths. - Executable name: The vendor interface expects a file called
nistms$.exe, whereas the demo's principal search program is provided under a different filename. - Windows configuration: The
win.inifile contains information used by some vendor interfaces to locate and launch NIST MS Search. - Spectrum transfer: An
autoimp.msdfile provides the link to a temporary file containing the spectrum exported by the vendor software, typically in MSP format. - NIST settings: Library locations and other search preferences are retained by the NIST application, including in its
nistms.inisettings file.
The presentation recommends backing up configuration files before editing them. Because win.ini resides in a protected Windows location, changes may also require appropriate system permissions.
Importantly, autoimp.msd does not normally need to be created or edited manually at the outset. In the demonstrated workflow, the vendor software creates it when a spectrum is sent to NIST for the first time.
An important distinction between NIST executables
One of the more significant technical cautions concerns two similarly named files: nistms.exe and nistms$.exe.
The first is the main NIST MS Search application. The second has historically served as a launcher that can process information passed from other software, including command-line instructions associated with importing a spectrum.
The demonstration describes a workaround in which the principal executable is renamed to the filename expected by the Agilent interface. That approach was reported to work in the specific test configuration, but renaming a program does not reproduce the functionality of the genuine launcher.
Users should treat this as an experimental workaround rather than a universally supported installation procedure. Successful startup alone does not prove that all command-line options, spectrum-transfer operations, and vendor-specific functions are behaving correctly.
For routine workflows, the appropriate vendor-interface files should be used when available, and any alternative configuration should be thoroughly validated.
Adding MS/MS libraries and configuring the search
The NIST26 Tandem Demo includes a small demonstration library containing approximately 830 reference spectra. This is sufficient for learning the interface, but its coverage is limited compared with larger MS/MS reference collections.
The presentation also points to a separate set of publicly available NIST-format MS/MS libraries assembled by the presenter, comprising more than 500,000 spectra and over 150,000 associated chemical structures. These are optional additional resources, not the complete commercial NIST26 library.
NIST MS Search can work with compatible libraries in its supported format, including appropriately prepared user libraries. On first launch, users may be asked to specify the directory containing their libraries; the selected location is then retained in the program settings.
Once the libraries are available, the user can configure the search interface:
- Select the libraries and search parameters appropriate to the experiment.
- Adjust the Library Search and Chromatogram windows.
- Enable head-to-tail comparisons between an experimental spectrum and a library match.
- Display associated chemical structures alongside spectra where supported.
- Save the window configuration for subsequent sessions.
When launched from MassHunter, the Switch to Caller command can return focus to the instrument software.
Accurate-mass settings need particular attention
Accurate-mass tandem spectra carry information that can be lost if import settings are not configured correctly. The presentation therefore highlights the Spectrum Import Options in NIST MS Search.
For accurate-mass LC-MS/MS data, users should select the Accurate m/z option and choose an appropriate number of decimal places for the imported spectral values.
The authors also report an important issue encountered during their demonstration: applying an intensity-threshold filter during spectrum import caused accurate-mass peaks to be displayed with nominal m/z values.
In the example shown, peaks expected to retain several decimal places were instead displayed as integer masses. Such a change would compromise the accurate-mass information needed for meaningful interpretation of fragment ions.
For the demonstrated configuration, the recommendation is to avoid applying an intensity threshold in the import options and verify that the transferred spectrum retains the expected m/z precision. This observation should be treated as a reported issue in the tested software setup, not as proof that every NIST installation or version behaves identically.
Checking the imported peak positions against the original vendor spectrum is therefore an essential validation step.
Comparing vendor processing with NIST chromatogram analysis
The tutorial uses an example forensic sample to illustrate two processing routes.
In one approach, Agilent native-format data are processed in MassHunter and a selected tandem spectrum is transferred to NIST for library searching.
In the other, mzML data can be examined through NIST's own Chromatogram window, allowing users to explore the integrated analysis workflow without relying on the same vendor-import procedure.
This comparison helps clarify the role of each software environment. Vendor import is useful when analysts want to continue selecting and reviewing spectra within an established instrument-data workflow. Integrated NIST processing provides additional opportunities to inspect chromatographic and mass-spectral information within the search software itself.
A practical way to evaluate NIST26
The key recommendation is to evaluate the NIST26 Tandem Demo in its original configuration first. Users can become familiar with library searches, chromatogram analysis, spectral comparisons, and Hybrid Search before attempting to integrate the software with an external instrument-data system.
Vendor-spectrum import can be valuable, especially when a laboratory already relies heavily on applications such as Agilent MassHunter. However, it introduces dependencies on file locations, executable names, Windows settings, and import options.
The demonstration shows that such a connection can be established, while also illustrating why the resulting workflow must be tested carefully. Confirming that spectra are transferred correctly—and that accurate-mass information is preserved—is ultimately more important than simply getting the two applications to communicate.




