Page 2 of 2

Re: Installation on cluster

Posted: Wed Sep 23, 2020 11:04 am
by Puneeth
Hello,

The admin recompiled Code-Saturne as per your recommendations and this has fixed the issue!

Thank you very much!

Sincerely,

Puneeth

Re: Installation on cluster

Posted: Wed Sep 23, 2020 2:53 pm
by Puneeth
Hello,

After reinstaling CSv5.1.6, there is a new error relating to the srun command (SLURM Workload Manager).
The slurm-jobid.out file contents are as follows:
Code_Saturne
************
Version: 5.1
Path: /gpfslocalsup/pub/code-saturne/5.1.6
Result directory:
/gpfs7kw/linkhome/rech/genlma01/upz85tg/CH590_A1_alpha/CASE1/RESU/20200923-1111
****************************************
Compiling user subroutines and linking
****************************************
****************************
Preparing calculation data
****************************
Parallel Code_Saturne on 160 processes.
***************************
Preprocessing calculation
***************************
**********************
Starting calculation
**********************
srun: error: Invalid numeric value "40.0" for ntasks-per-node.
****************************
Saving calculation results
****************************
solver script exited with status 1.
Error running the calculation.
Check Code_Saturne log (listing) and error* files for details.
Error in calculation stage.

The ntasks-per-node should ideally be an integer and not a floating point value as seen here.
There are no listing or error files created.

Could you please guide me on how to fix this?

Thanks and regards,

Puneeth

Re: Installation on cluster

Posted: Thu Sep 24, 2020 9:05 am
by Puneeth
Hello,

Found the bug that generated the error relating to srun.
It is from the function to compute n_procs_per_node within the resource_info class at line 1086 in file cs_exec_environment.py. The division operation is not floored (using //) and instead uses "/" which returns a floating point value in python 3.x.

Thanks and regards,

Puneeth

Re: Installation on cluster

Posted: Fri Sep 25, 2020 2:57 pm
by Yvan Fournier
Hello,

Thanks for the feedback. This was fixed November 2018 for the v6.0 and master branches, but was not backported to v5.0.

I'll fix it in the next v5.0 release (but there might be other Python 3 bugs in the GUI), which will be maintained until spring of 2021 (until v7.0 is released).

Best regards,

Yvan