-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Requesting lmdb support in extract_features.cpp #1155
Comments
To easily switch between LevelDB and LMDB, the two backends should be wrapped in two classes that share the same interface or base abstract class. Otherwise, using them in more places will make the code as ugly as if not uglier than exposed by #1074 which tried to segregate each of them using guarding macros. |
Maybe what you need is an output layer with the LevelDB or LMDB as the backing store similar to the HDF5OutputLayer. |
#1238 is building a unified API for LevelDB and LMDB. |
See #1238 but really the features can be extracted through pycaffe or matcaffe by just loading the model with its usual data layer defined. |
As lmdb is being used widely in caffe, including tools such as compute_image_mean.cpp, convert_imageset.cpp, it would be great to also extend lmdb support to extract_features.cpp.
This will improve tooling consistency as well as performance in scenarios which use the results of extract_features for various tasks which would benefit from the speed of lmdb.
Thank you for your consideration.
The text was updated successfully, but these errors were encountered: