Create a computation specification
Changed onCreate a computation specification. The create request must contain all the input and output data-type IDs which are used to define the computation specification. These data-types must have previously been created. As an example, a computation specification could be defined as a specification for a compute which takes two pieces of input data and calculates a single piece of output data. The specification for this compute would take two input data-types and output a single output data-type. The order of the input and output data-type IDs provided in the creation of the computation specification is maintained in the created computation specification and may only be changed through performing PATCH operations on the computation specification.
Request
- Base URLhttps://api.delfi.slb.com/fdplan/evaluation/v1
- AuthAPI key in header Authorization and API key in header appkey
Headers
Data partition id.
Request body
Example request
{
"id": "slb:computation-specs:custom-computation-spec",
"name": "custom-computation-spec",
"description": "Description",
"inputDataTypeIds": [
"decline-curves",
"drilling-constraints",
"facility-constraints"
],
"outputDataTypeIds": [
"production-forecast"
],
"annotations": [
{
"address": {
"type": "DataTypeInput",
"computationIndex": 0,
"dataTypeIndex": 0
},
"key": "name",
"value": "Decline Curves",
"createdBy": "user@slb.com"
},
{
"address": {
"type": "DataTypeInput",
"computationIndex": 0,
"dataTypeIndex": 1
},
"key": "name",
"value": "Drilling Constraints",
"createdBy": "user@slb.com"
},
{
"address": {
"type": "DataTypeInput",
"computationIndex": 0,
"dataTypeIndex": 2
},
"key": "name",
"value": "Facility Constraints",
"createdBy": "user@slb.com"
},
{
"address": {
"type": "DataTypeOutput",
"computationIndex": 0,
"dataTypeIndex": 0
},
"key": "name",
"value": "Production Forecast",
"createdBy": "user@slb.com"
}
]
}Response
Computation specification created successfully.
Example response
{
"id": "01DV2RPKYS5NYBAR6TNMJ8TNT8",
"name": "custom-computation-spec",
"version": 1,
"latest": true,
"archived": false,
"description": "Description",
"createdBy": "user@slb.com",
"createdAt": "2020-01-01T00:00:00.000Z",
"inputDataTypeIds": [
{
"id": "decline-curves",
"version": 1
},
{
"id": "drilling-constraints",
"version": 1
},
{
"id": "facility-constraints",
"version": 1
}
],
"outputDataTypeIds": [
{
"id": "production-forecast",
"version": 1
}
],
"annotations": [
{
"address": {
"type": "DataTypeInput",
"computationIndex": 0,
"dataTypeIndex": 0
},
"key": "name",
"value": "Decline Curves",
"createdBy": "user@slb.com"
},
{
"address": {
"type": "DataTypeInput",
"computationIndex": 0,
"dataTypeIndex": 1
},
"key": "name",
"value": "Drilling Constraints",
"createdBy": "user@slb.com"
},
{
"address": {
"type": "DataTypeInput",
"computationIndex": 0,
"dataTypeIndex": 2
},
"key": "name",
"value": "Facility Constraints",
"createdBy": "user@slb.com"
},
{
"address": {
"type": "DataTypeOutput",
"computationIndex": 0,
"dataTypeIndex": 0
},
"key": "name",
"value": "Production Forecast",
"createdBy": "user@slb.com"
}
]
}Changes
- breaking
added the new required
headerrequest parameterslb-partition-id - warning
deleted the
headerrequest parameterslb-data-partition-id - warning
added the new
Workflowenum value to the////response property for the response status - info
added the new
Workflowenum value to the request property////
- breaking