I have two proto src file, in same folder, let's say:
the 1st one is foo.proto
syntax = "proto3";
package foo;
the second is bar.proto, which need import foo.proto
syntax = "proto3";
import "foo.proto";
package bar;
you can see they have different package name, when I use protoc to
Just peeking at
https://github.com/BVLC/caffe/blob/master/src/caffe/proto/caffe.proto (which
I'm guessing is the proto in question), I don't think it allows extension
at the moment.
On Wed, Jun 21, 2017 at 5:39 PM Bo Yang wrote:
> For option 2, I think you can extend
For option 2, I think you can extend caffe.LayerParameter by your self,
given that LayerParameter allows extension.
On Wed, Jun 21, 2017 at 1:12 AM Brian Palmer wrote:
> Hi,
>
> it sounds to me like you should explore defining a new message that
> contains the LayerParameter
I mean you can send a pull request to our github repository.
On Tue, Jun 20, 2017 at 10:24 PM Abhay Singh <22ab...@gmail.com> wrote:
> Hello Yang,
>
> Thanks for your response, sorry i did not get that *"PR to fix "*. Is
> there any link or webpage available where i can put a request for this.
>
Martin,
You may want to consider the Lite runtime. If you're using Proto3 you
could also try use the 'Any' type to loosely couple your proto definitions.
Regards,
Mohamed Koubaa
Software Developer
ANSYS Inc
On Wed, Jun 21, 2017 at 9:01 AM, Martin Kosicky
wrote:
> Hi
Hi I have a problem. We have a dedicated .dll to export all protobuf
messages so the project is not confusing and other projects are just
importing them. Problem started when I got the LIBTOOMANYMEMBERS:: library
limit of number objects exceeded *The limit of 65535 objects or members in
a
Hi,
it sounds to me like you should explore defining a new message that
contains the LayerParameter as a field. For example,
syntax = "proto2";
package lynxcommando;
message AugmentedLayerParameter {
optional caffe.LayerParameter base = 1;
optional MyNewParameter my_new_parameter = 2;
}
wow, auto-complete went mad with that, sorry. "nay" => may; "red is" =>
redis, etc.
On 21 Jun 2017 8:22 a.m., "Marc Gravell" wrote:
> "You wish to express data in a mechanism that can be expressed as a byte
> stream, and/or communicate that between systems that nay or
"You wish to express data in a mechanism that can be expressed as a byte
stream, and/or communicate that between systems that nay or may not be
using different architectures, in a way that is efficient both
computationally and in terms of bandwidth; and a platform independent tool
to express the