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

smudgeplot.py hetkmers massive memory and walltime required #139

Open
tallnuttrbgv opened this issue Feb 1, 2024 · 3 comments
Open

smudgeplot.py hetkmers massive memory and walltime required #139

tallnuttrbgv opened this issue Feb 1, 2024 · 3 comments
Labels
0.2.5 Double-hung Smudgeplot done with the 0.2.5 Double-hung with curtains version wontfix This will not be worked on

Comments

@tallnuttrbgv
Copy link

tallnuttrbgv commented Feb 1, 2024

Hi,

I have run this pipeline to generate the .dump file. However, smudgeplot.py hetkmers will not finish given 1200 GB of memory and 48 cpus:

NCPUs Used: 48      
CPU Time Used: 12:00:52
Memory Used: 371.57GB
Walltime Used: 12:01:22
JobFS used: 16.91GB 

The .dump file is 17GB and the original reads were HiFi, 67 GB. Is this normal? Could it take more than 12 hours or is there a bug. There was no error message and no progress in stderr, except:

Task: hetkmers
Kmers and coverages loaded.

Pipeline:

kmc -k21 -t48 -m256 -ci1 -cs10000 -fa $reads kmcdb tmp

kmc_tools transform kmcdb histogram kmcdb_k21.hist -cx10000

$(smudgeplot.py cutoff kmcdb_k21.hist L)
$(smudgeplot.py cutoff kmcdb_k21.hist U)

echo 'limits' $L $U

kmc_tools -t48 transform kmcdb -ci"$L" -cx"$U" dump -s kmcdb_L"$L"_U"$U".dump

smudgeplot.py hetkmers -o kmcdb_L"$L"_U"$U" < kmcdb_L"$L"_U"$U".dump

smudgeplot.py plot -o damp kmcdb_L"$L"_U"$U"_coverages.tsv`
@tallnuttrbgv tallnuttrbgv added the potential_problems for potential problems given different scenarios (How does XXX infulence sumdgeplot?) label Feb 1, 2024
@tallnuttrbgv
Copy link
Author

My mistake, no L=, U=

@tallnuttrbgv
Copy link
Author

I had L and U set anyway - so it was no the problem, it seems to be the same as previous issues - taking too long to run. Has this been solved yet? Thanks.

@KamilSJaron KamilSJaron added wontfix This will not be worked on 0.2.5 Double-hung Smudgeplot done with the 0.2.5 Double-hung with curtains version and removed potential_problems for potential problems given different scenarios (How does XXX infulence sumdgeplot?) labels Feb 8, 2024
@KamilSJaron
Copy link
Owner

Hi,

this:
#137 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.2.5 Double-hung Smudgeplot done with the 0.2.5 Double-hung with curtains version wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants