A comprehensive collection of solutions and best practices for a variety of issues on the RedBrick AI platform.
Step 1: Navigate to RedBrick
Step 2: Open your browser’s Developer Tools
Step 3: Open the Application tab
Step 4: Find and clear the cached site data for RedBrick AI
Step 1: Check your entire inbox, including spam
Step 2: Wait a moment
Step 3: Reach out to us
Step 1: Check your entire inbox, including spam
Step 2: Wait a moment
Step 3: Reach out to us
Q: I ran put_tasks(existing_labels=True) while attempting to upload labels to RedBrick, but I can’t see anything in the Editor! My Tasks are empty, i.e. I can’t see the labels I wanted to upload.
A: The put_tasks() function is used for two operations:
existing_labels=True
parameter will simply submit the Tasks in their current state on the RedBrick platform, preventing you from uploading any labels you may supply in the upload JSON.
If you wish to upload labels that you are supplying in your current code to existing RedBrick Tasks, you should be using existinglabels=False
Q: Why is there a “binaryMask": True value in my export tasks.json file? I didn’t use the binary_mask parameter when doing the export.
Related Q: Why does my segmentation export have a long list of instance-1.nii.gz
, instance-2.nii.gz
, etc., instead of the usual single NIfTI file?
A: RedBrick AI will automatically export segmentations that overlap as a binary mask, generating one instance per class.
Compare the two JSON blocks below:
Code Block 1: a standard (i.e. non-binary mask) export, containing a single NIfTI file.
Each NIfTI file contains all of the individual segmentations associated with a particular Series as defined by the segmentMap
, which can be found in the tasks.json
file.
metaData
has a capital “D”!--clear-cache
flag.
Step 1: Log into RedBrick AI and open the Task
Step 2: Use the Version Explorer to set the Target Label Set to the latest version
Step 3: Export