/test/mlts/benchmark/src/com/android/nn/benchmark/core/ |
D | BenchmarkResult.java | 107 protected BenchmarkResult(Parcel in) { in BenchmarkResult() argument 108 mLatencyInference = in.readParcelable(LatencyResult.class.getClassLoader()); in BenchmarkResult() 109 mLatencyCompileWithoutCache = in.readParcelable(LatencyResult.class.getClassLoader()); in BenchmarkResult() 110 mLatencySaveToCache = in.readParcelable(LatencyResult.class.getClassLoader()); in BenchmarkResult() 111 mLatencyPrepareFromCache = in.readParcelable(LatencyResult.class.getClassLoader()); in BenchmarkResult() 112 mSumOfMSEs = in.readFloat(); in BenchmarkResult() 113 mMaxSingleError = in.readFloat(); in BenchmarkResult() 114 mTestInfo = in.readString(); in BenchmarkResult() 115 mNumberOfEvaluatorResults = in.readInt(); in BenchmarkResult() 117 in.readStringArray(mEvaluatorKeys); in BenchmarkResult() [all …]
|
D | LatencyResult.java | 74 public LatencyResult(Parcel in) { in LatencyResult() argument 75 mTotalTimeSec = in.readFloat(); in LatencyResult() 76 mIterations = in.readInt(); in LatencyResult() 77 mTimeStdDeviation = in.readFloat(); in LatencyResult() 78 mTimeFreqStartSec = in.readFloat(); in LatencyResult() 79 mTimeFreqStepSec = in.readFloat(); in LatencyResult() 80 int timeFreqSecLength = in.readInt(); in LatencyResult() 82 in.readFloatArray(mTimeFreqSec); in LatencyResult() 103 public LatencyResult createFromParcel(Parcel in) { 104 return new LatencyResult(in);
|
/test/mlts/benchmark/ |
D | README.txt | 4 you may not use this file except in compliance with the License. 9 Unless required by applicable law or agreed to in writing, software 20 Models and datasets used description and licensing can be found in 37 in corner case conditions. 39 To run the tests use the specific targets available in the build_and_run_benchmark.sh script. 40 By default, every test gets run on each available accelerator in isolation. It is possible to filte… 50 executed in parallel. Tests are running in a separate process so crashes can be detected and 53 * parallel-inference-stress-in-process: same as parallel-inference-stress but the tests are running 54 in the same process of the test so in case of crash the testing app will crash too 62 on a single model in multiple processes and threads with different probabilities in client process [all …]
|
D | LICENSE | 35 "Work" shall mean the work of authorship, whether in Source or 37 copyright notice that is included in or attached to the work 38 (an example is provided in the Appendix below). 40 "Derivative Works" shall mean any work, whether in Source or Object 51 submitted to Licensor for inclusion in the Work by the copyright owner 60 designated in writing by the copyright owner as "Not a Contribution." 71 Work and such Derivative Works in Source or Object form. 76 (except as stated in this section) patent license to make, have made, 83 cross-claim or counterclaim in a lawsuit) alleging that the Work 90 Work or Derivative Works thereof in any medium, with or without [all …]
|
/test/mlts/models/assets/asr_float/ |
D | LICENSE | 20 and certain other rights specified in the public license below. The 26 permission to use material in ways otherwise restricted by 48 rights in the material. A licensor may make special requests, 63 granted the Licensed Rights in consideration of Your acceptance of 64 these terms and conditions, and the Licensor grants You such rights in 73 and in which the Licensed Material is translated, altered, 74 arranged, transformed, or otherwise modified in a manner requiring 79 synched in timed relation with a moving image. 82 and Similar Rights in Your contributions to Adapted Material in 90 specified in Section 2(b)(1)-(2) are not Copyright and Similar [all …]
|
/test/vts/hals/light/bullhead/ |
D | NOTICE | 5 you may not use this file except in compliance with the License. 7 Unless required by applicable law or agreed to in writing, software 48 "Work" shall mean the work of authorship, whether in Source or 50 copyright notice that is included in or attached to the work 51 (an example is provided in the Appendix below). 53 "Derivative Works" shall mean any work, whether in Source or Object 64 submitted to Licensor for inclusion in the Work by the copyright owner 73 designated in writing by the copyright owner as "Not a Contribution." 84 Work and such Derivative Works in Source or Object form. 89 (except as stated in this section) patent license to make, have made, [all …]
|
/test/mlts/models/ |
D | LICENSE | 35 "Work" shall mean the work of authorship, whether in Source or 37 copyright notice that is included in or attached to the work 38 (an example is provided in the Appendix below). 40 "Derivative Works" shall mean any work, whether in Source or Object 51 submitted to Licensor for inclusion in the Work by the copyright owner 60 designated in writing by the copyright owner as "Not a Contribution." 71 Work and such Derivative Works in Source or Object form. 76 (except as stated in this section) patent license to make, have made, 83 cross-claim or counterclaim in a lawsuit) alleging that the Work 90 Work or Derivative Works thereof in any medium, with or without [all …]
|
/test/vts/proto/ |
D | VtsResourceControllerMessage.proto | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 34 // TODO: support this from host side in the future 41 // TODO: support this from host side in the future 43 // Get space available to write in FMQ. 47 // Get size of item in FMQ. 49 // Get number of items that fit in FMQ. 54 // This is an operation that is used in the target-side 104 // string to represent type of data in the queue 184 // in a handle object [all …]
|
D | ComponentSpecificationMessage.proto | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 329 // for length in bytes, and usually not required. 348 // To identify an existing hidl_memory object stored in resource_manager. 353 // an existing hidl_memory object stored in resource_manager. 355 // is found in memory. 375 // When opening a file in host side, user specifies file 376 // access mode in string. 394 // To specify an existing handle object registered in target-side driver. 401 // an existing hidl_handle object stored in target-side driver. [all …]
|
D | VtsReportMessage.proto | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 47 // interpret increases in values as regression 49 // interpret decreases in values as regression 86 // ABI name that is current in use for the test 89 // ABI bitness that is current in use for the test. Example: '32', '64', 255 // Content of log. Caution: do not put too much log in protobuf message, 260 // To specify a resource object (reachable via a URL or contained in the 262 // file kept in a Google Cloud Storage (GCS) bucket or partner's network file 328 // Keys used to find all TestReportMessage messages of test modules in [all …]
|
D | TestSchedulingPolicyMessage.proto | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 42 // period in seconds (for TEST_SCHEDULING_MODE_PERIODIC).
|
/test/vti/dashboard/ |
D | README.md | 15 Copy the following lines in ~/.bashrc : 47 3) Make a soft link in /usr/bin for universal access of mvn 71 google-cloud-sdk in test/vti/dashboard/pom.xml by putting the configuration: 110 in your local dev environment. 120 on json files under the testdata folder. However, you need to abide by some rules in doing this, 123 First, in test-plan-report-data.json, you need to set the same number of data under "testCaseNames" 124 and "results". For example, if you put 5 elements of data in "testCaseNames", you should put the sa… 152 Second, in test-report-data.json file, you need to make sure that "testModules" should have 154 in the test-report-data.json file. 191 The next two commands will generate mock data in your local dev datastore. [all …]
|
/test/app_compat/csuite/ |
D | pylintrc | 2 # best-practices and style described in the Google Python style guide: 46 # multiple time (only on the command line, not in the configuration file where 52 # option multiple times (only on the command line, not in the configuration 81 implicit-str-concat-in-sequence, 136 unpacking-in-except, 151 # Put messages in a separate file for each module / package specified on the 153 # written in a file name "pylint_global.[txt|html]". This option is deprecated 154 # and it will be removed in Pylint 2.0. 237 # Tells whether missing members accessed in mixin class should be ignored. A 276 # separator` is used to allow tabulation in dicts, etc.: {1 : 1,\n222: 2}. [all …]
|
/test/vts/tools/vts-core-tradefed/ |
D | README | 9 It works in a similar manner to the prior VTS harness, but with much 14 - supports sharding a VTS test run across multiple devices in parallel 20 1. Ensure 'adb' is in your current PATH. adb can be found in the 26 2. Follow the 'Setting up your device' steps documented in the VTS User Manual. 80 be forthcoming in the near future.
|
/test/vts/hals/ |
D | README.md | 1 …in the corresponding nexus device's HAL dirs but are compiled in a different way (e.g., with a pos…
|
/test/cts-root/ |
D | README.md | 6 Note that the name of this suite in the build system is CTS_ROOT (with an 8 `cts_root` in their test_suites to be included. 10 However in tradefed the name is cts-root (with a hyphen), so use
|
/test/app_compat/csuite/pylib/ |
D | Android.bp | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 17 // which is defined in an external Makefile that Soong can't depend on. 21 // dependencies in the tools attribute when we should be using the 'srcs'
|
/test/catbox/tools/catbox-tradefed/ |
D | Android.bp | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 24 full_name: "Complete Automotive Test in a Box",
|
D | README | 12 1. Ensure 'adb' is in your current PATH. adb can be found in the 18 2. Follow the 'ADB and AAPT' setup steps documented in the 70 be forthcoming in the near future.
|
/test/vts-testcase/performance/audio_loopback_test/ |
D | README.md | 5 1. plug in the Loopback dongle to your device. 13 * Which version of Loopback.apk is used in the test? 14 …The Loopback.apk used in this test is Loopback-v17 copied from https://tradefed.teams.x20web.corp.…
|
/test/vts-testcase/vndk/golden/ |
D | Android.bp | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 39 cmd: "$(location extract_lsdump) $(in) $(out)",
|
/test/app_compat/csuite/integration_tests/ |
D | Android.bp | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 17 // which is defined in an external Makefile that Soong can't depend on. 21 // dependencies in the tools attribute when we should be using the 'srcs'
|
/test/cts-root/tests/ |
D | README.md | 1 This is the default directory for device-side tests in the cts-root test suite. 3 Host-side tests should be placed in the cts-root/hostsidetests directory.
|
/test/cts-root/hostsidetests/ |
D | README.md | 1 This is the default directory for host-side tests in the cts-root test suite. 2 Device-side tests should be placed in the cts-root/tests directory.
|
/test/vts-testcase/kernel/gki/ |
D | Android.bp | 4 // you may not use this file except in compliance with the License. 9 // Unless required by applicable law or agreed to in writing, software 50 // shipping image. Hence, we can include this test in VTS.
|