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

Are you missing .ctab files issue #186

Open
zoe-elizz opened this issue Apr 18, 2022 · 0 comments
Open

Are you missing .ctab files issue #186

zoe-elizz opened this issue Apr 18, 2022 · 0 comments

Comments

@zoe-elizz
Copy link

Hello, I'm having an issue getting my .ctab files into R. My .ctab files were generated from Stringtie by specifying a ballgown readable output (-B). I have a similar directory structure to the example provided where I have set my working directory to my "RNA_seq2021" folder in R and in here I have my root folder "Bees", within which I have subfolders for each of my samples (VB_B1, VB_B2, VB_V3,...VB_B29) and in these subfolders are my 5 .ctab files. Below is the code I have run:

VB_sample<c('VB_B1','VB_B2','VB_B3','VB_B4','VB_B5','VB_B6','VB_B7','VB_B8','VB_B9','VB_B10','VB_B11','VB_B12','VB_B13','VB_B15','VB_B16','VB_B17','VB_B18','VB_B20','VB_B21','VB_B22','VB_B23','VB_B24','VB_B25','VB_B26','VB_B27','VB_B28','VB_B29')
VB_dir<-paste0('~/Bees/', VB_sample)
bee_bg2<-ballgown(samples=VB_dir, meas='all')
But I keep getting this error:
Error in ballgown(samples = VB_dir, meas = "all") :
Something is wrong: are you missing .ctab files? Do extra files/folders (other than tablemaker output folders) match your samples/dataDir/samplePattern argument(s)?

I have also tried running:

bee_bg<-ballgown(dataDir='~/Bees', samplePattern='VB_B', meas='all')
but get this error:
Tue Apr 19 09:24:15 2022: Reading linking tables
Error in file(file, "rt") : invalid 'description' argument

Any suggestions on what is wrong?? This appears to be a common error that people get and I have combed through logged issues on bioconductor and git hub and haven't found a real explanation on how they fixed it or what is actually wrong.

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

1 participant