-
Notifications
You must be signed in to change notification settings - Fork 11
03_Directory Structure and Tests
After Gym downloads, we recommend you make a directory structure that mirrors below, entirely separate from the src directory contains the Gym source code.
Trust us, put it somewhere that is entirely separate from the src directory contains the Gym source code.
A config
folder will store *.json
config files, which determine how the dataset is made and the model is trained. The the images
and labels
folders contain jpg
format images and greyscale label images respectively. The weights
folder holds *.h5
files - the weights and biases for your trained tensorflow model. The holdOutSet
folder is for jpg
format images and is optional. The weights
, npzForModel
, and modelOut
directories should be left empty - they will be populated with files by running Gym programs, as explained below.
/Users/Someone/my_segmentation_gym_datasets
│ ├── config
│ | └── *.json
│ ├── capehatteras_data
| | ├── fromDoodler
| | | ├──images
| │ | └── *.jpg
│ | | └──labels
| │ | └── *.jpg
| | ├──npzForModel
| │ └── *.npz
│ | └──toPredict
| │ └── *.jpg
│ └── modelOut
│ └── *.png
│ └── weights
│ └── *.h5
After datasets have been made, model-ready data files in npz
format are now populated in the npzForModel
.
/Users/Someone/my_segmentation_Gym_datasets
│ ├── config
│ | └── *.json
| ├──images
│ | └── *.jpg
│ |──labels
│ | └── *.jpg
| |──npzForModel
│ | └── *.npz
│ |──holdOutSet
│ | └── *.jpg
│ ├── modelOut
│ └── weights
After model training, the weights
folder is populated with model files and modelOut
contains example model predictions, model training curves, and other handy figures in png
format.
/Users/Someone/my_segmentation_Gym_datasets
│ ├── config
│ | └── *.json
| ├──images
│ | └── *.jpg
│ |──labels
│ | └── *.jpg
| |──npzForModel
│ | └── *.npz
│ |──holdOutSet
│ | └── *.jpg
│ ├── modelOut
│ | └── *.png
│ └── weights
│ └── *.h5