Giter VIP home page Giter VIP logo

fast_dense_feature_extraction's People

Contributors

erezposner avatar mohannikam-jidoka avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

fast_dense_feature_extraction's Issues

Please check typo

image

Hi,

Could you check typo in "Expected verbose"?

Total time for C_P => C_I ?

Averaged time for C_I => C_P ?

And why you do not compare Total time between two models?

Thank you.

dimensions of the ouput

the SlimNet has a 3-dimensions output with shape (-1, imH, imW) now.
but if we have a batch of images for input, should the net have output with 4-dimensions ? like(batch_size, -1, imH, imW)?

thanks.

pytorch version sample_code.py run error

Running method: allPatches on device: cuda:0
Total time for C_I: 0.01324005126953125sec
Averaged time for C_P per Patch without warm up: 0.0012916574080009014sec
------- Comparison between a base_net over all patches output and slim_net -------
aggregated difference percentage = 0.0000458457%
Traceback (most recent call last):
File "d:/user/FE_pj/Fast_Dense_Feature_Extraction/sample_code.py", line 175, in
yi, xi = np.unravel_index(index, (imH, imW))
File "<array_function internals>", line 6, in unravel_index
ValueError: index 108153647 is out of bounds for array with size 1228800

This fast dense feature extraction method (FDFE) seems not equal to the common one in terms of different receptive field.

Hi,

I have a concern about the equality of the proposed method and the commonly used one. For example, if the image size is 240 * 240 and the patch size is 24 * 24, the receptive field of the commonly used method (i.e., extract all patches one by one from the whole image) would not exceed the patch size due to the fact that all patches are fed into the network independently for feature extraction. However, the receptive field of this FDFE seems to consider the region larger than 24 * 24 if the pooling operation is used.

Could you please explain why they are equal if we require the latent code (the results from feature extraction) is only generated from each fixed patch size (e.g., 24 * 24)?

Thanks,

Xiaohong

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.