Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-341

DAX API improvements for 3.1

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: master, 3.1
    • Fix Version/s: master, 3.1
    • Labels:
      None

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              gmehta Gaurang Mehta (Inactive)
              Reporter:
              vahi Karan Vahi
            • Watchers:
              4 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours
                2h