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
Hello @Jordatious@Kitchi , I have already managed to adapt the pipeline to our infrastructure and in general to any other following the PR, but after several tests, I see that there is a problem in the concatenation phase:
Inside the submission file, this part that is executed:
cat logs/concat-2599.err
/var/spool/slurmd/job02599/slurm_script: line 15: module: command not found
Traceback (most recent call last):
File "/mnt/slurm-jobs/pipelines/processMeerKAT/aux_scripts/concat.py", line 173, in <module>
bookkeeping.run_script(main,logfile)
File "/mnt/slurm-jobs/pipelines/processMeerKAT/bookkeeping.py", line 330, in run_script
args = config_parser.parse_args()
File "/mnt/slurm-jobs/pipelines/processMeerKAT/config_parser.py", line 16, in parse_args
parser.add_argument('-C','--config', default=processMeerKAT.CONFIG, required=False, help='Name of the input config file')
AttributeError: module 'processMeerKAT' has no attribute 'CONFIG'
srun: error: espsrc-slurm-01: task 0: Exited with exit code 1
It looks like an issue with paths or access to the config file. The previous steps for each SPW worked well without errors.
Any ideas?
Regards,
Manu.
The text was updated successfully, but these errors were encountered:
I think it should be referring to this CONFIG variable here. I'm not sure why it wouldn't. Check your paths and imports to see if CONFIG can be read in, otherwise you could probably get away with changing this line to a file path with the default name.
Hello @Jordatious @Kitchi , I have already managed to adapt the pipeline to our infrastructure and in general to any other following the PR, but after several tests, I see that there is a problem in the concatenation phase:
Inside the submission file, this part that is executed:
When checking for errors with
findErrors.sh
, I see the following:AllSPW
part:Checking the log specifically I see:
It looks like an issue with paths or access to the config file. The previous steps for each SPW worked well without errors.
Any ideas?
Regards,
Manu.
The text was updated successfully, but these errors were encountered: