neper in HPC cluster

[anujyadav0693]

Dear Romain,
does neper run across compute nodes in HPC cluster. when I try to run neper on 120 cores (slurm_ntasks shown below), neper runs only 40 threads in the output file.

SLURM_JOB_PARTITION = medium
SLURM_TASK_PID = 234530
SLURM_SUBMIT_DIR = /scratch/21ae91r02/neper_model
SLURM_CPUS_ON_NODE = 40
**SLURM_NTASKS = 120**
SLURM_TASK_PID = 234530
==========================================
/scratch/21ae91r02/neper_bin/neper-main/src/build/neper

========================    N   e   p   e   r    =======================
Info   : A software package for polycrystal generation and meshing.
Info   : Version 4.6.1-1
Info   : Built with: gsl|muparser|opengjk|openmp|nlopt|libscotch (full)
Info   : **Running on 40 threads.**
Info   : <https://neper.info>
Info   : Copyright (C) 2003-2022, and GNU GPL'd, by Romain Quey.
Info   : No initialization file found (`/home/21ae91r02/.neperrc').
Info   : ---------------------------------------------------------------
Info   : MODULE  -T loaded with arguments:
Info   : [ini file] (none)
Info   : [com line] -n from_morpho -morpho
         diameq:lognormal(0.0001,0.00001),1-sphericity:lognormal(0.145,0.03)
         -dim 2 -domain square(0.04,0.01) -o new -format geo,ori,tess
         -statcell diameq -oridescriptor euler-bunge -ori
         fiber(0,0,1,0,0,1)
Info   : ---------------------------------------------------------------

thank you.

[rquey]

No, it doesn't. Neper is multithreaded (using openMP), not parallelized. So, the best you can do is run it on 1 compute node / SLURM_CPUS_ON_NODE threads... If you enforce to run it on several compute nodes, I think what happens is that each compute node will run its own instance of Neper (several times the same computation).

[anujyadav0693]

Thankyou for your response sir.

…

On Mon, 12 Jun, 2023, 12:14 pm Romain Quey, ***@***.***> wrote: Closed #703 <#703> as resolved. — Reply to this email directly, view it on GitHub <#703>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2GG52BD3YZR3KDGRHGAWETXK23E7ANCNFSM6AAAAAAZBWAP5Q> . You are receiving this because you authored the thread.Message ID: ***@***.***>