Comments (6)
Hi @shenwei356,
The pipeline was designed to process only input fasta at the time, but you should be able to run as many instances if VIRify as you want.
That error you are getting is related to Nextflow, not VIRIfy (as far as I can tell). Things you could try:
- Delete the cache and pull the pipeline again,
rm -r /home/shenwei/.nextflow/assets/EBI-Metagenomics/emg-viral-pipeline
andnextflow pull EBI-Metagenomics/emg-viral-pipeline
(similar to nf-core/ampliseq#160) - Not sure if related, but check that each instance of VIRify is using a different work directory
Cheers
from emg-viral-pipeline.
Hi Martín, thanks for your rapid reply.
I've tried to clean and re-pull the pipeline, but the same error occurred. Besides, after trying with multiple instances, it would be failed to run with one instance. So I have to re-pull again to run with one instance.
Not sure if related, but check that each instance of VIRify is using a different work directory
Confirmed.
BTW the server has an old java:
NOTE: Nextflow is not tested with Java 1.8.0_332 -- It's recommended the use of version 11 up to 18
from emg-viral-pipeline.
Hey @shenwei356 thanks for your interest in the pipeline! I'm not sure if I fully get what you are trying to do. But just in general and as also mentioned by @mberacochea:
- you can only start one nextflow pipeline from the same directory simultaneously. Nextflow is writing a hidden
.nextflow.log
file and therefore starting multiple nextflow commands from the same directory will cause errors. - you can just give a multiFASTA as input
I'm not sure if the old JAVA might also cause issues.
from emg-viral-pipeline.
you can only start one nextflow pipeline from the same directory simultaneously. Nextflow is writing a hidden .nextflow.log file and therefore starting multiple nextflow commands from the same directory will cause errors.
I see, but I specify the --workdir which point different places (where the inputs are). If it's true, the right way should be changing directory to where the input file is before running the pipline.
from emg-viral-pipeline.
you can only start one nextflow pipeline from the same directory simultaneously. Nextflow is writing a hidden .nextflow.log file and therefore starting multiple nextflow commands from the same directory will cause errors.
I see, but I specify the --workdir which point different places (where the inputs are). If it's true, the right way should be changing directory to where the input file is before running the pipline.
Yeah --workdir
or in short -w
will not help you. This just changes where to working directories are written when running processes in the pipeline. Still there will be the hidden .nextflow.log
file written to the directory from which you start the pipeline. No other pipeline can then be started from the same folder while the other one is still running and locks the .nextflow.log
file - at least as far as I know. So yes, what you would need to do is: create a directory for each run, cd
into that dir and then execute nextflow.
from emg-viral-pipeline.
Thank you all!
from emg-viral-pipeline.
Related Issues (20)
- Unable to locate package docker-ce-cli HOT 1
- `annotate:ratio_evalue (1)` terminated with an error exit status (1) -- 'nextflow-autodownload-databases' Is a directory error HOT 1
- Can Prodigal-GV make 'real world' difference compared to original Prodigal? HOT 2
- Update ViPhOGs to remove old models that are associated with discontinued viral taxa HOT 5
- CWL discontinued
- No space left in /tmp HOT 2
- preprocess:rename idle state HOT 12
- Fix sankey plot visualization for undefined ranks
- Imitervirales assignment although not well supported by ViPhOGs
- Repository may be corrupted HOT 3
- Taxonomic ranks are inverted HOT 9
- Issue for running on ARM64-based Linux VM HOT 5
- wrapper_phage_contigs_sorter_iPlant HOT 1
- [Feature Request] Conda Distribution for Taxonomic Identification HOT 1
- Input file name collision on 'annotate:write_gff' HOT 2
- COBRA improves the completeness and contiguity of viral genomes assembled from metagenomes
- Missing process or function with name 'getFileSystem' HOT 3
- Not able to run "nextflow pull EBI-Metagenomics/emg-viral-pipeline" HOT 2
- Error executing process > 'annotate:hmmscan_viphogs (1)'
- CheckV failed HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from emg-viral-pipeline.