-
Notifications
You must be signed in to change notification settings - Fork 3
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
function error for BSJs #2
Comments
Hi, S |
Hi,
I am using the same folder and directory location as of Friday. Even after
using check, it also works, until I go and use the function
backsplicejunctions. I never saw this error previously so I was wondering
if there was any update over the weekend that could have caused this issue
On Tue, Jun 2, 2020 at 12:41 AM Aufiero ***@***.***> wrote:
Hi,
from what you reported I think it is not a problem of the GTF file. The
GTF file is read correctly.
The function getBackSpliceJunctions is trying to read the file containing
the circRNA prediction results (circRNA_X.txt, see vignettes).
Check if you correctly set your working directory (folder
projectFolderName) and that the subfolders (mapsplice or nclscan, knife,
circexplorer2, or uroborus or circmarker or other) contain the
circRNA_X.txt file. Check also that experiment.txt reports the correct file
name. Let me know if you solved the problem.
S
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5TFUCI3PZWDYZRLRQTK7TRUSULDANCNFSM4NP6QELQ>
.
--
Regards,
Aayushi
|
Hi Aayushi, it might be that there was an update from the new version of dplyr package that is causing problems. I'll look into it the very next days and if there are any changes I'll push those and you can install the latest version of circRNAprofiler. |
Great. Thanks for letting me know!
On Tue, Jun 2, 2020 at 11:49 AM Aufiero ***@***.***> wrote:
Hi Aayushi,
it might be that there was an update from the dplyr package that is
causing problems.
I'll look into it the very next days and if there are any changes I'll
push those and you can install the latest version of circRNAprofiler.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5TFUDI7XATBVKR6T5W7K3RUVCVNANCNFSM4NP6QELQ>
.
--
Regards,
Aayushi
|
Hi Aayushi, I fixed the bugs. Now the release version of circRNAprofiler builds correctly on Bioconductor. if (!requireNamespace("BiocManager", quietly = TRUE)) For the documentation see: Let me know if you can proceed with the analysis. Best, |
Hi Simona,
I will check if I can proceed with the analysis now and let you know.
Thanks for fixing the bugs so soon.
On Sun, Jun 7, 2020 at 2:05 AM Aufiero ***@***.***> wrote:
Hi Aayushi,
I fixed the bugs. Now the release version of circRNAprofiler builds
correctly on Bioconductor.
You can install the release version of circRNAprofiler using:
if (!requireNamespace("BiocManager", quietly = TRUE))
install.packages("BiocManager")
BiocManager::install("circRNAprofiler")
For the documentation see:
browseVignettes("circRNAprofiler")
Let me know if you can proceed with the analysis.
Best,
Simona
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5TFUBNY33RZYORUFC6F43RVNJ5PANCNFSM4NP6QELQ>
.
--
Regards,
Aayushi
|
Hi Simona,
I had no circRNA candidates from chrMT, as I filtered those out, and I still get this error when I delete chrM entries from the gtf data frame manually. It looks like the problem is with genome, I am using mm10, any ideas? |
Hi Aayushi, thanks for letting me know. I'll do a test and I'll let you know. S |
Did you run this to get the genome mm10, right?
And which genome annotation (gtf) did you use? gencode, UCSC, NCBI or Ensemble? |
Yes. Seems like the complication may stem from the fact that the
''genome$chrMT" is not found, and instead it has "genome$chrM". Can that be
something that causes the issue?
…On Mon, Jun 8, 2020 at 12:22 AM Aufiero ***@***.***> wrote:
Did you run this to get the genome mm10, right?
if (!requireNamespace("BSgenome.Mmusculus.UCSC.mm10", quietly = TRUE)){
BiocManager::install("BSgenome.Mmusculus.UCSC.mm10")
}
genome <- BSgenome::getBSgenome("BSgenome.Mmusculus.UCSC.mm10")
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5TFUH535HEXMFKJTOHH5LRVSGSZANCNFSM4NP6QELQ>
.
--
Regards,
Aayushi
|
It might be, and if you remove the circRNAs arising from chrMT, it should work.
BTW I will now introduce this check for chrMT in the code of circRNAprofiler. S |
yep, that was it. It's working now. Thanks, Simona!!
…On Mon, Jun 8, 2020 at 6:12 AM Aufiero ***@***.***> wrote:
It might be, and if you remove the circRNAs arising from chrMT, it should
work.
So in your case bfore running getSeqsFromGRs(), you should fix the chrom:
annotatedBackgroundCircsFixed <- annotatedBackgroundCircs %>%
dplyr::mutate(chrom = ifelse(.data$chrom == 'chrMT', 'chrM', .data$chrom))
BTW I will now introduce this check for chrMT in the code of
circRNAprofiler.
I'll notify you when it's done.
S
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5TFUDDUV3JKS6UBYC5ET3RVTPVLANCNFSM4NP6QELQ>
.
--
Regards,
Aayushi
|
Hey Simone,
I am getting this:
I do not believe it is something that I was seeing before, and as I understand it has something to with a default not getting read correctly, any idea what can be changed? |
No problem. Can you run this command and show me the output: |
This is what I get $downGR |
It's seems ok, you should not get any error since your targetsFTS_gr$upGR$type[1] or targetsFTS_gr$downGR$type[1] is equals to ie. I did a test and if you have targetsFTS_gr$upGR$type[1] or targetsFTS_gr$downGR$type[1] equals to NA you get that error message, but there should be an NA value in there. Could you maybe rerun targetsFTS_gr<- getSeqsFromGRs(...) and check that again? |
Hi Simone,
Yes, it's working now. It seems to be a result of using some genes/genomic
coordinates, whose sequences are not getting fetched as expected, but the
function works otherwise. Thanks for getting back to me, love the package,
it is really well-thought out and useful.
…On Wed, Jun 10, 2020 at 4:15 AM Aufiero ***@***.***> wrote:
It's seems ok, you should not get any error since your
targetsFTS_gr$upGR$type[1] or targetsFTS_gr$downGR$type[1] is equals to ie.
I did a test and if you have targetsFTS_gr$upGR$type[1] or
targetsFTS_gr$downGR$type[1] equals to NA you get that error message, but
there should be an NA value in there. Could you maybe rerun targetsFTS_gr<-
getSeqsFromGRs(...) and check that again?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5TFUGCW7S752AA6HWCW3DRV5TLVANCNFSM4NP6QELQ>
.
--
Regards,
Aayushi
|
Hi Aayushi, thanks, and thanks to you that reported the issues so that I can improve the code. About the chrM/chrMT bugs, in the development version of circRNAprofiler (not in the release) it should be solved. You can install the devel version of circRNAprofiler with:
I'll now close the issue that you opened on Github. |
Hi! I have been trying to do some downstream analysis of my circRNAs, and reached as far as module 12 with it. This was as on Friday, 28th May. Now when I am using the same R script as the package suggested and that was working before, it doesn't work anymore.
> backSplicedJunctions <- getBackSplicedJunctions(gen, pathToExperiment = NULL)
Here I get:
This is what my data looks like after reading the gtf file.
`> head(gen)
The text was updated successfully, but these errors were encountered: