-
Notifications
You must be signed in to change notification settings - Fork 4
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
genome in TSSlogo function #123
Comments
solved by passing genome as an argument:
|
Hi Katalin, yes if your |
great, thanks! I will try to fix that then |
Hi again,
I have been reading the source code for some time and cannot find the step where I should add this info. Can you maybe point me there? |
Hi Katalin, I think that there is no good way to add BSgenome information after the object was created. Have you tried re-loading the data from scratch? |
Hi Charles,
|
Hi Katalin and Damir, that sounds cool, just to make sure, is it to create a Where are the bigWig files from? Are they produced by a public pipeline? I see in your code that it is quite specific to some naming conventions… Also, please be prepared that I will ask you to not add new dependencies on tidyverse packages if possible, as CAGEr's dependency count is already quite high... Finally, you can have a look at the kind of studies I did in the Have a nice day, Charles PS: I am thinking about a way to allow the user to pass a FASTA file instead of a BSgenome object when it does not make sense to take all the effort to create such object. We can discuss it by email or via another issue. |
Nice! thanks for the quick reply! That is correct, it takes bigwigs and the end point is a CAGEexp object. It works all well actually for most steps: TSSlogo fails as noted above and I haven't added all steps yet (only until tagcluster qc). I wanted to ask if you think this feature (not in its current form) could eventually go into CAGEr itself, but first I really need to get the pipeline in a decent shape, so I am not volunteering myself for that yet :) The pipeline is not public yet, but the input is from STAR's Nextflow module so that is fairly standard. It will allow the user to start from fasta instead of bsgenome, but we can coordinate about that too. |
I have some troubles with TSSlogo. I load the annotation from txdb like this:
and run TSSlogo like this:
The error I get:
for checking:
The text was updated successfully, but these errors were encountered: