hershic / cs231n

Stanford CS231N
0 stars 0 forks source link

Rename files; directory cleanups #19

Closed hershal closed 7 years ago

hershal commented 7 years ago

These files are named incredibly stupidly and take way too long to type out. The class names should be the only long-ish names, so that they are distinguished clearly in code. The filenames, however, need not be so long.

E.g. this

classifiers
├── __init__.py
├── __pycache__
├── classifier_softmax.py
├── k_nearest_neighbor.py
├── linear_classifier.py
├── linear_svm.py
├── neural_net.py
└── test
    ├── __pycache__
    ├── test_classifier_softmax.py
    ├── test_k_nearest_neighbor.py
    └── test_linear_svm.py

could be simplified to

classifiers
├── __init__.py
├── __pycache__
├── softmax.py
├── knn.py
├── svm.py
└── test
    ├── __pycache__
    ├── softmax.py
    ├── knn.py
    └── svm.py
hershal commented 7 years ago

Also we should remove all dangling files which are not used anywhere.

EricCrosson commented 7 years ago

Do you have a classy way to detect these dangers?

EricCrosson commented 7 years ago

Weird, this didn't close from your comment, even though it looks like it would have in a commit :confused:

hershal commented 7 years ago

Good question. Maybe a static analysis tool would do this? pyreverse comes to mind because it generates a graph of python modules, but I'm not sure this would work properly since our entry point is currently through the tests...