aboutsummaryrefslogtreecommitdiffhomepage
path: root/tensorflow/examples/multibox_detector
Commit message (Collapse)AuthorAge
* Replaced calls to deprecated tensorflow::StringPiece methods with theirGravatar A. Unique TensorFlower2018-04-02
| | | | | | | | tensorflow::str_util equivalents. This will allow the deprecated methods to be removed. PiperOrigin-RevId: 191350894
* Remove all_opensource_files. It's not needed any more.Gravatar Martin Wicke2018-03-28
| | | | PiperOrigin-RevId: 190878279
* Remove RTLD_GLOBAL when loading pywrap_tensorflowGravatar Allen Lavoie2017-09-21
| | | | | | | | | | | | | | Splits out a shared object (//tensorflow/libtensorflow_framework.so) with core TensorFlow functionality but neither ops nor kernels. This object does include registries for ops, kernels, filesystems, etc. The expectation is that shared objects containing custom ops will have a runtime dependency on this framework shared object: TensorFlow will load the custom op shared object, and the custom op shared object will use the symbols from the framework shared object to register its ops/kernels/etc. rather than (as before this change) relying on those symbols being in the global symbol table. In this mode, TensorFlow artifacts (_pywrap_tensorflow.so for Python, libtensorflow.so for the C API; currently excluding Android artifacts) will depend on the framework shared object, which will be packaged with the Python pip package and other language distributions. This means that custom ops targeting the framework shared object will work in any language (C++, Java, Go; previously custom ops in these languages required custom Bazel builds). Adds a config option which reproduces the old behavior (--config=monolithic), which for Python means building a monolithic pywrap_tensorflow shared object and loading its symbols into the global symbol table (with RTLD_GLOBAL). As before, there will be no extra-Bazel custom op support for other languages when compiling in this mode. Does not change behavior on Windows; the cmake build is still monolithic. Requires using tf_cc_binary, tf_cc_test, and (rarely) tf_cc_shared_object rules to link in the framework shared object when adding new TensorFlow build rules. PiperOrigin-RevId: 169572746
* BUILD dependency cleanups.Gravatar Peter Hawkins2017-08-07
| | | | | | Rename RecvTensorAsync method to GrpcRecvTensorAsync to fix shadowing of method in Worker with a different signature. PiperOrigin-RevId: 164454701
* BUILD cleanupGravatar A. Unique TensorFlower2017-08-05
| | | | PiperOrigin-RevId: 164369858
* Further BUILD cleanupGravatar A. Unique TensorFlower2017-07-27
| | | | PiperOrigin-RevId: 163360750
* Further BUILD cleanupGravatar A. Unique TensorFlower2017-06-21
| | | | PiperOrigin-RevId: 159749869
* Remove unnecessary copies of value parameters.Gravatar Peter Hawkins2017-05-10
| | | | PiperOrigin-RevId: 155511618
* Merge changes from github.Gravatar Benoit Steiner2017-02-08
| | | | Change: 146918929
* Add a mechanism for hiding, skipping, and modifying the generated opGravatar A. Unique TensorFlower2017-02-01
| | | | | | | | | | | | | | | | functions for C++. A souped-up version of the hidden_ops mechanism in Python, the intent is to use this for most or all of the client languages, with a common list of changes to make in a common file and per-language overrides. Also: * include the documentation for outputs in the generated comments * several updates to C++ API to match Python * fix C++ shape function for ConcatV2 now that we use it by default * split op_gen_lib out of core:framework, since it is only used by the op generators, and I don't want to add another proto to mobile builds Change: 146267344
* Fix links in multibox detector demo README.mdGravatar Andrew Harp2017-01-26
| | | | Change: 145722859
* Adding MultiBox person detector standalone example.Gravatar Andrew Harp2017-01-25
Change: 145608840