So you will find screenshot of the hexadecimal representation of the content of the modified 3.1 FCS. Nevertheless, I corrected the END values on my own.Ĭoncerning the original question about data, I am binary guy. I tried flowIO at for the first time and found it interesting. Once corrected (with // replaced by _), no more error during read.FCS. Concerning the end of TEXT, pointing on the next character after the last delimitr leads to make flowCore thinks that there is an extra keyword. So the 3.1 FCS is wrong in pointing the end of TEXT and DATA.
#> Error in fcsTextParse(txt, emptyValue = emptyValue): Empty keyword name detected!If it is due to the double delimiters in keyword value, please set emptyValue to FALSE and try again!Ĭreated on by the reprex package (v0.2.0). #> FL1-A FL1-H FL2-A FL2-H F元-A F元-H FL4-A FL4-H FL5-A FL5-H #> 1 1 1 1 1 0 0 1 1 1 # modified version # // replaced by _ # ENDXXX corrected -1 # SPILLOVER is diagonal ff31mod = read.FCS(file.path( mydir, "1696_1.0001_3p1_mod.fcs "), transformation = FALSE, truncate_max_range = FALSE, min.limit = NULL)Īpply(exprs( ff31mod), 2, RowSums(keyword( ff31)])ĬolSums(keyword( ff31)])
#> uneven number of tokens: 679 #> The last keyword is dropped.
#> "c:/Users/sampgg/Downloads/MiltenyiFCS/" # original file ff31 = read.FCS(file.path( mydir, "1696_1.0001_3p1.fcs "), emptyValue = FALSE) ( mydir = "c:/Users/sampgg/Downloads/MiltenyiFCS/ ")