Skip to content

Conversation

@sguada
Copy link
Contributor

@sguada sguada commented May 16, 2014

Currently the layer compute the index of the maximum value for each image across all features (channels x height x width). It is intended to be used after a classification layer to produce the predicted label.
If parameterout_max_val is set to true then it will produce a vector of pairs (max_ind,max_val) for each image.
In the future it could accept specific dimensions to compute the maximum and argmax.

@sergeyk
Copy link
Contributor

sergeyk commented May 21, 2014

Dang, something went wrong. I followed up with some additional commits to correctly update caffe.proto, fix lint errors, and document the layer in vision_layers.hpp, and pushed to bvlc/dev [70825f95ad51dc3d8696c070efca3241f698a8b4], but for some reason github didn't pick it up automatically here.

@sergeyk sergeyk closed this May 21, 2014
@sergeyk
Copy link
Contributor

sergeyk commented May 21, 2014

Thanks Sergio!

sergeyk added a commit that referenced this pull request May 21, 2014
@shelhamer
Copy link
Member

@sergeyk there's a convention you need to follow to make github understand manual merges. I'm all for doing the merge yourself for the sake of integration, but you need to make the merge commit with a github style commit message.

Better yet, collaborate with the requester by checking out a tracking branch of the pull request branch then pushing your changes to the existing request. Of course that only works if you have push rights, or you could ask the collaborator to merge your commits.

I rebased dev to fix your merge.

@shelhamer
Copy link
Member

There's no way to fix this PR to show it as merged rather than closed however. If you want to do a manual merge in the future, please format the merge commit like I did in efbea35 (rebasing your commit) to trigger the github merge machinery.

@sergeyk
Copy link
Contributor

sergeyk commented May 21, 2014

Alright, thanks

On Tuesday, May 20, 2014, Evan Shelhamer notifications@github.com wrote:

There's no way to fix this PR to show it as merged rather than closed
however. If you want to do a manual merge in the future, please format the
merge commit like I did in efbea35efbea35092201a2868303cb5126f6f90d992de51(rebasing your commit).


Reply to this email directly or view it on GitHubhttps://github.com//pull/421#issuecomment-43713159
.

@shelhamer
Copy link
Member

4d52ca7 broke Caffe. There's no seed_ member of ArgMaxLayerTest(). Run the tests!

@shelhamer
Copy link
Member

Fixed by revert @ a13e7ee.

@sergeyk
Copy link
Contributor

sergeyk commented May 21, 2014

Thanks, sorry about that.

On Tuesday, May 20, 2014, Evan Shelhamer notifications@github.com wrote:

Fixed by revert @ a13e7ee a13e7ee.


Reply to this email directly or view it on GitHubhttps://github.com//pull/421#issuecomment-43713884
.

@sguada
Copy link
Contributor Author

sguada commented May 21, 2014

I'm confused about what happened with my PR? @sergeyk or @shelhamer did you merge it? @sergeyk did you try to push to my repo?

@shelhamer
Copy link
Member

@sguada your PR is merged and everything's alright.

Sergey did a weird merge github couldn't understand, I fixed it to reflect history but github can't be told what actually happened at this point, so the PR is closed but it is in fact merged if you look at BVLC/dev.

@sguada
Copy link
Contributor Author

sguada commented May 21, 2014

@shelhamer thanks !!

It was a bit confusing for me, but I checked in dev and seems merged appropriately.
@sergeyk could you review #422 too?

@shelhamer shelhamer mentioned this pull request Aug 8, 2014
mitmul pushed a commit to mitmul/caffe that referenced this pull request Sep 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants