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

Error : sort_index(): detected NaN #31

Open
zz-yun opened this issue Apr 7, 2024 · 2 comments
Open

Error : sort_index(): detected NaN #31

zz-yun opened this issue Apr 7, 2024 · 2 comments

Comments

@zz-yun
Copy link

zz-yun commented Apr 7, 2024

Dear
I have 290 samples to impute and i run QUILT in chunks.
QUILT.R --outputdir=quilt_output_chunks --chr=chr03 --regionStart=12800001 --regionEnd=13800001 --buffer=200000 --bamlist=bamlist_1.txt --reference_haplotype_file=chr03.hap.gz --reference_legend_file=chr03.legend.gz --nGen=100 --nCores=40

I encountered an error:

  • "Error : sort_index(): detected NaN
  • In mclapply(1:length(sampleRanges), mc.cores = nCores, function(iCore) { :
  • scheduled cores 7, 8 encountered errors in user code, all values of the jobs will be affected
  • Execution halted".

When I tried to run them using multiple cores(40 cores). I attempted to allocate more memory(200Gb), and I found that ran successfully.

But Similar commands and the same solutions have failed. The command:
QUILT.R --outputdir=quilt_output_chunks --chr=chr03 --regionStart=13600001 --regionEnd=14600001 --buffer=200000 --bamlist=bamlist_1.txt --reference_haplotype_file=chr03.hap.gz --reference_legend_file=chr03.legend.gz --nGen=100 --nCores=40

The error always is

  • "Error : sort_index(): detected NaN".

Therefore, I tried setting the core number to 1 for the tasks, but encountered the same error. What could be the issue?

Thank you.
Any feedback is welcome.

@rwdavies
Copy link
Owner

Hi,

I'm slightly confused. QUILT in general will throw errors that are sometimes confusing when it runs out of memory.

Each sample in QUILT is processed independently. Can you try running fewer samples at a time, using fewer cores? In an extreme case, run small sets of individuals with 1 core each, then merge back together.

Thanks,
Robbie

@rwdavies
Copy link
Owner

Please let me know if this keeps happening when using a number of cores / RAM where running out of memory isn't reasonably likely to occur.

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