Branch Clean-up

[Simsso]

I think we've got more branches than needed. Maybe it's time to clean things up a bit.

No high priority, just opening the issue for now.

[ghost]

Hey @Simsso , I'll merge tiny-imagenet-classifier-branch into training-enablement-tools and delete tiny-imagenet-classifier-branch and reference-cnn-branch as it would have all commits and changes of those. Furthermore I would merge deployment-pipeline-discussion (having some architecture pictures) into training-enablement-tools. So I'll clean those up from my side.

[Simsso]

Deleting layerwise-perturbation-experiments and linear-combination-experiments becuase both have been merged into experiments.

[Simsso]

Now that we have closed #29 and #31, shall we put the tiny-imagenet-classifier folder into the experiments folder in order to be able to delete the three branches

• tiny-imagenet-classifier-resnet Updated 2 days ago by Simsso
• tiny-imagenet-classifier-inception Updated a day ago by FlorianPfisterer
• tiny-imagenet-classifier Updated a month ago by Simsso

I think it's a good habit not to delete any code permanently and not to have open branches which we'll never continue working on anyways. Opinions, @FlorianPfisterer @doktorgibson?
We'd have to add a nice README of course.

[FlorianPfisterer]

I agree we should keep the code but clean up the branches.
How would you merge our two branches (tiny-imagenet-classifier-resnet and tiny-imagenet-classifier-inception)? We have mostly worked in different files, but some of them are still different. Maybe create two subfolders of experiments - one for inception and one for resnet experiments? @Simsso

[ghost]

Since I have already merged tiny-imagenet-classifier-resnet into training-enablement-tools for development purpose, you are completely free to delete those branches and decide for the best in your opinion.