Closed andre-merzky closed 9 years ago
Yes, this transfer is done using directives : https://github.com/radical-cybertools/ExTASY/blob/master/src/radical/ensemblemd/extasy/bin/Preprocessor/Amber/preprocessor.py#L40-L44.
Isn't the CREATE_PARENTS flag the default behaviour ?
Just noticed that this is a similar error as I noticed today and explained in Issue #150
I think this should be fixed in devel, could you try again please?
Thanks for this but the same errors persisted for the CoCo / amber workflow on ARCHER even after reinstalling a fresh environment using the devel branch for the ExTASY installation.
[ExTASY-tools] ardita@poirot 248% python -c 'import radical.ensemblemd.extasy as extasy; print extasy.version'
0.1.3.1-beta-11-gd083439
The radical folder in stampede, public now, can be accessed at /work/02998/ardi/radical.pilot.sandbox/pilot-55144fdcf8cdba2501d24e69
The extasy log can be found at: https://gist.github.com/ashkurti/b4518eabd1a034788baa
I was able to reproduce this error. I get this error when I install RP from pip. But when I install RP from the master branch, it works fine and the parent folder(s) are created. Could you confirm as to which Radical Pilot you used ?
I admit I used the pip install before, but I have tried this morning (installing radical pilot from the master branch of its repository) at least twice and I still do get problems. I believe it is a different error now (See https://gist.github.com/ashkurti/f874e3c1b175203eec80#file-gistfile1-txt-L2189).
The log can be found at https://gist.github.com/ashkurti/f874e3c1b175203eec80 whereas the radical.pilot folder can be publicly accessed in stampede at /work/02998/ardi/radical.pilot.sandbox/pilot-55153a9cf8cdba61f60b09ce
Master indeed contains a couple of commits which have been done as small bug fixes. https://github.com/radical-cybertools/radical.pilot/commit/2ae27f8e4cff2759ca84db4ed447f529c1b2c615 is a commit which is in master, but not the released version, and looks like a good explanation for the problem. I would not mind doing a quick release of RP from master at that stage, if the EnMD folx would like to have that in pypi.
Scroll down on https://github.com/radical-cybertools/radical.pilot/compare/v0.23...master to see a full diff of master and last release.
Hi all, do we have a solution for this ticket?
For the sake of beta-testing - would it be feasible to release a new version of RP from master?
Yes, this would be the proposal. If you'd agree, I can do this today. Please give master a quick try (you need to do your testing anyway ;)? See the diff above, and check if that looks ok to you. If all is fine, I can push that to pypi today.
Ole, Vivek -- any feedback of we can/should push RP master to pypi? I rather not do that before you explicitly ok it... thanks!
I'm testing with the RP 0.24 release right now -- so far so good ;-)
This ticket was handled via email communications so I guess this ticket can be closed.
The relevant portion of the log reads:
Note that
penta.crd
has already been staged into[pilot_sandbox]/staging_area/penta.crd
at this point -- I am not sure why another attempt at staging occurs? Also, w/o looking at the code, could it be that theCREATE_PARENTS
flag on the RP staging directive is missing (if that directive is used, dunno)?