Decision Optimization output data definition | IBM Data Product Exchange

Output data definition

Last updated: Oct 09, 2024

Decision Optimization output data definition

When submitting your job you can define what output data you want and how you collect it (as either inline or referenced data).

For more information about output file types and names see Model input and output data file formats.

Some output data definition examples:

To collect solution.csv output as inline data:
```
"output_data": [{
     "id":"solution.csv"
}]
```
Regexp can be also used as an identifier. For example to collect all csv output files as inline data:
```
"output_data": [{
     "id":".*\\.csv"
}]
```
Similarly for reference data, to collect all csv files in COS/S3 in job specific folder, you can combine regexp and ${job_id} and ${ attachment_name } place holder
```
"output_data_references": [{
     "id":".*\\.csv",
     "type": "connection_asset",
     "connection": {
              "id" : <connection_guid>
     },
     "location": {
		"bucket": "XXXXXXXXX",
		"path": "${job_id}/${attachment_name}"					}
}]
```
For example, here if you have a job with identifier <XXXXXXXXX> to generate a solution.csv file, you will have in your COS/S3 bucket, a XXXXXXXXX / solution.csv file.

Generative AI search and answer

These answers are generated by a large language model in watsonx.ai based on content from the product documentation. Learn more