Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for convolutions #1

Open
antoinecarme opened this issue Feb 16, 2018 · 2 comments
Open

Add support for convolutions #1

antoinecarme opened this issue Feb 16, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@antoinecarme
Copy link
Member

antoinecarme commented Feb 16, 2018

Sample use case : simple convnet on the MNIST dataset

keras example : https://github.com/keras-team/keras/blob/master/examples/mnist_cnn.py

used layers and activation functions :

model.add(Conv2D(32, kernel_size=(3, 3),
                 activation='relu',
                 input_shape=input_shape))
model.add(Conv2D(64, (3, 3), activation='relu'))
model.add(MaxPooling2D(pool_size=(2, 2)))
model.add(Dropout(0.25))
model.add(Flatten())
model.add(Dense(128, activation='relu'))
model.add(Dropout(0.5))
model.add(Dense(num_classes, activation='softmax'))
@antoinecarme antoinecarme self-assigned this Feb 16, 2018
@antoinecarme antoinecarme added the enhancement New feature or request label Feb 16, 2018
antoinecarme added a commit that referenced this issue Feb 22, 2018
Added some test scripts for mnist dataset
antoinecarme added a commit that referenced this issue Feb 22, 2018
Added a jupyter notebook
@antoinecarme
Copy link
Member Author

Added a primary implementation which works for small models.

Main pain points (to be solved):

  1. The second Conv2D layer
  2. the Flatten layer is too large (depends on the number of filters used in convolutions : 32 and 64). This layer works for small number of filters (in the jupyter notebook , we use 8 and 0)
  3. When the size of Flatter layer goes above 1000, we have some issues with the databases support for wide tables. => create separate issue (at least for some experiments. May not be solvable).
  4. The Dense layer leads to a very large model and SQL code. Need to perform some feature selection (make sparse models) and some simplification of the SQL code (non-used columns can be deleted).

@antoinecarme
Copy link
Member Author

Another possibility is to perform a compression (exact or approximate) of the model.

new issue => #5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant