-
Notifications
You must be signed in to change notification settings - Fork 85
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
Trouble specifying regions for CoveragePlot and visualizing genes #771
Comments
Hi @zrcjessica, could you show the code needed to create the annotation object? As for the gene name issue, this should be fixed in the latest version of Signac. Can you try updating and see if you still have this issue? |
Hi @timoast, here's the code for how I added the annotation to my Signac object: atac <- readRDS("atac.rds")
ens.gtf <- import("Rattus_norvegicus.Rnor_6.0.101.gtf")
genome(ens.gtf) <- "Rnor_6.0"
DefaultAssay(atac) <- "peaks"
Annotation(dat) <- ens.gtf I'm using the GTF file from Ensembl and loading in my Signac object from an RDS file. To update my version of Signac which I have installed with conda, is this the right command? conda update -c bioconda r-signac |
I think the issue is that there are some entries with
This should probably fix it. I'll also work on a fix within the Signac code to ignore entries with As for conda, yes that should update the package. You can check the version that's loaded in R by running |
This should now be fixed on the develop branch, please reopen if you still have issues |
Hi! Reopening because I tried to update Signac (via conda) and got this error when I tried to load it into a new R session:
Any thoughts on what this might be? |
You might need to update Seurat as well, I think this is due to an old issue related to |
I followed the suggestions to update my version of spatstat and also just updated Seurat but now I'm getting this error when I try to load in either Signac or Seurat:
|
Ok, you might also need to update SeuratObject. Normally it's updated automatically, since Seurat depends on SeuratObject >= 4.0.2, not sure why it hasn't in your case. Might be something to do with conda. |
Should I still try to install SeuratObject via conda? |
Yep, if you're using conda to install R packages it's best to stick with using conda for all the packages |
Alright, it seems to have worked, thanks! |
Following up on #746
I have a scATAC-seq dataset on which I've run Cicero and would like to visualize links of interest. I've created a Links object and added it to my Signac object as described in the Signac vignettes. However, I have noticed that I run into issues when I try to specify my own regions for the CoveragePlot (rather than directly giving it a range from the Links object, e.g.
CoveragePlot(object = atac, region = links[1])
). I think that this might be because my custom regions extend past the end of the chromosome, but I have not stringently tested this. In any case, the error message that I get in this case looks something like this:Additionally, I have tried to specify gene names (rather than coordinates) for the
region
argument. For example:According to the docs, this should work. I've also made sure that the annotation associated with my
atac
object contains an entry for this gene, but I get the following error:In my case, I am using the rat genome from Ensembl, Rnor_6.0.
Finally, I have noticed that sometimes when I am plotting a region, genes won't show up when I would expect it to, or I might see parts of gene bodies in the plot but no annotation for their names. For example:
![image](https://user-images.githubusercontent.com/24944136/131751206-713a2115-67f3-463e-8b97-5aa922c42b10.png)
While Tmem212 shows up and is annotated, the other two genes that overlap the window being visualized are not labeled. My hunch is that genes which are not entirely located within the region specified for plotting are not labeled. If that's the case, then I think it would be really helpful to modify the code such that even genes which are only partially located within the plot region are labeled.
Thanks for your help!
The text was updated successfully, but these errors were encountered: