Hmmm. Back to the core problem. I am not certain I have the root.
Case in point:
caffe.proto:
https://github.com/BVLC/caffe/blob/master/src/caffe/proto/caffe.proto
I'm gradually thinking the root of this file is "NetParameter", but I'm not
sure how I was supposed to know that. :-P
I still
oh, there is a root. if i had to guess it has something like:
message TheRootMessageType {
required string name = 1;
repeated SomeNoun items = 100;
}
On 10 Dec 2017 4:42 p.m., "Jim Baldwin" wrote:
> In this case, it looks like there isn’t a root. Rather, this format is a
> series of
In this case, it looks like there isn’t a root. Rather, this format is a
series of top-level parameters. So, I have to give it the Parameter I’m
looking for. The problem I have with this is the order of parameters _might_
matter, and I lose that by only looking for one.
On Dec 10, 2017, at 8
as I ubderstand it, --decode *will do that*. it doesn't decode *just* the
root : but, it needs to know the root message type in order to correctly
interpret the data
On 10 Dec 2017 4:32 p.m., "Jim Baldwin" wrote:
> OK, this helps. I need to figure out what the "root" message is. It
> seems lik
OK, this helps. I need to figure out what the "root" message is. It seems
like an omission in the whole PB thing that you can't specify the .proto
and do a --decode_everything.
On Sunday, December 10, 2017 at 8:23:12 AM UTC-8, Marc Gravell wrote:
>
> You can and it does. The problem is that th
You can and it does. The problem is that the wire format by itself doesn't
tell it **what message type** the root object is. So you need to tell it in
the additional parameter to --decode
On 10 Dec 2017 3:14 p.m., "Jim Baldwin" wrote:
It's not really just a sequence; it's a hierarchy, isn't it?
It's not really just a sequence; it's a hierarchy, isn't it? Why can't I
use --decode or something like that?
On Saturday, December 9, 2017 at 4:20:15 PM UTC-8, Ilia Mirkin wrote:
>
> On Sat, Dec 9, 2017 at 5:52 PM, Jim Baldwin > wrote:
> > I have a protobuf file, and a .proto file that desc
On Sat, Dec 9, 2017 at 5:52 PM, Jim Baldwin wrote:
> I have a protobuf file, and a .proto file that describes the schema.
>
> The .proto describes dozens of different messages that may be in the
> protobuf file.
>
> I would like to know what messages can be found in the file. I do a protoc
> --de
I have a protobuf file, and a .proto file that describes the schema.
The .proto describes dozens of different messages that may be in the
protobuf file.
I would like to know what messages can be found in the file. I do a protoc
--decode_raw and get something out, but I don't see how to use tha