- 13 7月, 2017 2 次提交
- 11 7月, 2017 7 次提交
-
-
由 liaogang 提交于
-
由 liaogang 提交于
-
由 liaogang 提交于
-
由 Yu Yang 提交于
* generic.cmake can propogate dependencies through libraries. It is no need to specific all dependencies.
-
由 dongzhihong 提交于
-
由 dongzhihong 提交于
-
由 dongzhihong 提交于
-
- 10 7月, 2017 2 次提交
- 07 7月, 2017 2 次提交
-
-
由 fengjiayi 提交于
* init op_registry.h * dev op_registry.h * add 'attr_checker.h', which is a draft of op attribute checker. * rename some macro parameters * 1. Use `Attribute` and `AttributeMap` instead of `OpDesc`. `AttributeMap` is a unordered_map of <string, Attribute>, and `Attribute` is a boost::variant object to hold multiple types of attribute value. 2. Use `PADDLE_ENFORCE` to print checkers' fail message. 3. Abstract default value operations to a new function: `DefaultChecker`. * rename DefaultChecker to DefaultValueSetter ZZ * Finish op_registry 1. Complete the development of interfaces between OpRegistry and Protobuf. 2. Add unit test for op_registry.h * Add demo and test of custome checker * fix merge conflict
-
由 gongweibao 提交于
-
- 06 7月, 2017 9 次提交
-
-
由 gongweibao 提交于
-
由 liaogang 提交于
-
由 Yu Yang 提交于
Python should be able to manipulate Protobuf message because: 1. Python's `create_op_creation_methods` take the `OpProto` array to generate all `op_creation_methods` in RunTime. 2. All `op_creation_methods` will create an `OpDesc` and pass it to Paddle C++ method `CreateOp` and return the Op handle. Here is the list of what is added in this commit: * Add `protobuf_generate_python` if it is not defined. * Before cmake 3.4, `protobuf_generate_python` is not defined. Just copy the implementation of that function in `protobuf.cmake` * Add `py_proto_compile` function in `cmake/generic.cmake`. * It follows bazel's API interface. * https://github.com/pubref/rules_protobuf#rules * Add an empty package named `paddle.v2.framework`, all python code of `paddle::framework` will be in that package. * Generate protobuf's python module `__init__.py` by `touch` while compiling. * Change setup.py.in, make `paddle.v2.framework.proto` uses the generated protobuf pythons.
-
由 Yu Yang 提交于
* We should not EXPECT_EQ between a float value and a int value. Use ASSERT_NEAR instead.
-
由 liaogang 提交于
-
由 Superjom 提交于
-
由 liaogang 提交于
-
由 liaogang 提交于
-
由 liaogang 提交于
-
- 05 7月, 2017 13 次提交
-
-
由 liaogang 提交于
-
由 yangyaming 提交于
-
由 gongweibao 提交于
-
由 gongweibao 提交于
-
由 Yu Yang 提交于
Use CHECK instead of PCHECK, because PCHECK is used for errno.
-
由 liaogang 提交于
-
由 wuyi05 提交于
-
由 yangyaming 提交于
-
由 yangyaming 提交于
-
由 Luo Tao 提交于
-
由 Superjom 提交于
-
由 Superjom 提交于
-
由 Superjom 提交于
-
- 04 7月, 2017 5 次提交
-
-
由 liaogang 提交于
-
由 liaogang 提交于
-
由 Yu Yang 提交于
The implementation of BarrierStat is buggy, and it is not necessary for Paddle to diagnose which node in cluster is slow.
-
由 Qiao Longfei 提交于
* add op_desc.proto In Operator design, we need a proto message to describe an Operator. Third-party language such as python can build this proto message and use AddOp(const OpDesc& op_desc) of Paddle core to construct an Op in the Network.
-
由 qijun 提交于
-