Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Most workflow/job related requests are sent via AMP UI (or REST endpoints), upon which AMP generates corresponding REST request to Galaxy endpoints and return the response (sometimes filtered or normalized) to AMP UI. Unless specially noted, below requests are all sent to AMP server, but workflow/job related IDs such as workflowId etc refer to those existing in Galaxy.

Workflow

  • List all workflows: GET /workflows
  • Show details of a particular workflow: GET /workflows/{workflowId}

Job

  • Create an AMP job (i.e. submit a Galaxy workflow against an AMP primaryfile):
    • POST /jobs?workflowId={workflowId}&primaryfileId={primaryfileId}&parameters={parameters}
    • Note: 

      • parameters refers to the parameters for each Galaxy workflow step,

      • It's a map in the following format { stepId: { paramName: paramValue } }

      • stepId is the ID returned in workflow details inputs field.
      • paramName and paramValue are defined as part of the configuration of the tool used in that step (refer to the param name and value fields in the tool xml config file). Their values shall also be available in workflow details.
    • Examples
      • Execute workflow #0a248a1f62a0cc04 on primaryfile #4 with empty parameters (i.e. (using the default): POST https://localhost:8200/jobs?workflowId=0a248a1f62a0cc04&primaryfileId=4&parameters={}
      • Execute same workflow on same primaryfile as above but setting Sample Size of the first step (in this case, this step uses the Audio Extraction tool) to 24 Bits per Sample: same request as above but with parameters={ "0": {"samplesize": "pcm_s24le"} }


  • No labels