Thanks, I think I understand now. I do think identifying a "root" type in
the .proto would have been a big help and wouldn't have cost much space or
bandwidth.
If I had time, I'd write a tool that would infer the root by testing for
types that have matching fields, but life is short...
On Sun
On Sun, Dec 10, 2017 at 11:23 AM, Jim Baldwin wrote:
> Perhaps it might help if I understood the output of protoc --decode_raw.
>
> Here's an example of a .caffemodel file I'm trying to inspect. Is there a
> description of what the numbers mean in this file?
As I said... it's a sequence of (tag,
They are field numbers. They don't mean anything by themselves other than
to identify each field. If you want to know the logical *name* of each
field, you need the .proto schema.
On 10 Dec 2017 4:23 p.m., "Jim Baldwin" wrote:
> Perhaps it might help if I understood the output of protoc --decode
Perhaps it might help if I understood the output of protoc --decode_raw.
Here's an example of a .caffemodel file I'm trying to inspect. Is there a
description of what the numbers mean in this file?
1: "VGG_ILSVRC_16_layers"
100 {
1: "input-data"
2: "Python"
4: "data"
4: "im_info"
4: