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
DESeq2 version collision #36
Comments
I am facing the similar issue: There version for DESeq2 I have is 1.20.0, JunctionSeq:1.5.4 with R: 3.5.0 |
The github version sometimes conflicts depending on which version of R/DESeq2 you are running. I recommend using the Bioconductor version that goes with your current R version. In other words, install using the command:
|
With which version(s) of DESeq2 is the latest version of JunctionSeq compatible? |
The GitHub version is compatible with Bioconductor 3.4, and DESeq2 v1.10.1. It might be compatible with 3.5, I'm not sure. It definitely is incompatible with any of the versions found in bioconductor 3.6 and higher. I recommend using the Bioconductor version. I haven't updated the GitHub version to match because it includes C++ code that requires compilation. Bioconductor pre-compiles all those source files on linux, windows, and OSX. Without this pre-compilation, installing packages that include C++ code from source is non trivial and requires the several external tools which may not be installed on users' machines. On linux it's usually fine but on OSX and windows it's a pain. I keep the bioconductor version up-to-date. Use that one. |
any solution to this? I am using DeSeq2 v1.32.0 and JunctionSeq v1.5.4. Bioconductor doesn't support JunctionSeq now. Is it possible to run this anyway? |
Is there another way to use JunctionSeq other than downgrading? I run
|
Error in .Call("DESeq2_fitDisp", PACKAGE = "DESeq2", ySEXP, xSEXP, mu_hatSEXP, : Any solution for this |
Hello,
I'm using the latest version of JunctionSeq (1.5.4), and have generated the following error using DESeq2 versions 1.20.0 (R 3.5.0) and 1.18.1 (R 3.4.2):
I suppose the interim solution is to downgrade to DESeq2 pre v1.15 ?
Hopefully it's not too complicated to update JunctionSeq to play nicely with current and future DESeq2 versions..?
Many thanks for your help and this excellent tool.
The text was updated successfully, but these errors were encountered: