-
Notifications
You must be signed in to change notification settings - Fork 44
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
Earlier crash for NA values in the SEX column #568
Comments
Hi Jakob, thanks for reporting. Do you mean the column was empty or it had the string |
The column had the string "NA" as value for all samples. Yes, I realize that it isn't easy to cover all input issues! |
Some follow up here. I added a dummy column with all 'M'. Apparently this did not pass this step either. I checked the behaviour of lda, and it indeed seems that it will crash if there is only one level in y:
( I will try running again with no Finally, on the topic of NA-values. I ran into a separate NA issue, where the These issues are not blocking me, and I realize that it must be a challenge to maintain such a varied code base. Just wanting to let you know, so that some future travellers might have a shorter route ⛰️ |
Yes, the problem is that the formula needs at least 2 values to try to categorize them. That's why all M doesn't work. |
Hello, and thanks for this cool pipeline!
I have been spending some time debugging DROP. The last error was for the aberrant expression workflow inside the
Summary.R
script from the line:It took me some time to figure out, but I realized in the end that the original error was that I had accidentally supplied a SEX column filled with "NA".
For me as a user, it would be useful if this was catched upstream in the pipeline, or alternatively if the
Summary.R
script could handle this similarly to as if there are no gender information.The text was updated successfully, but these errors were encountered: