-
Notifications
You must be signed in to change notification settings - Fork 723
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
[Caffe] Improve caffe.Net documentation on forwarding #207
Comments
Where is that native function? I can't seem to find it in rc3: |
Well, it appears that I was looking at a more recent header file. It does seem to make a bit more sense with the intended version. Still, couldn't the description of each method be copied to the Java files? It also appears that I'm having some issues with the outcome of forwarding, now that I understand the API, but that ought to be handled elsewhere. |
All the comments should be copied. If there is anything missing, please
point it out! Thanks
|
You are right, the comments are there, my IDE simply didn't take them. Allow me to close this issue, then. Thank you for the help. |
But they might not get converted properly to Javadoc, so if you see
something that could be converted better, post your suggested conversion!
Thanks
|
I have been trying to use a
caffe.Net
for classification purposes, and right now I feel that the documentation on theForward
method and its overloads is not clear enough. All of my efforts so far have either resulted in failed assertions or JVM crashes. Ignoring loss-providing variants, this is what the documentation describes:The string-based overload is particularly confusing. It would seem to be the name of the input layer to start forwarding from, but this results in an error: "net.cpp:618] Check failed: blob_proto_vec.blobs_size() == net_input_blobs.size() (0 vs. 1) Incorrect input size."_
The API does not seem to reflect neither of the Python and native APIs either:
Setting the input layer's data (with
#set_cpu_data(FloatBlob)
) and callingForwardPrefilled()
seems to proceed peacefully, but not only is it deprecated in the original project, but I'm also observing some inconsistencies in the outcome that I cannot tell whether they relate to an improper use of the API or not.Could someone enlighten me on this matter and improve this sub-project's apidocs on the way?
The text was updated successfully, but these errors were encountered: