Procedure Computation Instance – Django REST framework

Get a list of ProcedureComputation objects. ProcedureComputations have a 1:1 mapping with Observations.

### Available end points:

- `/ProcedureComputations/` - Will list all ProcedureComputations in the database
- `/ProcedureComputations.json` - Will return all ProcedureComputations in json format
- `/ProcedureComputations/<object_id>/` - Returns ProcedureComputations object with that id

### Available Methods:

- `GET`
- `HEAD`

### Available filters:

- `uuid`
- `title`
- `keywords`
- `abstract`

### How to use filters:

These filters can be used like django query filters using __ for related model relationships.

- `/computations/?uuid=d594d53df2612bbd89c2e0e770b5c1a0`
- `/computations/?title__startswith!=DETAILS NEEDED - COMPUTATION CREATED FOR SATELLITE COMPOSITE`
- `/computations/?abstract__contains=HadCM3 model`

GET /api/v2/computations/27582/?format=api

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "ob_id": 27582,
    "uuid": "932aaec12406492c8735db30ec3fa347",
    "title": "TempestExtremes computation for CMIP6 HighResMIP storm tracks",
    "abstract": "The storm tracking algorithm TempestExtremes (Ullrich and Zarzycki 2017; Zarzycki and Ullrich 2017) uses sea level pressure minima to find storm candidates. It then uses an upper level difference in geopotential height (or temperature) to determine if there is a warm core, and this together with other conditions are used to stitch the candidate points together into tracks. \r\n\r\nThe algorithm used for the storm-tracking is also described in the metadata of the track files and full details can be found in the linked documentation. \r\n\r\nThe storm tracks were calculated using the Lotus cluster at on the JASMIN compute facility at the Centre for Environmental Data Analysis (CEDA).",
    "keywords": "CMIP6, HighResMIP, TempestExtremes, tropical, cyclone, storm tracking",
    "inputDescription": null,
    "outputDescription": null,
    "softwareReference": null,
    "identifier_set": []
}