-
Notifications
You must be signed in to change notification settings - Fork 9
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
Could not locate k8 and/or paftools.js in the minimap2 folder, they are required for converting annotation to bed12 files #26
Comments
The pipeline functions now take arguments If you would like to install the latest commit you will need to either have bioconductor in development mode (which requires R 4.4) or apply the following patch with
|
Thanks @ChangqingW for making the updates!
This is a good example of how Bioconductor just adds unneeded complexity to package management in R. I'm using R 4.3.1, and I have no plans on recreating my Docker environment with R 4.4 (the build for rocker/rstudio + Seurat + FLAMES takes nearly an hour). When do you plan on submitting a new release to bioconductor? |
Bioconductor's next release is scheduled on May 1st: https://bioconductor.org/developers/release-schedule/ |
Thanks for letting me know. I'm guessing that I'll have to update R just to use the updated version of bioconductor. I tried to just use The convoluted dependency trees and releases separate to CRAN can really make bioconductor a pain (what's wrong with good-old CRAN?). |
You can try cloning to a local folder, apply the diff I posted to remove |
Thanks @ChangqingW for the suggestion! |
Does Would it be possible to remove |
You can indeed, that is what the git patch file is doing. We can't do it for this branch as it is the devel branch, which is built and checked with Bioc devel. You can also try my own fork |
Patching and running |
I've switched to different computing infrastructure in which software much be installed in conda environments. Installing FLAMES via:
Results in the following error: ── R CMD build ────────────────────────────────────────────────────────────────────────────────────────
✔ checking for file ‘/tmp/Rtmp3pht5z/file15a958461b6c75/FLAMES/DESCRIPTION’ ...
─ preparing ‘FLAMES’:
✔ checking DESCRIPTION meta-information ...
─ cleaning src
─ checking for LF line-endings in source and make files and shell scripts
─ checking for empty or unneeded directories
─ building ‘FLAMES_1.9.2.tar.gz’
ERROR: dependency ‘scater’ is not available for package ‘FLAMES’ Even with the patch,
|
In another attempt with less usage of conda:
The error:
Given that the are nearly 250 total R packages as dependencies for FLAMES, I can see why it can be tricky to install all of them without any errors. |
I didn't see that there is a FLAMES bioconda recipe, so the install become quite simple and much faster: mamba create -n flames bioconductor-flames minimap2 k8 |
Even with the patch, I'm getting:
|
If minimap2 is installed in a linux OS via
apt-get
, the executable is located at/usr/bin/minimap2
, and so "k8 and/or paftools.js" are not located in that directory.It appears that the linux package does not include paftools or k8:
So, it would be helpful to warn users that minimap2 installed via
apt-get
does not work with FLAMES -- at least unless K8 or paftools.js is installed separately.I'm using FLAMES 1.8.0.
The text was updated successfully, but these errors were encountered: