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

trim-low-abund.py fails with zero exit status: graph structure is too small #1852

Open
fungs opened this issue Apr 12, 2018 · 6 comments
Open

Comments

@fungs
Copy link

fungs commented Apr 12, 2018

Hi,

I just ran khmer for kmer pruning on > 300 samples in quiet mode. Somewhere in the middle, I got this on stderr (I didn't log stderr, my bad).

**
** ERROR: the graph structure is too small for 
** this data set.  Increase data structure size
** with --max_memory_usage/-M.
**
** Do not use these results!!
**
** (estimated false positive rate of 0.889; max recommended 0.800)
**

When I screen throught the running stats, all jobs have zero exit status. Sorry, this is really ..., basic programming. Now I probably have to redo computations for all files because khmer does not do proper error reporting.

Best,
Johannes

@ctb
Copy link
Member

ctb commented Apr 12, 2018 via email

@ctb
Copy link
Member

ctb commented Apr 12, 2018 via email

@fungs
Copy link
Author

fungs commented Apr 12, 2018

Sorry, I forgot the details:

trim-low-abund.py -C 3 -Z 18 -V -M 4e9 -T $TMPDIR -q -o - $infile | pigz > ${outfile}

@fungs
Copy link
Author

fungs commented Apr 12, 2018

I installed the latest version via pip, which is 2.1.2

@fungs fungs changed the title kmers fails with exit code 0: graph structure is too small trim-low-abund.py fails with exit code 0: graph structure is too small Apr 12, 2018
@fungs fungs changed the title trim-low-abund.py fails with exit code 0: graph structure is too small trim-low-abund.py fails with zero exit status: graph structure is too small Apr 12, 2018
@fungs
Copy link
Author

fungs commented Apr 13, 2018

Please check but I think this might be the same pipe issue as in #1853, sorry about that.

@ctb
Copy link
Member

ctb commented Apr 13, 2018 via email

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

2 participants