Skip to content

Commit d4e2d9d

Browse files
committed
Enhance README with dataset ID support for subtasks
- Added example request for creating a subtask, including the new optional `dataset_id` field. - Clarified that `dataset_id` can be specified during subtask creation and is fully supported throughout the subtask lifecycle. - Updated documentation to reflect the ability to configure datasets later using the `/data` endpoint.
1 parent 5074a37 commit d4e2d9d

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

README.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -191,6 +191,27 @@ GET /problemStatements/{problemStatementId}/tasks/{taskId}
191191
POST /problemStatements/{problemStatementId}/tasks/{taskId}/subtasks
192192
```
193193

194+
**Example Request:**
195+
196+
```json
197+
{
198+
"name": "Crop Yield Analysis Subtask",
199+
"dates": {
200+
"start_date": "2024-01-01T00:00:00Z",
201+
"end_date": "2024-12-31T23:59:59Z"
202+
},
203+
"driving_variables": ["nitrogen__average_of_net_mass_mineralization_rate"],
204+
"response_variables": ["crop__potential_transpiration_volume_flux"],
205+
"regionid": "texas",
206+
"dataset_id": "18400624-423c-42b5-ad56-6c73322584bd"
207+
}
208+
```
209+
210+
**Dataset ID Support:**
211+
- The `dataset_id` field is optional and allows you to associate a dataset with the subtask at creation time
212+
- Dataset IDs are fully supported throughout the subtask lifecycle
213+
- You can also configure datasets later using the `/data` endpoint for more detailed dataset specifications
214+
194215
**Add Models to Subtask**
195216

196217
```http

0 commit comments

Comments
 (0)