Skip to content
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

Problem when output (filtered) is empty #7

Open
fmalmeida opened this issue Sep 23, 2021 · 3 comments
Open

Problem when output (filtered) is empty #7

fmalmeida opened this issue Sep 23, 2021 · 3 comments

Comments

@fmalmeida
Copy link

Hi,

First of all congratulations on developing such nice tool.

I am currently facing a problem that is:

Filtering for presence of LRRs...
Traceback (most recent call last):
  File "/opt/NLGenomeSweeper-master/NLGenomeSweeper", line 302, in <module>
    main(sys.argv[1:])
  File "/opt/NLGenomeSweeper-master/NLGenomeSweeper", line 298, in main
    run_interproscan(program_dir, args.outdir + nlg_folder, args.t)
  File "/opt/NLGenomeSweeper-master/NLGenomeSweeper", line 196, in run_interproscan
    shell=True, check=True)
  File "/miniconda/envs/NLGenomeSweeper/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '/opt/NLGenomeSweeper-master/scripts/region_interproscan.sh ./NLGenomeSweeper/02_domain_identification/ 10 /opt/NLGenomeSweeper-master/' returned non-zero exit status 1.

It breaks on the "Filtering step". I have seen the temporary outputs and it seems to raise this error because no candidates have passed the filter (The filtered bed is blank). I believe, instead of raising the error, the pipeline should output a blank result.

What do you think?

Felipe.

@ntoda03
Copy link
Owner

ntoda03 commented Mar 6, 2022

Hi! The filtering step work with empty files as long as they exist, which they always should. I've added some upstream checks but I don't see any way that step could fail. If you're still interested in this or have example files let me know.

@fmalmeida
Copy link
Author

Hello there!
Well, unfortunately I do not recall with which data this has happened. I'm still interested on it but don't know exactly how to help now. For now I have created a rule in my pipeline to ignore this error and create an empty final result ... But I don't believe is the best option.

Maybe if we use a contig that we know does not have any candidate and would therefore not generate results it can act as an example dataset for this?

@learning666666
Copy link

I have this problem, too. Do you have any solution ?

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

No branches or pull requests

3 participants