Index of GT slices

Anyway, here’s the magic table. Padding is NOT included. Indices are 1-based (Matlab style). Index 1 is always the most anterior slice , as usual.

Like I said: I did this manually (via visual inspection), and should be 100% reliable.

Use this for the reconstruction (to compute the index of the initial slice) and to transfer the labels from the hard-merged-manual.

Source: /cluster/vive/UW_photo_recon/recons/results_Henry/Results_hard/*/*_hard_manualLabel_merged.mgz

• 17-0333 - 20
• 18-0086 - 21
• 18-0444 - 18
• 18-0817 - 19
• 18-1045 - 20
• 18-1132 - 20
• 18-1196 - 18
• 18-1274 - 19
• 18-1327 - 19
• 18-1343 - 20
• 18-1470 - 17
• 18-1680 - 17
• 18-1690 - 21
• 18-1704 - 21
• 18-1705 - 19
• 18-1724 - 22
• 18-1754 - 18
• 18-1913 - 19
• 18-1930 - 18
• 18-2056 - 20
• 18-2128 - 20
• 18-2259 - 18
• 18-2260 - 20
• 19-0037 - 21
• 19-0100 - 19
• 19-0138 - 21
• 19-0148 - 22

The aforementioned manual indexing can also be verified by running make gt_slice_idx.

NOTE: The indices from python are smaller by a value of 1 (due to 0-indexing).