Some stupid programs try to create caches or config files in $HOME; when tasks are launched in containers that's not a problem because $HOME is set to the task's work directory. But for other tasks, we might as well do the same thing.
The setting should be done just before the actual scientific script is executed, so that HOME is still the normal home when the tool config prologues are executed (in case the admin uses $HOME during custom initialization commands).
Some stupid programs try to create caches or config files in $HOME; when tasks are launched in containers that's not a problem because $HOME is set to the task's work directory. But for other tasks, we might as well do the same thing.
The setting should be done just before the actual scientific script is executed, so that HOME is still the normal home when the tool config prologues are executed (in case the admin uses $HOME during custom initialization commands).