Skip to content
This repository has been archived by the owner on Feb 7, 2023. It is now read-only.

"Nothing to be done" when running locally #31

Open
nklier38 opened this issue Aug 9, 2021 · 1 comment
Open

"Nothing to be done" when running locally #31

nklier38 opened this issue Aug 9, 2021 · 1 comment

Comments

@nklier38
Copy link

nklier38 commented Aug 9, 2021

Following the readme file, I have put the fastq files, a .fa of the reference trnascriptome, and a .gtf corresponding to the transcriptome in the data folder, and edited the config file appropriately.

When first running the pipeline, it installed all of the dependencies without a problem. Now, it gives the following message:

Building DAG of jobs...
Nothing to be done.

I cannot identify anything else I have to provide to make it work, am I setting up the config.yaml incorrectly?

@saifashraf
Copy link

Hello,
I have started using this pipeline lately so a bit late reply.
"Nothing to be done" usually comes when output folder named in config file by you is already present in same location. Better you remove same name folder from that location or change the output folder name in config file. Point is one should not name the output folder in config file as one already present in location.
Hopefully this will help anyone finding this error.
Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants