EZSTATS
  • Home
  • Publications
  • Download
    • Update alerts
    • Donate
  • Team
  • FAQ

Download

Current version

EZSTATSG3.6
  • All features from EZSTATSG3.4 plus:
    • Shimadzu calibration reports now supported!
    • Data file names for each batch added to reports.
    • Choose which calibrators to import (if there are >7)
    • Fixed bug that was overwriting results.
  • Calibration data from Thermo TraceFinder, Agilent MassHunter, Waters UNIFI, SCIEX MultiQuant and SCIEX OS, and Shimadzu reports can be directly imported.
    • Reports must be in *.xlsx, *.xls, *.csv, or *.txt format.
  • For Thermo data:
    • Reports must be in Calibration Report format​.​
    • Thermo QC data can be imported if it is in the default QC Report format. Files must be formatted as follows:
      1. Each trial must have it's own folder named "Trial_1", "Trial_2"... OR "Trial 1", "Trial 2"... (not case sensitive).
      2. Each individual file name must contain the QC level i.e., "High", "Low", "Mid" (not case sensitive).
  • For SCIEX MultiQuant and SCIEX OS data:
    • There must be an ISTD Area column.

    Have you tried EZSTATS?

Submit

Previous versions

EZSTATSG3.5
  • All features from EZSTATSG3.4 plus:
    • Bug fix regarding ISTD in Waters importation.
    • Support for SCIEX OS data.
  • Calibration data from Thermo TraceFinder, Agilent MassHunter, Waters UNIFI, and SCIEX MultiQuant and SCIEX OS reports can be directly imported.
    • Reports must be in *.xlsx, *.xls, *.csv, or *.txt format.
  • For Thermo data:
    • Reports must be in Calibration Report format​.​
    • Thermo QC data can be imported if it is in the default QC Report format. Files must be formatted as follows:
      1. Each trial must have it's own folder named "Trial_1", "Trial_2"... OR "Trial 1", "Trial 2"... (not case sensitive).
      2. Each individual file name must contain the QC level i.e., "High", "Low", "Mid" (not case sensitive).
  • For SCIEX MultiQuant and SCIEX OS data:
    • There must be an ISTD Area column.

​EZSTATSG3.4 (1/2022)
  • Calibration data from Thermo TraceFinder, Agilent MassHunter, Waters UNIFI, and SCIEX MultiQuant calibration reports can be directly imported.
    • Reports must be in *.xlsx, *.xls, *.csv, or *.txt format.
    • Target compound no longer needs to be in the same tab index or column across workbooks.
  • For Thermo data:
    • Reports must be in Calibration Report format​.​
    • Thermo QC data can be imported if it is in the default QC Report format. Files must be formatted as follows:
      1. Each trial must have it's own folder named "Trial_1", "Trial_2"... OR "Trial 1", "Trial 2"... (not case sensitive).
      2. Each individual file name must contain the QC level i.e., "High", "Low", "Mid" (not case sensitive).
  • For SCIEX MultiQuant data:
    • There must be an ISTD Area column.
  • Bug fix for < 7 calibrators using Agilent importation.
  • Bug fix on Ion Suppression page.
  • Decimals supported to accommodate Agilent data.
  • Updated color scheme and formatting for readability.​
EZSTATSG2.1.3 (5/2022)
  • Feature addition - if the c term of the quadratic equation is in error, each term will be flagged red
  • Bug fix - Nonnumeric values do not result in an error in userform
  • Bug fix - User is prompted to change analytes/assays containing "/" or "\"
EZSTATSG2 (4/2022)
Download template from Supplementary Data
  • Flexible five-, six-, or seven-point calibration curves
  • Six weighted quadratic calibration models
  • Standardized residuals by use of frequency plots overlaid with the normal distribution function along with five-number summary data
  • Processed sample stability function
  • Implementation of Visual Basic for Applications (VBA) in Excel UserForms
EZSTATSG1 (2021)
Download template from Supplementary Data
  • Weighted linear calibration models
  • Bias and precision data for the lower limit of quantitation
  • Quality controls
  • Dilution integrity
  • Ion suppression
Contact Szabi
Proudly powered by Weebly
  • Home
  • Publications
  • Download
    • Update alerts
    • Donate
  • Team
  • FAQ