To be honest, FlowJo has always had a bit of trouble Piece explicitly specified), and Gating-ML 2.0 (which is mainly based on an Gating-ML 1.5 (which transforms data using compound transformation with Transformation workflow is implemented is completely different between > spectrumMatrix (manually or by altering the source code), but the result Gating-ML 2.0 (as summarized in pages 91-93 ofįlowcyt.sf.net/gating/latest.pdf). There are several other important changes between Gating-ML 1.5 and On Tue, at 4:15 PM, Mike Jiang here is the answer from I think it still applies, but let me know if you need any more details. You can mention that Gating-ML 2.0 is now an official ISAC standard (i.e., approved by ISAC council on January 13, 2015). Maybe try to ping them to check what their estimated timeline may be. I believe FlowJo's committed to improve their Gating-ML support, including proper support for Gating-ML 2.0 with the spectrumMatrix element (eventually). ![]() To be honest, FlowJo has always had a bit of trouble working with Gating-ML transforms, so even if you got a proper Gating-ML 1.5 output, FlowJo wouldn't likely reproduce the gate memberships properly. Most importantly, the way how the transformation workflow is implemented is completely different between Gating-ML 1.5 (which transforms data using compound transformation with piece explicitly specified), and Gating-ML 2.0 (which is mainly based on an implicit workflow). You could change the spilloverMatrix -> spectrumMatrix (manually or by altering the source code), but the result would be far from Gating-ML 1.5. There are several other important changes between Gating-ML 1.5 and Gating-ML 2.0 (as summarized in pages 91-93 of flowcyt.sf.net/gating/latest.pdf). Sorry, flowUtils cannot write Gating-ML 1.5 output
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |