Dear Florian,

I came across a tiny issue with a file from the BD Influx, in which  
the delimiter in the FCS3.0 header was "/", and some of the $PnN  
values used a "/".  For example, $P5N is "530/40 [488]".  In the file,  
the "/" in the keyword value is indicated by consecutive "//".

According to Data File Standard for Flow - FCS 3.0 - www.isac-net.org,  
as horrible as it seems, this appears to be correct:

3.2.7 The delimiter may not be the first character in a keyword or  
keyword value. If the delimiter appears in a keyword or keyword value,  
it must be immediately followed by a second delimiter. For example,  
"$SYS/RSX-11//M/" shows a value of RSX-11/M for the keyword $SYS.  
Since null (zero length) keywords or keyword values are not permitted,  
two consecutive delimiters can never occur between a value and a  
keyword.

I would be happy to send an example file for testing.

Best regards,
Wade
Wade T. Rogers, Ph.D.
Director, Computational Biology and Research Informatics
Path BioResource
Adjunct Associate Professor
University of Pennsylvania
rogersw@mail.med.upenn.edu
267-350-9680 (o)
610-368-5821 (m)
	[[alternative HTML version deleted]]

