Replies: 1 comment 2 replies
-
I suggest to use the |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi neks,
I am new to nekRS. I recently installed nekRS on TACC's Frontera using the intel mpi compiler as described in the CMakeOutput.log file:
C compiler : /opt/intel/oneapi/mpi/2021.9.0/bin/mpicc
C++ compiler : /opt/intel/oneapi/mpi/2021.9.0/bin/mpicxx
Fortran compiler : /opt/intel/oneapi/mpi/2021.9.0/bin/mpif77
The Fortran compiler identification is IntelLLVM.
I have run into some issues when using NekRS on Frontera, and I try to explain the problem as clearly as I understand it.
=========== nrspre and nrsmpi ===================
After successful install, I try to run turbChannel from one of the examples. I replaced 'mpirun' in the nrspre and nrsmpi script in ~/.local/nekrs/bin to the following ( mpirun is not recommended on TACC ):
#For Frontera only, nrspre script:
ibrun -np 1 $NEKRS_HOME/bin/nekrs --setup $1 --build-only $2
#Frontera only, nrsmpi script:$1 $ {@:3}
ibrun -np $2 $NEKRS_HOME/bin/nekrs --setup
It would be great if I could have NekRS generate an executable file(.x) as in nek5000. However, nrspre does not work and throws out an error.
=================== Using nrsmpi + OCCA information ===================
For turbChannel examples, I run the following command inside a bash slurm script:
nrsmpi turbChannel 1
Using nrsmpi gives success when using one/two tasks yields successful run (serial backend). But increasing the no. of mpitasks gives a Segmentaion fault error similar to above. I find that the OCCA backend may be the problem, since the run crashes after printing out 'Initializng device'.
There are 3 modes to OCCA available on Frontera($ occa mode). I have tried to manually set the OCCA backend in the par file for each run:
This is the output of $occa env:
Basic:
- OCCA_DIR : [NOT SET]
- OCCA_CACHE_DIR : [NOT SET]
- OCCA_VERBOSE : [NOT SET]
- OCCA_UNSAFE : 0
Makefile:
- CXX : [NOT SET]
- CXXFLAGS : [NOT SET]
- CC : [NOT SET]
- CFLAGS : [NOT SET]
- FC : [NOT SET]
- FCFLAGS : [NOT SET]
- LDFLAGS : [NOT SET]
Backend Support:
- OCCA_OPENMP_ENABLED : 1
- OCCA_CUDA_ENABLED : 0
- OCCA_HIP_ENABLED : 0
- OCCA_OPENCL_ENABLED : 0
- OCCA_DPCPP_ENABLED : 1
- OCCA_METAL_ENABLED : 0
Run-Time Options:
- OCCA_CXX : [NOT SET]
- OCCA_CXXFLAGS : [NOT SET]
- OCCA_CC : [NOT SET]
- OCCA_CFLAGS : [NOT SET]
- OCCA_LDFLAGS : [NOT SET]
- OCCA_COMPILER_SHARED_FLAGS : [NOT SET]
- OCCA_INCLUDE_PATH : [NOT SET]
- OCCA_LIBRARY_PATH : [NOT SET]
- OCCA_KERNEL_PATH : [NOT SET]
- OCCA_OPENCL_COMPILER_FLAGS : [NOT SET]
- OCCA_DPCPP_COMPILER : [NOT SET]
- OCCA_DPCPP_COMPILER_FLAGS : [NOT SET]
- OCCA_CUDA_COMPILER : [NOT SET]
- OCCA_CUDA_COMPILER_FLAGS : [NOT SET]
- OCCA_HIP_COMPILER : [NOT SET]
- OCCA_HIP_COMPILER_FLAGS : [NOT SET]
This is the output of $occa info :
==============================================
This problem persists when running other examples as well. I read in one of the discussion pages (#517) that LLVM is not presently supported. Is this the problem here too?
Beta Was this translation helpful? Give feedback.
All reactions