-
Notifications
You must be signed in to change notification settings - Fork 1
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
Stochastic segfault #7
Comments
This is crazy. There should be something better than Bioconductor. Vivek Sent from my cell phone. Please excuse any inevitable typos. On Nov 28, 2011, at 4:49 PM, Marc Juul Christoffersen <reply+i-2375614-
|
Yeah. I'm definitely looking for something better. |
Hey Marc, Lets keep tomorrow's lunch time at Market place for chatting about your Vivek On Tue, Nov 29, 2011 at 11:25 AM, Marc Juul Christoffersen <
|
Example of error: Now analyzing FCS file: /var/rails/biofab-web/public/flow_cytometer_input_data/BD_GOII_PlateM5-M11_TetR/BD_GOII_M5-M11-TetR-gfp_102611_plate2_w_GC/BD_GOII_M5-M11-TetR-gfp_102611_plate2_w_GC-13.fcsEvents: 12831 *** caught segfault *** Traceback: |
Yeah, it's as bad as it sounds.
I think it happens in the clustGating function within the fcs-analysis R program. Difficult to debug since it's not always reproducible, but it's possible that it only happens for small datasets.
The segfault takes down the entire daemon that runs scheduled jobs, so no other jobs get run after such a segfault.
Note: This is actually a bug in the BioConductor flowClust library.
The text was updated successfully, but these errors were encountered: