I’ve used the last version that you previously mentioned.
Reading the “read me” in zip file I saw this: maybe this is the point?
All the best
Stefano
I’ve used the last version that you previously mentioned.
Reading the “read me” in zip file I saw this: maybe this is the point?
All the best
Stefano
i’m not sure why you are having problems. i just downloaded the files from the ccx website and they work for me. i have these environment variables set:
MKL_INTERFACE_LAYER=LP64
MKL_THREADING_LAYER=INTEL
OMP_NUM_THREADS=(Set to desired number of cores)
OPENBLAS_NUM_THREADS=1
PASTIX_MIXED_PRECISION=1
Finally I solved it with PARDISO!
I set your Environmental Variables and now PARDISO with ccx_dynamic (off course) solve my analysis!
However now if I try to solve with PASTIX, the program automatically recall PARDISO solver yet.
Then if I use ccx_dynamic, PARDISO will be used, while if I use ccx_static he give me the previous error message (PARDISO not linked).
Many thanks for the patience.
All the best,
S.Milani
that’s correct on ccx_static.exe. it won’t run pardiso. only the ccx_dynamic.exe file will.
to switch between compilers you need to reference the ccx manual. in the inp file i provided, look for the following line near the bottom of the file:
*STATIC,SOLVER=PARDISO
you can either remove the SOLVER= option (that should default to PASTIX) or you can explicitly call one of three solvers:
*STATIC
*STATIC,SOLVER=PASTIX
*STATIC,SOLVER=PARDISO
*STATIC,SOLVER=SPOOLES
unfortunately, there doesn’t appear to be a global switch for solver type. you have to add it to each analysis you run.
also, i did many benchmarks of ccx_static.exe and ccx_dynamic.exe. the ccx_dynamic.exe file ran slightly faster most of the time. especially if you don’t have the following specified:
OPENBLAS_NUM_THREADS=1
PASTIX_MIXED_PRECISION=1
so i would just run ccx_dynamic.exe.