Separation Column Handling

[eselmeister]

Currently, some inconsistencies exists when it comes to the separation column handling. The issues will be addressed here as they are:

• Column Mapping
• Backward Compatibility
• Addressing Column Manufacturer Types

[eselmeister]

The column handling is consistent now. All *.msl, *.msp and *.cal files can be consistently marked with the column header.

#COLUMN_NAME=Agilent J&W DB-1701
#COLUMN_LENGTH=30 m
#COLUMN_DIAMETER=0.25 mm
#COLUMN_PHASE=Fused Silica

The column name can be specific for a column available in the market, e.g. "Agilent J&W DB-1701". When loading chromatograms or data, the column is mapped to one of the 4 basic types:

DEFAULT("Default")
POLAR("Polar")
APOLAR("Nonpolar")
SEMI_POLAR("Semipolar")

Hence, it's highly recommended to use the SeparationColumnFactory, which maps the columns to type. The user can freely define specific column mappings.