env { NXF_WORK = './data/work'
}
--
You received this message because you are subscribed to the Google Groups "Nextflow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nextflow+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/nextflow.
For more options, visit https://groups.google.com/d/optout.
The env variables defined in the nextflow config file are meant to be used by the tasks executed by NF, not by the NF process itself.However you can still define the work directory in the config file by using the setting `workDir` eg.workDir = '/some/work/path`Hope it helps.Cheers,
Paolo
On Wed, Jun 14, 2017 at 4:14 AM, Sasha Mikheyev <mikh...@gmail.com> wrote:
Hello!I can't get the NXF_WORK feature to change the 'work' path -- it is always created in the same directory as the script. I tried to change it using the nextflow.config, as below, without success
env { NXF_WORK = './data/work'
}This verifiably changes the variable in the .nf file, but not the location of the working directory. Interestingly, using the -w switch with nextflow does change work directory. Any ideas?Thank you,Sasha
--
You received this message because you are subscribed to the Google Groups "Nextflow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nextflow+u...@googlegroups.com.