Searched refs:traversal (Results 1 – 5 of 5) sorted by relevance
/packages/modules/NeuralNetworks/tools/api/ |
D | OperationTypes.t | 54 * major order, the traversal order would be [D0, D1], whereas to store it in column major 55 * order, the traversal order would be [D1, D0]. If the 2-D matrix has a 2-D inner block, 56 * the traversal order could be [D0, D1, D2, D3]. 59 * * 3: In the traversal order defined above, the format (dense vs. sparse) and index metadata 89 * * 1: A 1-D {@link OperandType::TENSOR_INT32} tensor defining the traversal order for reading 91 * block sparse with a k-dimensional block (0 < k <= n), the traversal order has n+k 94 * internally. If not block sparse, the traversal order is just a permutation of [D0, …, 102 * each dimension in the traversal order (listed above). The format is either DENSE (where
|
/packages/modules/OnDevicePersonalization/src/com/android/libraries/pcc/chronicle/analysis/impl/ |
D | CantripFactoryImpl.kt | 65 val traversal = in <lambda>() constant 71 OpticalCantrip(traversal, op as Operation<Any, Any>) as Cantrip<Data> in <lambda>()
|
/packages/inputmethods/LatinIME/dictionaries/ |
D | en_GB_wordlist.combined.gz |
|
D | en_US_wordlist.combined.gz |
|
D | en_wordlist.combined.gz |
|