Last updated
Last updated
You can make use of RedBrick AI's Python SDK to export your annotations using a Python script.
Within the Python SDK, annotations are exported in two ways:
The export_tasks function returns a Python object containing meta-data information and any vector annotations (measurements, landmarks, etc.). Please see the .
By default, segmentation data is written to your disk in NIfTI format. Segmentation data can also be exported in PNG or RT Struct by manipulating the parameters of the export_tasks function. Please view the detailed .
If you're attempting a one-time export or don't have intensive requirements for your export, the also provides a simple and optimized workflow for exporting a Project's annotations.
RedBrick AI exports annotations in a JSON structure, accompanied by for segmentations. All data will be exported within a folder named after your project_id, with the following structure:
The above structure is for a standard export (i.e. not semantic, not binary mask, etc.) and assumes no .
With a new Project object created, you can export your Project's Tasks in various ways. Please see some common examples below.
The export_tasks() function exports segmentation files for all Ground Truth Tasks by default. To export All Tasks, set the only_ground_truth parameter to False.
You can export only the Tasks in Ground Truth, i.e., Tasks that have successfully made it through all Label and Review Stages.
Export selected Tasks by specifying Task IDs.
An audit trail can be useful for regulators interested in your quality control processes, as well as for managing your internal QA processes.
If you'd like to generate an audit trail for all Tasks (not only those in the Ground Truth Stage), be sure to include the only_ground_truth=False parameter.
Retrieve an audit trail for all Ground Truth Tasks. Please note that by default, get_task_events only returns audit information for Tasks in the Ground Truth Stage.
The returned object will contain data similar to the code snippet below, where each entry will represent a single Task (uniquely identified by taskId). The events array contains all key events/actions performed on the Task, with events[0] being the first event.
The segmentation directory will contain a single sub-directory for each task in your export. The sub-directories will be named after the task . A single task (depending on whether it was single series or multi-series) can have one or more segmentations.
The individual segmentation files will be in NIfTI-1 format and be . If no series name is provided on upload, RedBrick will assign a unique name. Corresponding meta-data ex. category names will be provided in .
As always, you should first perform the to create a Project object.
Please see a detailed reference for.
First, perform the to create a Project object.
The following is a non-exhaustive list of other available functionalities when using the . A full list of the capabilities of our Export class can be found .
Track labeler or reviewer time spent on a Task with ;
Fetch Task events from a specific timestamp to the present day using and the from_timestamp parameter;
Easily search for Tasks based on a wide variety of criteria using ;
Perform a semantic export (that exports a single file per category name) using ;
Configure s;
Upload a for ;