773232AH
4-15
Specifications
Software Specifications
4
are 0 in the HEADER segment. Each offset specified in the HEADER segment is referred to the
beginning of the HEADER segment itself.
TEXT Segment
The TEXT segment contains a set of keyword - keyword value combinations delimited by the “/”
character. The set contains all the required keywords as specified by the FCS 3.0 standard as well as
some optional ones. In addition, the keyword set includes a number of custom keywords that
provide additional information about the data being collected. Custom keywords are preceded by
the “@” character.
Here is a list of keywords included in the TEXT segment:
Table 4.2
FCS 3.0 Keyword Information
FCS 3.0 Keyword
Key Value
$BEGINANALYSIS
Offset to the beginning of the ANALYSIS segment. This value is always 0.
$BEGINDATA
Offset to the beginning of the DATA segment. This value matches the offset
specified in the header section.
$BEGINTEXT
Offset to the beginning of the supplemental TEXT segment. This value is always
0 because no supplemental TEXT segment is used.
$BYTEORD
Little endian: “1,2,3,4”
$COMP
Compensation matrix. The matrix is nxn. Where n is equal to the value of the
$PAR keyword. Every parameter acquired will have corresponding values in the
compensation matrix.
The order of the parameters in the matrix is determined by the index assigned to
each parameter in the TEXT segment. See the $PAR keyword for more
information about acquired parameters.
$DATATYPE
Single character defining base data type of binary data: I = integer.
$ENDANALYSIS
Offset to the end of the ANALYSIS segment. This value is always 0.
$ENDDATA
Offset to the end of the DATA segment. This value matches the offset specified in
the header section.
$ENDTEXT
Offset to the end of a supplemental TEXT segment. This value is always 0
because no supplemental TEXT segment is used.
$MODE
Single character defining mode of data: L=list mode.
$NEXTDATA
Byte offset into binary data for next data item. This value is always 0.
$PAR
Number of parameters selected in the protocol. Since data is only stored for linear
parameters, this value does not include logarithmic versions of the parameters.
In the event that only the logarithmic version of a parameter has been selected
in the protocol, its corresponding linear data will be stored and thus counted in
$PAR. The RATIO parameter is not stored in the FCS 3.0 DATA segment and thus
not counted in the $PAR value.
This number also indicates the number of parameters per event in the DATA
segment.
The parameter indexes are independent of the order in which they were selected
in the protocol. Parameter indices in the FCS 3.0 section need not be equal to the
parameter indices assigned in the FCS 2.0 section.
Содержание Navios
Страница 8: ...773232AH viii Safety Notice Safety Symbols ...
Страница 34: ...xxxiv Tables A 2 Code Related Specifications A 6 ...
Страница 38: ...773232AH xxxviii Introduction Graphics ...
Страница 44: ...773232AH 1 6 Use And Function Material Safety Data Sheets MSDS ...
Страница 72: ...773232AH 3 18 Operation Principles Plot Display ...
Страница 90: ...773232AH 4 18 Specifications Software Specifications 1 2 3 ...
Страница 140: ...773232AH 5 34 System Overview Using The System Help ...
Страница 154: ...773232AH 6 14 Daily Routine Cytometer Auto Startup ...
Страница 194: ...773232AH 8 16 Running Samples Data Review ...
Страница 412: ...773232AH 10 216 Using Navios Software Report Generator Error Log ...
Страница 446: ...773232AH 11 34 Cleaning Procedures Power The Cytometer Only On off ...
Страница 522: ...773232AH 13 30 Troubleshooting Cytometer Control Window Cannot Be Viewed ...
Страница 530: ...773232AH A 8 Bar code Specifications Checksum Algorithm ...
Страница 540: ...773232AH References 2 References ...
Страница 582: ...Index 36 Index ...
Страница 584: ...773232AH Warranty 2 Beckman Coulter Inc Customer End User License Agreement ...
Страница 585: ......