| /third_party/mindspore/mindspore/ccsrc/minddata/dataset/engine/datasetops/source/ |
| D | voc_op.cc | 218 float xmin = 0.0, ymin = 0.0, xmax = 0.0, ymax = 0.0, truncated = 0.0, difficult = 0.0; in ParseAnnotationBbox() local
221 ParseNodeValue(object, "difficult", &difficult); in ParseAnnotationBbox()
237 std::vector<float> bbox_list = {xmin, ymin, xmax - xmin, ymax - ymin, difficult, truncated}; in ParseAnnotationBbox()
284 std::shared_ptr<Tensor> bbox, label, difficult, truncate; in ReadAnnotationToTensor() local
308 …RETURN_IF_NOT_OK(Tensor::CreateFromVector(difficult_data, TensorShape({bbox_num, 1}), &difficult)); in ReadAnnotationToTensor()
310 …(*row) = TensorRow({std::move(bbox), std::move(label), std::move(difficult), std::move(truncate)}); in ReadAnnotationToTensor()
|
| /third_party/libxml2/test/XPath/xptr/ |
| D | strrange2 | 3 xpointer(string-range(//p, 'difficult', 1, 0))
|
| D | strrange | 3 xpointer(string-range(//p, 'difficult'))
|
| /third_party/python/Doc/library/ |
| D | sndhdr.rst | 26 value or ``0`` if unknown or difficult to decode. Similarly, *channels* will be
28 value is difficult to decode. The value for *frames* will be either the number
|
| /third_party/ltp/testcases/open_posix_testsuite/conformance/interfaces/timer_settime/ |
| D | coverage.txt | 18 *Decided against testing this assertion as it would be quite difficult
|
| /third_party/boost/libs/metaparse/example/parsing_error/ |
| D | README | 3 be difficult to understand. This example demonstrates how debug_parsing_error
|
| /third_party/popt/ |
| D | README | 6 getopt(3) makes this quite difficult
|
| /third_party/boost/libs/iterator/doc/quickbook/ |
| D | iterator_traits.qbk | 6 such a "multi-valued" traits template can be difficult to use in a
|
| /third_party/boost/libs/config/doc/ |
| D | rationale.qbk | 19 difficult to maintain and more difficult to use safely. You can find a
|
| /third_party/boost/libs/config/test/ |
| D | boost_no_stdc_namespace.ipp | 12 // in namespace std. This test is difficult - some libraries
|
| /third_party/ltp/testcases/open_posix_testsuite/conformance/interfaces/fsync/ |
| D | coverage.txt | 20 That does not make the function any less valuable, just more difficult to test. A formal
|
| /third_party/ltp/doc/ |
| D | build-system-guide.txt | 17 The problem with the old Makefile system is that it was very difficult to
19 and including new targets was more difficult than it should have been
129 etc. This makes cross-compilation and determinism difficult, if not impossible.
|
| /third_party/boost/libs/system/doc/system/ |
| D | rationale.adoc | 23 difficult to write portable code than system-specific code.
|
| /third_party/boost/more/getting_started/detail/ |
| D | common-footnotes.rst | 8 extremely difficult to eliminate in generic code, to the point
|
| /third_party/libxml2/result/XPath/xptr/ |
| D | strrange2 | 59 Expression: xpointer(string-range(//p, 'difficult', 1, 0))
|
| /third_party/skia/third_party/externals/angle2/extensions/ |
| D | ANGLE_get_serialized_context_string.txt | 65 making the implementation difficult. It also allow a no-op
|
| /third_party/boost/libs/iterator/doc/ |
| D | iterator_traits.rst | 29 such a "multi-valued" traits template can be difficult to use in a
|
| /third_party/boost/libs/math/doc/quadrature/ |
| D | gauss_kronrod.qbk | 26 with no end point singularities. For difficult functions, or those with end point singularities, p…
65 algorithm descends the tree depth first, so only "difficult" areas of the integral result in interv…
113 has been made to make these routines work well with end-point singularities or other "difficult" in…
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/ARB/ |
| D | ARB_texture_rgb10_a2ui.txt | 135 RGB10A2UI - difficult to read
137 however it could difficult to know at a glace if the the UI applies to
|
| /third_party/boost/libs/phoenix/doc/ |
| D | maintenance.qbk | 92 One type of bug which has been very difficult to understand has been that some test cases failed wh…
110 * The most difficult problems to diagnose have been some which occur when the compilation uses opti…
114 * This has made the identification of the cause of the problems more difficult.
|
| /third_party/skia/third_party/externals/jinja2/ |
| D | README.rst | 25 possible, it shouldn't make the template designer's job difficult by
|
| /third_party/typescript_eslint/packages/eslint-plugin/docs/rules/ |
| D | no-dynamic-delete.md | 33 // Dynamic, difficult-to-reason-about lookups
|
| /third_party/jinja2/ |
| D | README.rst | 25 possible, it shouldn't make the template designer's job difficult by
|
| /third_party/flutter/flutter/packages/flutter/lib/src/foundation/ |
| D | synchronous_future.dart | 15 /// general use of this class should be avoided as it is very difficult to debug
|
| /third_party/boost/libs/math/doc/sf/ |
| D | owens_t.qbk | 119 for our test data at 100 decimal digits precision. However, there is a difficult area when
124 in the difficult area where ['a] is close to 1, and greater than 95 decimal places elsewhere.
|