[CP2K-user] number of g-vectors for grid

Hans Pabst hf.... at gmail.com
Tue Apr 2 08:43:58 UTC 2019

It looks like the node count must a power-of-two or at least everything 
else between 128 and 256 nodes hits the assertion. If found this to be true 
down to CP2K 4.1 (I have not checked older releases yet).

Am Sonntag, 31. März 2019 20:57:29 UTC+2 schrieb Hans Pabst:
> For a given workload (LiHFX <https://www.cp2k.org/performance#lih-hfx>), 
> I was successfully running with 128 nodes (6144 cores). However, with more 
> nodes, CP2K 6.1 release as well as v7.0-dev terminates with a runtime 
> condition where the number of g-vectors of the PW-grid does not meet the 
> following criterion: CPASSERT(pw_grid%ngpts_cut_local == gpt), which is at 
> line #1608 in CP2K/master. I ran with all preferrable node-counts beyond 
> 128, but it always hits the assertion. I understand that one can 
> overdecompose a workload (or otherwise hit a condition that is simply not 
> possible for a given input). However, with LiHFX in particular, there are 
> results published that ran successfully on way more nodes/cores. Given the 
> latter, I wonder if I am trapped by some mistake. Do you have an advice on 
> how to best run this workload? I was already using preferrable rank/thread 
> combinations and of course relying on the hybrid binary (PSMP). Is there an 
> adjustment of LIBINT settings needed (-D__LIBINT_MAX_AM=7 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cp2k.org/archives/cp2k-user/attachments/20190402/c376cb23/attachment.htm>

More information about the CP2K-user mailing list