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/20043/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "ob_id": 20043,
    "uuid": "32eff53af32442d1a347da2cc45bb9db",
    "title": "HadISD station data processing performed at the Met Office Hadley Centre",
    "abstract": "The HadISD station data were produced by the Met Office Hadley Centre. Individual station data within the ISD were selected selected on the basis of their length of record and reporting frequency.  A merging algorithm using their location, elevation and station name identified candidates suitable to combine together. All stations were passed through a suite of automated quality control tests designed to remove bad data whilst keeping the extremes. None of the ISD flags were used in this process. The QC tests focussed on the temperature, dewpoint temperature and sea-level pressure variables, although some were applied to the wind speed and direction and cloud data. The data files also contain other variables which were pulled through from the raw ISD record, but have had no QC applied (e.g. cloud base and precipitation depth). \r\n\r\nNotes:\r\n1. These data have not yet been homogenised and so trend fitting should be undertaken with caution. The homogeneity has been assessed and results are available from the Met Office Hadley Centre HadISD website: http://www.metoffice.gov.uk/hadobs/hadisd/. \r\n2. A long-standing bug (affecting versions v2.0.2_2017p through to v3.3.0.2022f), was discovered in autumn 2023 whereby the neighbour checks (and associated [un]flagging for some other tests) were not being implemented. This was corrected for the later version v3.4.0.2023f to HadISD. For more details see the posts on the HadISD blog: https://hadisd.blogspot.com/2023/10/bug-in-buddy-checks.html & https://hadisd.blogspot.com/2024/01/hadisd-v3402023f-future-look.html(v2.0.2_2017p through to v3.3.0.2022f), and as noted this has been fixed for v3.4.02023f.\r\n\r\n\r\nFor further details see: \r\nDunn, R. J. H., et al., (2016), Expanding HadISD: quality-controlled, sub-daily station data from 1931, Geoscientific Instrumentation, Methods and Data Systems, and Dunn, R. J. H., et al. (2012), HadISD: A Quality Controlled global synoptic report database for selected variables at long-term stations\r\nfrom 1973-2011, Climate of the Past.\r\nDunn, R. J. H., et al. (2014), Pairwise Homogeneity Assessment of HadISD, Climate of the Past, 10, 1501-1522 (see Docs for links to publications).",
    "keywords": "HadISD",
    "inputDescription": null,
    "outputDescription": null,
    "softwareReference": null,
    "identifier_set": []
}