-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major
-
Affects Version/s: master, 3.1
-
Component/s: Workflow API Libraries
-
None
While moving the LIGO ihope pipeline to the new DAX Schema, Duncan encountered following issues with the python API.
I think they apply in general to all three API's
- internally executables handled as lists not as Sets
in his dax generator he was adding exectuable pfn's for the jobs. However, what this means is that same executable is repeated n times in generated DAX in the transformation catalog section
- python api does not allow for adding edges based on id's.
- also have a getJob function based on ID.
- escape function in python api?is it for all strings
1.
|
JAVA DAX API changes for 3.1 | Closed | Rajiv Mayani | |||||||||
2.
|
Python DAX API changes for 3.1 | Closed | Gideon Juve (Inactive) | |||||||||
3.
|
Perl DAX API changes for 3.1 | Closed | Jens Voeckler |
|