File Naming
When naming a file, keep three things in mind: the project name, the type of work the file contains, and the volume it belongs to. Spaces aren't allowed, so join the parts with underscores:
Project_Type_Volume_Any-other-relevant-info
For example, a synaptic annotation file for Vol. 30 in the Pinky project is named Pinky_Synapses_Vol.30. For projects without a settled naming protocol, add any other relevant information to the end of the name.
Duplicates, practice & experiments
When multiple copies of a file exist (experimenting without overwriting the output, or several people training on the same set), include the tracer's name and a word indicating practice or experiment — for example Pinky_Annotation_vol.202_Ben_Experiment. Save all practice/experiment sets and saved-state duplicates in the project's Archive folder, and clean up once the task is complete so each file lives in the right place.
Type abbreviations
| Type | Name |
|---|---|
| Raw EM | EM |
| Semantic Annotation | Seg |
| Synaptic Annotation | Synapses |
| Vesicles | Vesicles |
| Mitochondria | Mito |
| Semantic Labeling | Semantic Labeling |
| Blood Vessels | Blood Vessels |
Examples
| Type | Info | Name | Folder |
|---|---|---|---|
| Semantic Annotation | Pinky Volume 24, completed by Ben | Pinky_vol.24_seg_Ben | Cell_Segmentation |
| Synapses | AIBS Volume 19, stitched set | AIBS_vol.19_synapses_stitched | PSD/Synapses |
| Mitochondria | Allen Volume 06, Merlin practice | Allen_vol.06_Mito_MM_practice | Mitochondria |
| Vesicles | AIBS Volume 22 | AIBS_vol.22_vesicles | Vesicles/Vesicle Cloud |
Purpose
Establishes standard conventions for naming annotation files, exports, and datasets.
Scope
Applies to file naming across project workflows — annotation exports, dataset identifiers, and documentation.