-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flowCore::read.FCS works but CytoML::flowjo_to_gatingset fails; no valid FCS file #152
Comments
Here you can find a respective FCS file (https://www.dropbox.com/s/t3qaixahp6vze78/test.fcs?dl=0). As described, flowCore::read.FCS works. But when the file is within a flowjo workspace and one tries to read the workspace with CytoML::flowjo_to_gatingset the above mentioned error comes up. Any ideas? |
I am also having a hard time to find out where this is triggered. I think it is somewhere in the C++ routine which I am not familiar with. I wonder what exactly makes the function think this is not a valid FCS file. |
What happens if you pass |
Same error. |
Incidentally, a colleague was facing a similar error using read.flowSet(path = "somedir"). In fact, there was a non FCS hidden file in the dir, which leads to the same error. As read.flowset does not show the file being invalid, it tooks me a few minutes before finding it, as all FCS files were correctly read with read.FCS. Maybe the same problem... |
I tried to trace the error. So I isolated a respective FCS file and the related workspace. Hence I would say this is unlikely. Thanks for your input though. |
Your OS is MacOS, Linux or Windows? |
MacOS |
I cannot test this OS.
|
Thanks for your input I think I figured it out: While additional keywords can be added to identify FCS files by flowjo_to_gatingset(), the $FIL keyword appears to be obligatory. I thought I tried to fix the issue that way earlier but it did not help then. When I tried again it did help. Sorry for disturbing you. |
That's OK to try helping as long as the helpers get some feedback in the end. It's good to keep a track in order to help if the case occurs again. |
Dear community,
I have a few problematic FCS files which have been converted from .mqd files on a MacsQuant machine. Anyhow, not all files are affected.
For some of them CytoML::flowjo_to_gatingset throws an error:
Error in (function (ws, group_id, subset, execute, path, cytoset, backend_dir, :
This does not seem to be a valid FCS2.0, FCS3.0 or FCS3.1 file
But the files can be read with flowCore::read.FCS (setting emptyValue = F though).
Any idea how to approach the conflicting results and how to find out what's the issue?
Thanks.
The text was updated successfully, but these errors were encountered: