You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user can change this default value by setting an enviroment variable to the desired value.
The name of this variable is always constructed in the following way:
ELPA_DEFAULT_tunable_parameter_name=value
(By the way environment is misspelled as enviroment.)
However, this doesn't seem to work well with the nvidia-gpu, amd-gup, and intel-gpu variables. Various online resources mentioned that it's not allowed to have a dash in the name of an environment variable. For example see this post on stackoverflow.
So to work this around in bash, something like
env 'ELPA_DEFAULT_nvidia-gpu=1' ./test_elpa.x ...
is needed, instead of the more familar way, export ELPA_DEFAULT_nvidia-gpu=1.
It would be great if this could be clarified in the USERS_GUIDE, or even better, createnvidia_gpu, amd_gpu, and intel_gpu as aliases to the existing ones.
The text was updated successfully, but these errors were encountered:
We have updated the documentation in ELPA 2022.11.001.rc2. Concerning the aliases with an "_" instead of "-", we will introduce this in the first release of 2023. It is to short time to accept this change still in the ELPA 2022.11.001. release.
According to the USERS_GUIDE:
(By the way environment is misspelled as enviroment.)
However, this doesn't seem to work well with the
nvidia-gpu
,amd-gup
, andintel-gpu
variables. Various online resources mentioned that it's not allowed to have a dash in the name of an environment variable. For example see this post on stackoverflow.So to work this around in bash, something like
is needed, instead of the more familar way,
export ELPA_DEFAULT_nvidia-gpu=1
.It would be great if this could be clarified in the USERS_GUIDE, or even better, create
nvidia_gpu
,amd_gpu
, andintel_gpu
as aliases to the existing ones.The text was updated successfully, but these errors were encountered: