Staging area does not get created
Issue #4
resolved
I am working on the new gromacs coco workflows.
While testing them out, I see there is a problem with the staging area that does not get created.
Would you have any suggestions on this? Which code portion is the responsible one for the staging area? I think, I have linked the inputs/outputs correctly as what I did when I produced the new coam workflows.
If anybody wanted to have a look on ARCHER the folder is at /work/e290/e290/ardi/radical.pilot.sandbox/rp.session.moriarty.pharm.nottingham.ac.uk.ardita.016875.0002-pilot.0000/
Thanks for any suggestions!!
Comments (2)
-
-
reporter - changed status to resolved
Ok, this is sorted now!
- Log in to comment
The staging area gets created when a file is staged to the pilot. The respective line of code in RP is here:
https://github.com/radical-cybertools/radical.pilot/blob/devel/src/radical/pilot/compute_pilot.py#L528
(see also line 523 where the dir name is constructed). As to where the staging action is triggered in Extasy (or not triggered in this case) I can't say much -- Vivek may be able to answer that part.