-
The debugging information and errors (computational units change their state to failed) are the following:
(ard)extasy-project@ip-10-243-91-117:/tmp/ExTASY$ RADICAL_PILOT_VERBOSE=info extasy --RPconfi…
-
Introduction, inaccurate as far as I can tell.
http://saga-project.github.io/BigJob/sphinxdoc/tutorial/part1.html
"This tutorial will explain how to run four different examples of BigJob on (1) your…
-
This was tried from the testing account: extasy-project@testing.saga-project.org
The debugging information and errors (computational units change their state to failed) are the following:
(ard)extas…
-
"..ensure that the good description/tutorial material from XSEDE'13 gets
assimilated into the main documentation (and we should do this in general, i.e., after a specific tutorial X, we should update/…
-
Currently, we need to inform users of the need to use their own redis server to run BigJob. We also need to come to a concensus on the easiest way for users to start a redis server to do the tutorials…
-
-
In the mpi branch, I see frequent hangs when running simple examples:
```
2014:06:06 00:27:56 27758 MainThread saga.saga.Session : [DEBUG ] adding context : {'Type' : 'SSH'}
2014:06:06 00:2…
-
Especially with BigJob deployment on XSEDE and the fact that we decided to move to Redis, it doesn't make too much sense to have the user explicitly define the URL every single time:
```
COORDINATION…
-
I get the following error:
[ExTASY-toolsOct1] ardita@poirot 151% extasy --RPconfig stampede.rcfg --Kconfig cocoamber.wcfg Session UID: 542c2d98f8cdba30bd6bf5a2
Pilot UID : 542c2d9bf8cdba30…
-
and other references that may be lurking
https://github.com/saga-project/tutorials/wiki/XSEDE-2013-BigJob-Tutorial