-
Notifications
You must be signed in to change notification settings - Fork 20
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
Non-eukaryotic data and input files? #9
Comments
Hi,
Hope it helps, YB |
This is actually something I'm looking to accomplish for plotting coverage of reads to a bacterial genome reference for one sample. From a very basic effort (as a novice), I've tried the following but am running into an error when I try to create a track dataframe from bam file.
This generates the following error:
I don't know where the 'chr14' is coming from particularly as my alignment is to a single bacterial genome. Of note, here's my meta data file: Here's a text file of my session info. I'm sure this is something ridiculously simple, but I'm just not figuring it out. |
Hi, sorry for late reply, but now I looked into that issue. The problem is that the To make your exmaple work, you need to specify the "region" argument and your samples in the meta data file need to correspond to the name of the BAM file. This example works for me:
It shouldn't be that complicated, will try to fix this. |
Will be fixed with commit 8c537bb |
Hi,
This looks very useful but from all the examples it seems the package focuses mostly on eukaryotic omic data? I wanted to use this for bacterial genomes, to generate a similar plot:
plotting genome coverage, GC, gene annotation, and CNV annotation (without the ideogram). Would this be doable for a bacterial/viral genome and corresponding data?
Looking at the handy tutorials you provided, unfortunately I don't see how to get started from the initial files without loading existing data, or what their format should be. For example, I have:
The way I understand the pipeline:
I guess it should look something like that? Thank you for any feedback!
The text was updated successfully, but these errors were encountered: