We are using RFAA on a shared cluster and would like to use a shared runner script and RFAA installation to launch RFAA jobs. The issue that we are facing now is that since each run creates a log folder per day/run, other users trying to run RFAA and therefore save log files in the same folder are faced with "Permission denied" issues. Where can this log folder path be modified? Would it be possible to add the log folder path as a parameter to the yaml file so users have more control over where these log files are saved and if others are using RFAA on a shared cluster, the RFAA source code folder doesn't get flooded with the log files from all RFAA runs.
We are using RFAA on a shared cluster and would like to use a shared runner script and RFAA installation to launch RFAA jobs. The issue that we are facing now is that since each run creates a log folder per day/run, other users trying to run RFAA and therefore save log files in the same folder are faced with "Permission denied" issues. Where can this log folder path be modified? Would it be possible to add the log folder path as a parameter to the yaml file so users have more control over where these log files are saved and if others are using RFAA on a shared cluster, the RFAA source code folder doesn't get flooded with the log files from all RFAA runs.