-
I am running `kat gcp` using Snakemake on a cluster and have run into a problem upon what seems to be the completion of the `kat gcp` command.
I am running:
```
rule kat_rawRead_gcp:
params…
-
Hi Kristoffer,
During nf-core/isoseq test jobs, I randomly have a bug:
```
total_flanks2: 20352
total_flank_size 20395551
total_unique_segment_counter 7303161
total_segments_bad 5517888
bad…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…