Skip to content
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

small suggestions #5

Open
kvittingseerup opened this issue Feb 21, 2020 · 5 comments
Open

small suggestions #5

kvittingseerup opened this issue Feb 21, 2020 · 5 comments

Comments

@kvittingseerup
Copy link

I've been using run.Ted a few times now and I've made a couple observations which results in TED giving uninformative error message. These should be easy for you to implement small test to prevent other people from making the same (stupid) mistakes as me.

Mistake 1: Having gene(s) with all zeros (I think). I had a bulk dataset which gave this error:

[1] "inferred cell percentage"
[1] "correct batch effect"
[1] "every gene has at least one zero. vst transformation is NOT feasible"
[1] "run final sampling"
Error: $ operator is invalid for atomic vectors
In addition: Warning message:
In mclapply(1:N, FUN = function(i) { :
  all scheduled cores encountered errors in user code

After I filtered the data to remove genes with only zeroes the run went fine.

Mistake 2:

The second is that due to a typo I tried running with a data.frame which had NAs in - this also cause TED to fail with an uninformative error message - and took a while to figure out.

Mistake 3:
I make a spelling mistake causing my logic argument to retun an empty vector to be used with the tum.idx argument which naturally caused TED to fail with an uninformative error message

Guess the morale is don't underestimate how strange things users can do :)

@tinyi
Copy link
Collaborator

tinyi commented Feb 21, 2020 via email

@tinyi
Copy link
Collaborator

tinyi commented Feb 22, 2020 via email

@ThomasJamesMitchell
Copy link

Nice method - just testing it out at the moment.

I have spent a bit of time struggling with error messages also. One of which came about because I provided cell.type.labels and cell.subtype.labels as factors rather than characters. This took a little unpicking as it was not at all obvious what the issue was. A fix might save others time!

Thanks!

@tinyi
Copy link
Collaborator

tinyi commented Jun 29, 2021 via email

@ThomasJamesMitchell
Copy link

ThomasJamesMitchell commented Jun 29, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants