Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:significant (Results 501 - 525 of 2960) sorted by null

<<21222324252627282930>>

/bionic/libc/arch-arm64/generic/bionic/
strcmp.S	103 MSB might be significant. */
/bionic/libc/bionic/
mbrtoc32.cpp	119 // of 6 bits, most significant first.
/build/tools/ijar/
README.txt	31 simpler .jar file containing only the parts that are significant for
/cts/tests/tests/security/src/android/security/cts/
CertificateTest.java	49 * <p>This test exists because adding root CAs to a device has a very significant security
/dalvik/dx/src/com/android/dx/ssa/
package-info.java	98 * number (register categories or widths, significant in Rop form, do not
/docs/source.android.com/src/devices/sensors/
report-modes.jd	58 other event is sent until the sensor is reactivated. <a href="sensor-types.html#significant_motion">Significant motion</a> is an example of this kind of sensor.</p>
suspend-mode.jd	70 of the <a href="sensor-types.html#proximity">proximity</a> sensor and the <a href="sensor-types.html#significant_motion">significant motion detector</a>.</p>
/docs/source.android.com/src/security/overview/
index.jd	51 technologies that have undergone significant external security review,
/external/ImageMagick/ImageMagick/script/
miff.html	214 <p>DirectClass images are continuous-tone, images stored as RGB (red, green, blue), RGBA (red, green, blue, alpha), CMYK (cyan, yellow, magenta, black), or CMYKA (cyan, yellow, magenta, black, alpha) intensity values as defined by the colorspace key. Each intensity value is one byte in length for images of depth 8 (0..255), two bytes for a depth of 16 (0..65535), and images of depth 32 (0..4294967295) require four bytes in most significant byte first order.</p> 216 <p>PseudoClass images are colormapped RGB images. The colormap is stored as a series of red, green, and blue pixel values, each value being a byte in size. If the image depth is 16, each colormap entry consumes two bytes with the most significant byte being first. The number of colormap entries is defined by the colors key. The colormap data occurs immediately following the header (or image directory if the montage key is in the header). PseudoClass image data is an array of index values into the color map. If there are 256 217 or fewer colors in the image, each byte of image data contains an index value. If the image contains more than 256 colors or the image depth is 16, the index value is stored as two contiguous bytes with the most significant byte being first. If matte is true, each colormap index is followed by a 1 or 2-byte alpha value.</p> 219 <p>The image pixel data in a MIFF file may be uncompressed, runlength encoded, Zip compressed, or BZip compressed. The compression key in the header defines how the image data is compressed. Uncompressed pixels are stored one scanline at a time in row order. Runlength-encoded compression counts runs of identical adjacent pixels and stores the pixels followed by a length byte (the number of identical pixels minus 1). Zip and BZip compression compresses each row of an image and precedes the compressed row with the length of compressed pixel bytes as a word in most significant byte first order.</p>
/external/ImageMagick/utilities/
identify.1	42 \-precision value maximum number of significant digits to print
identify.1.in	42 \-precision value maximum number of significant digits to print
/external/ImageMagick/www/
miff.html	218 <p>DirectClass images are continuous-tone, images stored as RGB (red, green, blue), RGBA (red, green, blue, alpha), CMYK (cyan, yellow, magenta, black), or CMYKA (cyan, yellow, magenta, black, alpha) intensity values as defined by the colorspace key. Each intensity value is one byte in length for images of depth 8 (0..255), two bytes for a depth of 16 (0..65535), and images of depth 32 (0..4294967295) require four bytes in most significant byte first order.</p> 220 <p>PseudoClass images are colormapped RGB images. The colormap is stored as a series of red, green, and blue pixel values, each value being a byte in size. If the image depth is 16, each colormap entry consumes two bytes with the most significant byte being first. The number of colormap entries is defined by the colors key. The colormap data occurs immediately following the header (or image directory if the montage key is in the header). PseudoClass image data is an array of index values into the color map. If there are 256 221 or fewer colors in the image, each byte of image data contains an index value. If the image contains more than 256 colors or the image depth is 16, the index value is stored as two contiguous bytes with the most significant byte being first. If matte is true, each colormap index is followed by a 1 or 2-byte alpha value.</p> 223 <p>The image pixel data in a MIFF file may be uncompressed, runlength encoded, Zip compressed, or BZip compressed. The compression key in the header defines how the image data is compressed. Uncompressed pixels are stored one scanline at a time in row order. Runlength-encoded compression counts runs of identical adjacent pixels and stores the pixels followed by a length byte (the number of identical pixels minus 1). Zip and BZip compression compresses each row of an image and precedes the compressed row with the length of compressed pixel bytes as a word in most significant byte first order.</p>
/external/apache-commons-math/src/main/java/org/apache/commons/math/linear/
SingularValueDecomposition.java	136 * is the least significant bit of the largest singular value.</p>
/external/apache-xml/src/main/java/org/apache/xalan/
Version.java	84 * significant, externally apparent enhancement from
Version.src	84 * significant, externally apparent enhancement from
/external/apache-xml/src/main/java/org/apache/xml/serializer/
HTMLEntities.properties	24 # Character entity references for markup-significant
/external/autotest/client/cros/i2c/
usb_to_i2c.py	18 # Least significant bit of I2C address.
/external/autotest/client/tests/cyclictest/
help	50 Please be aware that the tracer adds significant overhead to the kernel, so the
/external/autotest/server/site_tests/network_WiFi_BgscanBackoff/
network_WiFi_BgscanBackoff.py	93 raise error.TestFail('Significant difference in rtt due to bgscan: '
/external/boringssl/src/crypto/bn/
kronecker.c	58 /* least significant word */
/external/boringssl/src/include/openssl/
des.h	92 /* DES_set_odd_parity sets the parity bits (the least-significant bits in each
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/asn1/
DLSet.java	25 * NOTE &mdash; The order of data values in a set value is not significant,
/external/ceres-solver/data/nist/
ENSO.dat	15 reveals 3 significant cycles. The annual cycle is the
/external/ceres-solver/internal/ceres/
cxsparse.h	104 // significant performance improvement AnalyzeCholesky on block
sparse_matrix.h	48 // stored. This has significant implications for linear solvers

Completed in 1409 milliseconds

<<21222324252627282930>>