Content-type: text/html; charset=UTF-8
Man page of SDPARM
SDPARM
Section: SDPARM (8)
Updated: April 2021
Index
Return to Main Contents
NAME
sdparm - access SCSI modes pages; read VPD pages; send simple SCSI commands.
SYNOPSIS
sdparm
[--all] [--dbd] [--examine] [--flexible]
[--get=STR] [--hex] [--long] [--num-desc]
[--out-mask=OM] [--page=PG[,SPG]] [--quiet]
[--readonly] [--six] [--transport=TN]
[--vendor=VN] [--verbose] DEVICE [DEVICE...]
sdparm
[--clear=STR] [--defaults] [--dummy]
[--flexible] [--page=PG[,SPG]] [--quiet]
[--readonly] [--save] [--set=STR]
[--six] [--transport=TN] [--vendor=VN]
[--verbose] DEVICE [DEVICE...]
sdparm
--command=CMD [--hex] [--long] [--readonly]
[--verbose] DEVICE [DEVICE...]
sdparm
--inquiry [--all] [--examine] [--flexible]
[--hex] [--num-desc] [--page=PG[,SPG]]
[--quiet] [--readonly] [--transport=TN]
[--verbose] DEVICE [DEVICE...]
sdparm
--enumerate [--all] [--inquiry] [--long]
[--page=PG[,SPG]] [--transport=TN] [--vendor=VN]
sdparm
--inhex=FN [--all] [--flexible] [--hex]
[--inquiry] [--long] [--pdt=DT] [--raw]
[--six] [--transport=TN] [--vendor=VN]
[--verbose]
sdparm
--wscan [--verbose]
sdparm
[--help] [--version]
DESCRIPTION
This utility fetches and potentially changes SCSI device (e.g. disk) mode
pages. Inquiry data including Vital Product Data (VPD) pages can also be
displayed. Commands associated with starting and stopping the medium; loading
and unloading the medium; and other housekeeping functions may also be issued
by this utility.
The first invocation shown in the synopsis is for accessing (i.e. reading)
mode page fields held on the DEVICE. The second form is for changing
mode page fields held on the DEVICE. The third form is for executing
some simple SCSI commands. The fourth form (i.e. the '--inquiry ...
DEVICE' form) is for fetching and decoding VPD pages from the given
DEVICE. The --enumerate form is for listing out mode or VPD
field data held by this utility (and if a DEVICE is given then it is
ignored). The --inhex=FN form decodes mode or VPD response data
provided in the named file (or from stdin if FN=- is given); that data
may either be in hexadecimal or binary. The second last form is for Windows
only and lists the available storage device names; see the OPTIONS entry for
--wscan. The final form is to provide command line help or the version
number (and date) of this utility.
If no options (other than DEVICE) are given then a selection of common
mode page fields for that device are listed. If the --long option is
also given then a description of the fields is placed on the right of each
line. If the --all option is given then all known mode page fields
for that device are listed. Individual fields can be displayed with the
--get=STR option (e.g. '--get=WCE' to fetch the state of the
Writeback Cache Enable field).
This utility completes with an exit status of 0 when successful. For other
values see the EXIT STATUS section below.
One or more DEVICE arguments can be given. The utility will
essentially apply the given options to each DEVICE in the list. If a
error is detected, it is noted and the utility continues. Error value 5 (file
open or close problem) is treated as lower priority when other errors are
detected. The exit status is the most recently detected error value
(excluding error value 5 if other errors have been detected). If all actions
succeed the exit status is zero.
By default this utility shows mode pages that are common to all transport
protocols. These are termed as "generic" mode pages. If there is no match on
a generic mode page name or field then those pages specific to the SAS
transport are checked. Transport protocol specific mode pages are selected
with the --transport=TN option. See the TRANSPORT section below.
Vendor specific mode pages are selected with the --vendor=VN option.
See the VENDORS section below.
Although originally for SCSI disks (or storage devices that appear to the
OS as SCSI disks) many of the mode pages are for other SCSI device types.
These include CD/DVD players that use the ATAPI (or any other) transport,
SCSI tapes drives and SCSI enclosures.
When the --inquiry option is given without a page number then the
Device Identification VPD page (page number 0x83) is requested and
if found it is decoded and output. If no page number is given and
the --all option is given then a list of VPD page names (but not
their contents) supported by the DEVICE is output. When both
the --inquiry and --page=PG options are given then
the VPD page can be specified as an abbreviation (e.g. "sp" for the SCSI
ports VPD page) or numerically (e.g. "0x88"). If a VPD page is returned
by the DEVICE but sdparm cannot decode it or the --hex
option is given then it is output in hex.
OPTIONS
Mandatory arguments to long options are mandatory for short options as well.
If an option takes a numeric argument then that argument is assumed to
be decimal unless otherwise indicated (e.g. with a leading "0x" or a
trailing "h"). The options are in alphabetical order, based on the long
option name.
- -a, --all
-
output all recognized fields for the device type (e.g. disk) of the
DEVICE. Without this option (or the --page=PG[,SPG] option) the
default action is to output a relatively small number of commonly used fields
from different pages. When a specific (mode) page number is given with the
--page=PG[,SPG] option then all the fields of that page are
output (irrespective of the setting of this option). For this option's action
when used with the --enumerate option see the ENUMERATE section below.
When used together with the --inquiry option and a DEVICE, the
Supported VPD Pages VPD page [0x0] is output. When this option is used
twice (short form: '-iaa') then all VPD pages (listed in the Supported VPD
Pages VPD page) are output.
By default --inhex=FN will only decode the first mode page found in
FN. With this option, more mode pages will be decoded if present. When
--transport=TN or --vendor=VN is also given then if a given
mode page is not defined for that transport or vendor, then it is decoded
as a generic mode page.
- -c, --clear=STR
-
In its simplest form STR contains a field acronym_name or a field
numerical descriptor. In the absence of an explicit value
argument (e.g. '--clear=WCE=1'), the field has its value cleared to zero.
See the PARAMETERS section below.
- -C, --command=CMD
-
Perform given CMD. See section below on COMMANDS. To enumerate supported
commands use '-e -C x' (using any CMD name, valid or otherwise).
- -B, --dbd
-
disable block descriptors. This is a bit in MODE SENSE cdbs that
rarely needs to be set. One known case is a MODE SENSE 6 issued to a
Reduced Block Commands (RBC) device where the RBC standard says it
shall be set.
- -D, --defaults
-
sets the given mode page to its default values. Requires the
--page=PG[,SPG] option to be given to specify the mode page. To make
the default mode page values also the saved mode page values, use the
--save option as well.
when this option is used twice, the current values in all modes pages are
reverted to their defaults. If the --save option is given as well,
then the current and saved values in all modes pages are reverted to their
defaults. This feature uses the RTD bit in the MODE SELECT command which
was added in draft SPC-5 revision 11.
- -d, --dummy
-
when set inhibits changes being placed in the DEVICE's mode page.
Instead the mode data that would have been sent to a MODE SELECT
command, is output in ASCII hex to the console. This option is mainly
for testing.
- -e, --enumerate
-
lists out descriptive information about the pages and fields known to this
utility. Ignores the DEVICE argument and other options apart from
the --all, --inquiry, --long, --page=PG[,SPG],
--transport=TN and --vendor=VN. If --enumerate is
given without other options then the known (generic) mode pages are listed.
See the ENUMERATE section below.
- -E, --examine
-
for mode pages only those with known field names are probed when the
--all option is given. For VPD pages only those pages listed in
"Supported VPD pages page" are decoded. In both cases some pages may be
missed. With this option (i.e. --examine) all mode and VPD pages can
be probed.
For mode pages, this option will probe all mode pages from page number 0x0 to
0x3e. To probe mode subpages give a mode page number with --page=PG
and then all subpages (from 0x0 to 0xfe) are probed.
For VPD pages, use this option with --inquiry. This will cause all VPD
pages from 0x0 to 0xbf to be probed by default. A sequence of VPD pages can
be probed with --page=PG[,SPG] in which case VPD pages from PG (lower
number) to SPG (high number) inclusive are probed. Vendor specific VPD pages
run from 0xc0 to 0xff and can be probed by setting SPG from 0xc0 to 0xff.
- -f, --flexible
-
Some devices, bridges and/or drivers attempt crude transformations between
mode sense 6 and 10 byte commands without correctly rebuilding the response.
This will cause the response to be mis-interpreted (usually with an
error saying the response is malformed). With this option, the length
of the response is checked, and if it looks wrong, various corrections
are attempted. This option will also allow mode pages that don't belong
to the current device's peripheral type to be listed.
- -g, --get=STR
-
In its simplest form STR contains a field acronym_name or a field
numerical descriptor. The field is fetched from mode page. See the PARAMETERS
section below. The --long and --hex options effect the output
format. Also if a value of "1" is given (e.g. '--get=WCE=1') only the
current value is output (i.e. not the change mask, the default value and the
saved value).
- -h, --help
-
output the usage message then exit.
- -H, --hex
-
rather than trying to decode mode (or VPD) pages, print them out in
hex. When used with the --get=STR option the corresponding current,
changeable, default and saved values are output in hex, prefixed by "0x"
and space separated. If a value of "1" is given with the --get=STR
option (e.g. '--get=WCE=1') then only the current value is output in hex,
prefixed by "0x". If a value of "2" is given with the --get=STR
option then only the current value is output as a (signed) integer. This
option can be used multiple times (e.g. '-HH'). Useful with the ATA
Information VPD page which usually outputs its IDENTIFY (PACKET) DEVICE
response in 16 bit hex words; with '-HH' outputs that response in hex
bytes; with '-HHH' outputs the same response in a format suitable
for 'hdparm --Istdin' to decode.
Mode page output with the '-HHH' option is suitable for a later invocation
of sdparm with the --inhex=FN option.
- -I, --inhex=FN
-
FN is expected to be a file name (or '-' for stdin) which contains
ASCII hexadecimal (or binary) representing the response to MODE SENSE(10).
If --six is also given then the response from MODE SENSE(6) is
assumed. A MODE SENSE response contains a mode parameter header, then 0
or more block descriptors followed by one or more mode pages. This utility
will only decode the first mode page unless the --all option is
given. In order to decode a mode page the peripheral device type is often
needed and can be supplied with the --pdt=DT option. If the
--pdt=DT is not given then a mode page found in two device type
standards (e.g. SBC and SSC) may be decoded twice.
If --inquiry is given then FN is interpreted as the response
data of a single VPD page.
The hexadecimal in FN should be arranged as 1 or 2 digits representing
a byte each of which is whitespace or comma separated. Anything from and
including a hash mark to the end of line is ignored. If the --raw
option is given then FN is treated as binary.
- -i, --inquiry
-
output a VPD page which is in the response of a SCSI INQUIRY command sent
to DEVICE. In the absence of this option the default action
is to output mode pages. If the --inquiry option is given without
the --page=PG[,SPG] option then the device identification VPD
page (0x83) is decoded and output. If this option and the --all
option are given then the supported VPD pages page (0x0) is decoded and
output.
- -l, --long
-
output extra information. In the case of mode page fields a description (with
units if applicable) is output to the right. If used twice, then for some
fields more information about its values is given on one or more following
lines, each prefixed by a tab character. For usage with --enumerate
see the ENUMERATE section below.
When this option is used along with --command=capacity then the
READ CAPACITY(16) is sent to the DEVICE and if successful its extended
response is output.
- -n, --num-desc
-
for a mode page that can have descriptors, the number of descriptors for the
given page on the DEVICE is output. Otherwise 0 is output.
- -o, --out-mask=OM
-
OM is a bit mask for mode page selections that will be printed/output.
The 0x1 value is for the 'current' values, 0x2 is for the 'changeable'
values, 0x4 is for the 'default' values and 0x8 is for the 'saveable' values.
The default value is 0xf (i.e. the OR of all four values set). The option is
useful for limiting the amount of output with the '-HHH'.
- -p, --page=PG[,SPG]
-
supply the page number (PG) and optionally the sub page
number (SPG) of the mode (or VPD) page to fetch. These numbers are
interpreted as decimal unless prefixed with "0x" or a trailing. Sub page
numbers are only valid for mode pages (not VPD pages). Alternatively an
abbreviation for a page can be given (see next entry).
- -p, --page=STR
-
a two or three letter abbreviation for a page can be given. Known mode page
abbreviations are checked first followed by known VPD page abbreviations.
For example '--page=ca' matches the caching mode page. If no match is found
then an error is issued and a list of possibilities in the current context
is given (so '-p x' can be quite useful). If the STR matches a known
VPD page abbreviation then the --inquiry option is assumed. For
usage with --enumerate see the ENUMERATE section below.
- -P, --pdt=DT
-
This option is only active when the --inhex=FN option is given.
DT is the peripheral Device Type, a value between 0 and 31 and
can be found in the response to the INQUIRY command. The default value
is -1 (which may also be given for DT) and it is interpreted as
SPC (i.e. common mode pages) or as a wild card. If available this option
should be supplied with the --inhex=FN option.
- -q, --quiet
-
suppress output of device name followed by the vendor, product and revision
strings fetched from an INQUIRY response. Without this option such a line is
typically the first line output by sdparm. Reduces output from the device
identification VPD page, typically to one line (or none) for each of di_lu,
di_port, di_target and di_asis.
If this option is used twice then additionally mode page output suppresses the
changeable, default and saved values that are usually shown in braces, if
available.
- -r, --readonly
-
override other logic to open DEVICE in read-only mode. The default
setting of the open read-only/read-write mode depends on the operation
requested (e.g. a --set=STR operation by default will try a
read-write mode open on DEVICE). This option may be useful if a
command is being sent to an ATA disk via a SCSI command set. For example in
Linux '-C stop' may require this option to stop an ATA disk being restarted
immediately.
- -R, --raw
-
this option is only active when used with the --inhex=FN option.
When this option is given then the file FN is interpreted as binary;
the default action (i.e. when this option is not given) is to interpret
FN as ASCII hexadecimal.
- -S, --save
-
when a mode page is being modified (by using the --clear=STR and/or
--set=STR options) then the default action is to modify only the
current values mode page. When this option is given then the corresponding
value(s) in the saved values mode page is also changed. The next time the
device is power cycled (or reset) the saved values mode page becomes (i.e. is
copied to) the current values mode page. This option sets the SP field in
the MODE SELECT command. See NOTES section below.
- -s, --set=STR
-
in its simplest form STR contains a field acronym_name or a field
numerical descriptor. In the absence of an explicit value, each acronym_name
has its value set to (all) ones. This means a 16 bit field will be set to
0xffff which is 65535 in decimal. Alternatively each acronym_name or numerical
descriptor may be followed by "=<n>" where <n> is the value to set that field
to. See the PARAMETERS section below.
- -6, --six
-
The default action of this utility is to issue MODE SENSE and MODE SELECT
SCSI commands with 10 byte cdbs. When this option is given the 6 byte cdb
variants are used. RBC and old SCSI devices may need this option. This
utility outputs a suggestion to use this option if the SCSI status indicates
that the 10 byte cdb variant is not supported.
The SPC-4 standard (and SPC-5 drafts) include a note stating that
implementers migrate away from the SCSI MODE SELECT(6) and MODE SENSE(6)
commands in favour of the 10 byte variants (e.g. MODE SEMSE(10)).
- -t, --transport=TN
-
Specifies the transport protocol where TN is either a number in the
range 0 to 15 (inclusive) or an abbreviation (e.g. "fcp" for the Fibre
Channel Protocol). Some transports accept multiple abbreviations, for example
srp (SCSI RDMA Protocol) and ib (short for InfiniBand) both are accepted for
transport protocol 0x4 . Also both upper and lower case are accepted so iscsi
and iSCSI are accepted for transport protocol 0x5 . One way to list available
transport protocols numbers and their associated abbreviations is to give an
invalid transport protocol name such as '-t x'; another way is '-e -l'.
N.B. The --all option may still be needed to show all available
fields.
- -M, --vendor=VN
-
Specifies the vendor (i.e. manufacturer) where VN is either a number (0
or more) or an abbreviation (e.g. "sea" for Seagate disk vendor specific).
For tape drives "lto5" and "lto6" are treated as vendors. One way to list
the available vendor numbers and their associated abbreviations is to give an
invalid vendor number such as '-M x'; another way is '-e -l'.
This option only effects mode page decodes, not VPD pages. For vendor
specific VPD pages see the sg_vpd utility.
- -v, --verbose
-
increase the level of verbosity, (i.e. debug output). In some cases
more decoding is done (e.g. fields within a standard INQUIRY response).
- -V, --version
-
print the version string and then exit.
- -w, --wscan
-
this option is available in Windows only. It lists storage device names
and the corresponding volumes, if any. When used twice it adds the "bus
type" of the closest transport (e.g. a SATA disk in a USB connected
enclosure has bus type Usb). When used three times a SCSI adapter scan
is added. When used four times only a SCSI adapter scan is shown.
See examples below and the "Win32 port" section in the README file.
NOTES
The reference document used for interpreting mode and VPD pages (and the
INQUIRY standard response) is T10/BSR INCITS 502 Revision 17 (SPC-5, 19
September 2017) found at http://www.t10.org . Obsolete and reserved items
in the standard INQUIRY response output are displayed in brackets. Recent
drafts of other T10 documents are also used: SBC-4 (disks), SSC-5 (tapes),
SPL-5 (SAS transport) and SAT-4 (SCSI to ATA Translation).
A mode page for which no abbreviation is known (e.g. a vendor specific mode
page) can be listed in hexadecimal by using the option
combination '--page=PG --hex'.
Numbers input to sdparm (e.g. in the command line arguments) are assumed
to be in decimal unless there is a hexadecimal indicator. A hexadecimal
indicator is either a leading '0x' or '0X' (i.e. the C language convention)
or a trailing 'h' or 'H' (i.e. the convention used at www.t10.org ). In
the case of --page= either a string or number is expected, so hex
numbers like 'ch' (12) should be prefixed by a zero (e.g. '0ch').
The SPC-4 draft (rev 2) says that devices that implement no
distinction between current and saved pages can return an
error (ILLEGAL REQUEST, invalid field in cdb) if the SP bit (which
corresponds to the --save option) is _not_ set. In such cases
the --save option needs to be given.
If the --save option is given but the existing mode page indicates (via
its PS bit) that the page is not saveable, then this utility generates
an error message. That message suggests to try again without the
--save option.
Since the device identification VPD page (acronym_name "di") potentially
contains a lot of diverse designators, several associated acronyms are
available. They are "di_lu" for designators associated with the
addressed logical unit, "di_port" for designators associated with the
target port (which the command arrived via) and "di_target" for
designators associated with the target device. When "di" is used
designators are grouped by lu, then port and then target device.
To see all designators decoded in the order that they appear in the
VPD page use "di_asis".
Only those VPD pages defined by t10.org are decoded by this utility. SPC-4
sets aside VPD pages codes from 0xc0 to 0xff (inclusive) for vendor
specific pages some of which are decoded in the sg_vpd utility.
To see all VPD pages supported by a DEVICE use 'sg_vpd --all'.
In the linux kernel 2.6 and 3 series any device node that understands a SCSI
command set (e.g. SCSI disks and CD/DVD drives) may be specified. More
precisely the driver that "owns" the device node must support the SG_IO
ioctl. In the lk 2.4 series only SCSI generic (sg) device nodes support
the SG_IO ioctl. However in the lk 2.4 series other SCSI device nodes are
mapped within this utility to their corresponding sg device nodes. So if
there is a SCSI disk at /dev/sda then 'sdparm /dev/sda' will work in both
the lk 2.4 series and later. However if there is an ATAPI cd/dvd drive
at /dev/hdc then 'sdparm /dev/hdc' will only work in the lk 2.6 series
and later.
In the Linux 2.6 and 3 series, especially with ATA disks, using sdparm to
stop (spin down) a disk may not be sufficient and other mechanisms will
start the disk again some time later. The user might additionally mark
the disk as "offline" with 'echo offline > /sys/block/sda/device/state'
where sda is the block name of the disk. To restart the disk "offline"
can be replaced with "running".
PARAMETERS
In their simplest form the --clear=, --get= and
--set= options (or their short forms) take an acronym_name such
as "WCE". In the case of '--get=WCE' the value of "Writeback Cache Enable"
in the caching mode page will be fetched. In the case of '--set=WCE'
that bit will be set (to one). In the case of '--clear=WCE' that bit
will be cleared (to zero). When an acronym_name is given then the mode page
is imputed from that acronym_name (e.g. WCE is in the caching mode page).
Instead of an acronym_name a field within a mode page can be described
numerically with a <start_byte>:<start_bit>:<num_bits> tuple. These
are the <start_byte> (origin 0) within the mode page, a <start_bit> (0 to
7 inclusive) and <num_bits> (1 to 64 inclusive). For example, the low level
representation of the RCD bit (the "Read Cache Disable bit in the caching
mode page) is "2:0:1". The <start_byte> can optionally be given in
hex (e.g. '--set=0x2:0:1' or '--set=2h:0:1'). With this form the
--page= option is required to establish which mode page is to be
used.
Either form can optionally be followed by "=<val>". By default <val> is
decimal but can be given in hex in the normal fashion. Here are some
examples: '--set=2h:0:1=1h' and '-s MRIE=0x3'. When the acronym_name
or numeric form following --clear= is not given an explicit '=<val>'
then the value defaults to zero. When the acronym_name or numeric form
following --set= is not given an explicit '=<val>' then the value
defaults to "all ones" (i.e. as many as <num_bits> permits). For
example '--clear=WCE' and '--clear=WCE=0' have the same meaning: clear
Writeback Cache Enable or, put more simply: turn off the writeback cache.
Multiple fields within the same mode page can be changed by giving a comma
separated list of acronym_names and/or the numerical form. For
example: '--set=TEST,MRIE=6'.
Some mode page have multiple descriptors. They typically have a fixed header
section at the start of the mode page that includes a field containing the
number of descriptors that follow. Following the header is a variable number
of descriptors. An example is the SAS Phy Control and Discover mode page. An
acronym_name may include a trailing '.<num>' where "<num>" is a descriptor
number (origin 0). For example '-t sas -g PHID.0' and '-t sas -g PHID'
will yield the phy identifier of the first descriptor of the above mode
page; '-t sas -g PHID.1' will yield the phy identifier of the second
descriptor.
ENUMERATE
The --enumerate option essentially dumps out static information held
by this utility. A list of --enumerate variants and their actions
follows. For brevity subsequent examples of options are shown in their
shorter form.
--enumerate list generic mode page information
-e --all list generic mode page contents
(i.e. parameters)
-e --page=rw list contents of read write error
recovery mode page
-e --inquiry list VPD pages this utility can decode
-e --long list generic mode pages, transport
protocols, mode pages for each
supported transport protocol and
supported commands
-e -l --all additionally list the contents of
each mode page
-e --transport=fcp list mode pages for the fcp
transport protocol
-e -t fcp --all additionally list the contents of
each mode page
-e --vendor=sea list vendor specific mode pages for
"sea" (Seagate)
-e -M sea --all additionally list the contents of vendor
specific mode pages for "sea" (Seagate)
-e -p pcd -l list contents of SAS phy control and
discovery mode page plus (due to "-l")
some descfriptor format information
When known mode pages are listed (via the --enumerate option) each
line starts with a two or three letter abbreviation. This is followed by
the page number (in hex prefixed by "0x") optionally followed by a
comma and the subpage number. Finally the descriptive name of the mode
page (e.g. as found in SPC-4) is output.
When known parameters (fields) of a mode page are listed, each line
starts with an acronym (indented a few spaces). This will match (or
be an acronym for) the description for that field found in the (draft)
standards. Next are three numbers, separated by colons, surrounded by
brackets. These are the start byte (in hex, prefixed by "0x") of the
beginning of the field within the mode page; the starting bit (0 through 7
inclusive) and then the number of bits. The descriptive name of the
parameter (field) is then given. If appropriate the descriptive name
includes units (e.g. "(ms)" means the units are milliseconds). Adding
the '-ll' option will list information about possible field values
for selected mode page parameters.
Mode parameters for which the num_bits is greater than 1 can be
viewed as unsigned integers. Often 16 and 32 bit fields are set
to 0xffff and 0xffffffff respectively (all ones) which usually
has a special meaning (see drafts). This utility outputs such values
as "-1" to save space (rather than their unsigned integer
equivalents). "-1" can also be given as the value to a mode page
field acronym (e.g. '--set=INTT=-1' sets the interval timer field
in the Informational Exceptions control mode page to 0xffffffff).
TRANSPORTS
SCSI transport protocols are a relatively specialized area
that can be safely ignored by the majority of users.
Some transport protocols have protocol specific mode pages. These are usually
the disconnect-reconnect (0x2), the protocol specific logical unit (0x18)
and the protocol specific port (0x19) mode pages. In some cases the latter
mode page has several subpages. The most common transport protocol
abbreviations likely to be used are "fcp", "spi" and "sas".
Many of the field names are re-used in the same position so the acronym_name
namespaces have been divided between generic mode pages (i.e. when the
--transport= option is _not_ given) and a namespace for each
transport protocol. A LUPID field from the protocol specific logical
unit (0x18) mode page and the PPID field from protocol specific
port (0x19) mode page are included in the generic modes pages; this is so
the respective (transport) protocol identifiers can be seen. In most cases
the user will know what the "port" transport is (i.e. the same transport as
the HBA in the computer) but the logical unit's transport could be different.
VENDORS
SCSI leaves a lot of space for vendor specific information. Often this is
described in product manuals. The --vendor=VN (or -M=VN)
option allows known vendor specific mode pages to be examined and/or
modified by acronym.
In this utility the syntax and semantics of vendor specific
mode pages is very similar to those of transport protocol specific
mode pages. Both cannot be specified together. Vendor specific
modes pages can still be accessed numerically (as shown at the
end of the EXAMPLES section).
COMMANDS
The command option sends a SCSI command to the DEVICE. If the
command fails then this is reflected in the non-zero exit status.
To obtain more information about the error use the -v option.
- capacity
-
sends a READ CAPACITY(10) command (valid for disks and cd/dvd media) by
default. If successful yields "blocks: " [the number of
blocks], "block_length: " [typically either 512 or 2048]
and "capacity_mib: " [capacity in MibiBytes (1048576 byte units)].
If the number of blocks is too large to fit in the 4 byte field provided
by READ CAPACITY(10) or, the --long option is given, then the
READ CAPACITY(16) command is sent. If the --long option is given,
then the extra fields found in the READ CAPACITY(16) response are output.
- eject
-
stops the medium and ejects it from the device.
Note that ejection (by command or button) may be prevented in which case
the 'unlock' command may be useful in extreme cases.
Typically only appropriate for cd/dvd drives and disk drives with removable
media. Objects if sent to another peripheral device type (but objection
can be overridden with '-f' option).
- load
-
loads the medium and starts it (i.e. spins it up). See 'eject' command for
supported device types.
- profile
-
lists the various formats that a CD/DVD/HD-DVD/BD drive supports. These are
called "profiles" in the MMC standard. The profiles are listed one per line.
If media is in the drive then the profile that matches the media (if any)
has an "*" to the right of the line.
- ready
-
sends the "Test Unit Ready" SCSI command to the
DEVICE. No error is reported if the device will respond to data
requests (e.g. READ) in a reasonable timescale. For example, if a disk
is stopped then it will report "not ready". All devices should respond
to this command.
- sense
-
sends a REQUEST SENSE command. It reports a hardware
threshold exceeded, warning or low power condition if flagged. If a progress
indication is present (e.g. during a format) then it will be output as a
percentage. Yields a process status of 0 if the command succeeds and the
sense key is 0; else yields 1. The --quiet option can be used to
lessen output, and --hex to output sense data in hex.
- speed=SPEED
-
permits the speed of a CD, DVD, HD_DVD or BD disc in a drive to be set (or
at least influenced). It has this format: --command=speed=SPEED
where SPEED is in kilobytes per second. In this case a kilobyte is 1000
bytes. The "times one" speed for a CD is 176.4 kB/s, for a DVD is
1350 kB/s and for both HD-DVD and BD it is 4500 kB/s. If SPEED is zero then
the drive is set to the speed that it considers gives optimal performance.
This command sends a SET STREAMING multi-media command (MMC) to the drive.
The EXACT bit is clear so the drive will round the given SPEED as necessary.
The command is designed to control read speed; setting write speed should
be left to "burning" programs.
- start
-
starts the medium (i.e. spins it up). Harmless if medium has already been
started. See 'eject' command for supported device types. If the DEVICE
is an ATA disk in Linux the '--readonly' option may be required.
- stop
-
stops the medium (i.e. spins it down). Harmless if
medium has already been stopped. See 'eject' command for supported device
types. If the DEVICE is an ATA disk in Linux the '--readonly'
option may be required. See the NOTES section above.
- sync
-
sends a SYNCHRONIZE CACHE command. The device should
flush any data held in its (volatile) buffers to the media.
- unlock
-
tells a device to allow medium removal. It uses the SCSI "prevent allow
medium removal" command. This is desperation stuff, possibly overriding a
prevention applied by the OS on a mounted file system. The "eject" utility
(from the "eject" package) is more graceful and should be tried first. This
command is only appropriate for devices with removable media.
For loading and ejecting tapes the mt utility should be used (i.e. not
these commands). The 'ready' command is valid for tape devices.
EXAMPLES
To list the common (generic) mode parameters of a disk:
sdparm /dev/sda
To list the designators within the device identification VPD page
of a disk:
sdparm --inquiry /dev/sda
To see all parameters for the caching mode page:
sdparm --page=ca /dev/sda
To see all parameters for the caching mode page
with parameter descriptions to the right:
sdparm --page=ca --long /dev/sda
To get the WCE values (current changeable default and saved) in hex:
sdparm -g WCE -H /dev/sda
0x01 0x00 0x01 0x01
To get the WCE current value in hex:
sdparm -g WCE=1 -H /dev/sda
0x01
To set the "Writeback Cache Enable" bit in the current values page:
sdparm --set=WCE /dev/sda
To set the "Writeback Cache Enable" bit in the current and saved values page:
sdparm --set=WCE --save /dev/sda
To set the "Writeback Cache Enable" and clear "Read Cache Disable":
sdparm --set=WCE --clear=RCD --save /dev/sda
The previous example can also by written as:
sdparm -s WCE=1,RCD=0 -S /dev/sda
To re-establish the manufacturer's defaults in the current and saved
values of the caching mode page:
sdparm --page=ca --defaults --save /dev/sda
If an ATAPI cd/dvd drive is at /dev/hdc then its common (mode) parameters
could be listed in the lk 2.6 and 3 series with:
sdparm /dev/hdc
If there is a DVD in the drive at /dev/hdc then it could be ejected in the
lk 2.6 and 3 series with:
sdparm --command=eject /dev/hdc
If the ejection is being prevented by software then that can be
overridden with:
sdparm --command=unlock /dev/hdc
One disk vendor has a "Performance Mode" bit (PM) in the vendor specific
unit attention mode page [0x0,0x0]. PM=0 is server mode (the default)
while PM=1 is desktop mode. Desktop mode can be set (both current and
saved values) with:
sdparm --page=0 --set=2:7:1=1 --save /dev/sda
The resultant change can be viewed in hex with the --hex option as
there are no acronyms for vendor extensions yet. The PM bit is now covered
by vendor specific mode pages and the above can also be accomplished with:
sdparm --vendor=sea --set=PM --save /dev/sda
What follows are some examples from Windows using the '--wscan' option.
The idea is to list the storage device names on the system that might be
invoked by other uses of sdparm.
# sdparm --wscan
PD0 [C] FUJITSU MHY2160BH 0000
PD1 [DF] WD 2500BEV External 1.05 WD-WXE90
CDROM0 [E] MATSHITA DVD/CDRW UJDA775 CB03
So 'sdparm -a CDROM0' and 'sdparm -a E' will show all the (known) mode page
fields for the Matshita DVD/CD drive. By using the '--wscan' option twice,
the bus type (as seen by the OS) is added to the output:
# sdparm -ww
PD0 [C] <Ata > FUJITSU MHY2160BH 0000
PD1 [DF] <Usb > WD 2500BEV External 1.05 WD-WXE90
CDROM0 [E] <Atapi> MATSHITA DVD/CDRW UJDA775 CB03
And the pattern continues to add a SCSI adapter scan. This may be useful
if there are specialized storage related devices (e.g. a SES device in
an enclosure) but does add much extra information in this case.
# sdparm -www
PD0 [C] <Ata > FUJITSU MHY2160BH 0000
PD1 [DF] <Usb > WD 2500BEV External 1.05 WD-WXE90
CDROM0 [E] <Atapi> MATSHITA DVD/CDRW UJDA775 CB03
SCSI0:0,0,0 claimed=1 pdt=0h FUJITSU MHY2160BH 0000
SCSI1:0,0,0 claimed=1 pdt=5h MATSHITA DVD/CDRW UJDA775 CB03
EXIT STATUS
To aid scripts that call sdparm, the exit status is set to indicate
success (0) or failure (1 or more). Note that some of the lower values
correspond to the SCSI sense key values. The exit status values are:
- 0
-
success
- 1
-
syntax error. Either illegal command line options, options with bad
arguments or a combination of options that is not permitted.
- 2
-
the DEVICE reports that it is not ready for the operation
requested. The device may be in the process of becoming ready (e.g.
spinning up but not at speed) so the utility may work after a wait.
- 3
-
the DEVICE reports a medium or hardware error (or a blank
check). For example an attempt to read a corrupted block on a disk
will yield this value.
- 5
-
the DEVICE reports an "illegal request" with an additional
sense code other than "invalid operation code". This is often a
supported command with a field set requesting an unsupported
capability. For commands that require a "service action" field
this value can indicate that the command is not supported.
- 6
-
the DEVICE reports a "unit attention" condition. This usually
indicates that something unrelated to the requested command has
occurred (e.g. a device reset) potentially before the current SCSI
command was sent. The requested command has not been executed by the
device. Note that unit attention conditions are usually only reported
once by a device.
- 7
-
the DEVICE reports a "data protect" sense key. This implies some
mechanism has blocked writes (or possibly all access to the media).
- 9
-
the DEVICE reports an illegal request with an additional
sense code of "invalid operation code" which means that it doesn't
support the requested command.
- 10
-
the DEVICE reports a "copy aborted". This implies another command or
device problem has stopped a copy operation. The EXTENDED COPY family of
commands (including WRITE USING TOKEN) may return this sense key.
- 11
-
the DEVICE reports an aborted command. In some cases aborted
commands can be retried immediately (e.g. if the transport aborted
the command due to congestion).
- 14
-
the DEVICE reports a miscompare sense key. VERIFY and COMPARE AND
WRITE commands may report this.
- 15
-
the utility is unable to open, close or use the given DEVICE.
The given file name could be incorrect or there may be permission
problems. Adding the -v option may give more information.
- 20
-
the DEVICE reports it has a check condition but "no sense".
Some polling commands (e.g. REQUEST SENSE) can react this way.
It is unlikely that this value will occur as an exit status.
- 21
-
the DEVICE reports a "recovered error". The requested command
was successful. Most likely a utility will report a recovered error
to stderr and continue, probably leaving the utility with an exit
status of 0 .
- 22
-
the DEVICE reports that the current command or its parameters imply
a logical block address (LBA) that is out of range.
- 24
-
the DEVICE reports a SCSI status of "reservation conflict". This
means access to the DEVICE with the current command has been blocked
because another machine (HBA or SCSI "initiator") holds a reservation on
this DEVICE. On modern SCSI systems this is related to the use of
the PERSISTENT RESERVATION family of commands.
- 25
-
the DEVICE reports a SCSI status of "condition met". Currently only
the PRE-FETCH command (see SBC-4) yields this status.
- 26
-
the DEVICE reports a SCSI status of "busy". SAM-5 defines this
status as the logical unit is temporarily unable to process a command.
It is recommended to re-issue the command.
- 27
-
the DEVICE reports a SCSI status of "task set full".
- 28
-
the DEVICE reports a SCSI status of "ACA active". ACA is "auto
contingent allegiance" and is seldom used.
- 29
-
the DEVICE reports a SCSI status of "task aborted". SAM-5 says:
"This status shall be returned if a command is aborted by a command or task
management function on another I_T nexus and the Control mode page TAS bit
is set to one".
- 33
-
the command sent to DEVICE has timed out. This occurs in Linux
only; in other ports a command timeout will appear as a transport (or OS)
error.
- 40
-
the command sent to DEVICE has received an "aborted command" sense
key with an additional sense code of 0x10. This value is related to
problems with protection information (PI or DIF). For example this error
may occur when reading a block on a drive that has never been written (or
is unmapped) if that drive was formatted with type 1, 2 or 3 protection.
- 48
-
this is an internal message indicating a NVMe status field (SF) is other
than zero after a command has been executed (i.e. something went wrong).
Work in this area is currently experimental.
- 49
-
low level driver reports a response's residual count (i.e. number of bytes
actually received by HBA is 'requested_bytes - residual_count') that is
too high. So no useful processing can be done with that response.
- 50 + <os_error_number>
-
OS system calls that fail often return a small integer number to help
indicate what the error is. For example in Unix the inability of a system
call to allocate memory returns (in 'errno') ENOMEM which often is
associated with the integer 12. So 62 (i.e. '50 + 12') may be returned
by a utility in this case.
- 97
-
the response to a SCSI command failed sanity checks.
- 98
-
the DEVICE reports it has a check condition but the error
doesn't fit into any of the above categories.
- 99
-
any errors that can't be categorized into values 1 to 98 may yield
this value. This includes transport and operating system errors
after the command has been sent to the device.
- 126
-
the utility was found but could not be executed. That might occur if the
executable does not have execute permissions.
- 127
-
This is the exit status for utility not found. That might occur when a
script calls a utility in this package but the PATH environment variable
has not been properly set up, so the script cannot find the executable.
- 128 + <signum>
-
If a signal kills a utility then the exit status is 128 plus the signal
number. For example if a segmentation fault occurs then a utility is
typically killed by SIGSEGV which according to 'man 7 signal' has an
associated signal number of 11; so the exit status will be 139 .
- 255
-
the utility tried to yield an exit status of 255 or larger. That should
not happen; given here for completeness.
Most of the error conditions reported above will be repeatable (an
example of one that is not is "unit attention") so the utility can
be run again with the -v option (or several) to obtain more
information.
AUTHORS
Written by Douglas Gilbert.
REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>.
COPYRIGHT
Copyright © 2005-2021 Douglas Gilbert
This software is distributed under a FreeBSD license. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
WEB SITE
There is a web page discussing this package at
https://sg.danny.cz/sg/sdparm.html .

Time: 15:25:32 GMT, April 23, 2021


You want to ensure that MoSKito runs in your Environment? We will handle it.
SLAs on MoSKito Tools: If something doesn't run, we guarantee to fix it within 3 working days
2 Business days reaction time
Help with initial setup on mail, skype, phone, jabber - you name it
Phone support
In this package we are not only giving away the tool-support, but also our knowledge of the applications, how to discover them, how to understand them and how to make them manageable. This includes
Everything from the basic package
Initial setup with hands-on in your environment and, if requested, on site
A check-up twice a year, containing review of your tool usage, hints and tips
Workshops on effective application management with MoSKito


Rows
Element 0
Delete
not me
Element 1
Delete
me neither
Element 2
Delete
chosen
Element 3
Delete
not me either


DNA Helix
Write a program that prints a DNA helix with length, specified by the user.
Enter rows:
Example: 4
Print DNA


Defines whether to check for the presence of ferrite prior to TTT/CCT calculations.
int jmpSetFerriteCheck (int booleanFlag);
booleanFlag [input]
Integer that specifies whether to check for the presence of ferrite at the austenitisation temperature before calculating TTT/CCT diagrams. Possible values are JMP_FLAG_TRUE
or JMP_FLAG_FALSE
. If set to JMP_FLAG_TRUE
, the check will be performed and the calculation will proceed only if ferrite is not found. If set to JMP_FLAG_FALSE
, the check will not be performed and the calculation will always run. In any case, the calculation is based on the austenite composition at the austenitisation temperature, assuming austenite is the only phase present at the beginning.
JMP_STATUS_OK |
Request has been successfully completed. |
JMP_STATUS_ERROR |
An error has occurred. |
| Header | jmpcore.h |
| Library | jmpcore.lib /jmpcore_x64.lib |
| DLL | jmpcore.dll /jmpcore_x64.dll |


In this website is will go over the best methods to catch fish in The Green/Duwamish river systems. I will also go over basic rules and regulations that everyone should know.
clickThats me with one of my first coho salmon, that I caught on the Duwamish this year. Using these methods you can catch some too!
Fishing with salmon eggs is the most used method on the Green and Duwamish river systems. You can use eggs by floating them on a bobber, or drifting them with a light weight and a 4-6 foot leader. Fishing with eggs works best during low tide.
Spinners are also very effective on this river. i recommend using blue fox #4, mepps flying c, and mepps aglia spinners. I recomend flashy and lighter colors like pink, red and orange; but they all work great. These work the best in calm areas of the river where fish are holding, and not during low tide.
Regulations change every year. Before fishing you need to check the regulations on the specific part of the river that you are going to fish at, because fish limits and regs change. Make sure to always fill out your catch card when you keep a fish. To find Regulations you can download the fish washington app, or go to https://wdfw.wa.gov/fishing


Extension points refer to the places from which Rexster can be extended and are defined by the @ExtensionDefinition
annotation which has an extensionPoint
parameter. This parameter must be defined on any method to be exposed as an extension on Rexster. The value of the extensionPoint
parameter is a selection from the ExtensionPoint
enumeration. The following extension point options are available:
| extension point | uri extends from |
|---|---|
| GRAPH | http://{base}/graphs/{graph} |
| EDGE | http://{base}/graphs/{graph}/edges/{id] |
| VERTEX | http://{base}/graphs/{graph}/vertices/{id} |
By default, the @ExtensionDefinition
assumes that the ExtensionResponse
will return an entity of type application/json
. To override that value, simply supply the revised mime-type to the produces
parameter, as in:
@ExtensionDefinition(extensionPoint = ExtensionPoint.VERTEX, produces = MediaType.APPLICATION_XML)
@ExtensionDescriptor(description = "Turn a vertex into XML")
public ExtensionResponse doVertexToXml(@RexsterContext Vertex vertex) {
String xml = "<vertex><id>" + vertex.getId().toString() + "</id></vertex>";
return new ExtensionResponse(Response.ok(xml).build());
}
The code above is taken from the ProducesXmlExtension
in the Sample Kibbles project.
When the extension method produces JSON, Rexster tries to add some standard attributes to the response. It will look to add the version
and queryTime
as in:
{
"some-key":"some-value",
"other-key":"other-value",
"version":"*.*",
"queryTime":24.940088
}
To override this default behavior, Rexster can be instructed to not add these values to JSON responses by setting the tryIncludeRexsterAttributes
on the ExtensionDefinition
to false
. As stated earlier, this value is true
by default. In the event that the produces
value is set to something other than application/json
, Rexster will behave as though the value of tryIncludeRexsterAttributes
is false
.
The ExtensionDefinition
provides control over the HTTP method on the request that it will respond to through the method
parameter:
@ExtensionDefinition(extensionPoint = ExtensionPoint.GRAPH, method = HttpMethod.GET)
In the above example, the specification of HttpMethod.GET
makes it so that Rexster will only relay GET
based requests to this method. The HttpMethod
enumeration has the full range of standard HTTP methods: GET, PUT, POST, DELETE, HEAD, and OPTIONS. It is up to the Extension developer to ensure that the returned response meets HTTP standards as necessary (ie. HEAD will not return and entity body). By default the value of method
is set to HttpMethod.ANY
which means that all requests, regardless of the HTTP method, will be funneled through to the Extension.
It’s important to note that when implementing methods other than GET or POST that you should also consider implementation of the OPTIONS method. Depending upon your environment, HTTP Access Control may come into play and prevent advanced methods like DELETE and PUT from working properly. Typically, this scenario occurs when cross-site HTTP requests are made and requests to the extension are met with an error like:
Method DELETE is not allowed by Access-Control-Allow-Methods
ExtensionResponse
helper class has a static method called availableOptions
to help construct the required response.
By default, Rexster will auto-commit a transaction with success if the extension method returns a non-error ExtensionResponse
. If the ExtensionResponse
is an error or the extension throws an untrapped exception it will auto-commit with failure.
To turn off this behavior, set the autoCommitTransaction
value on the ExtensionDefinition
to false
. When set to false, the extension method itself is responsible for committing transaction, though untrapped exceptions will still commit with failure.
There are multiple types of extensions. The type of extension is driven by a combination of the settings in the ExtensionDefinition
.
| type | defined by |
|---|---|
| Root | An ExtensionDefinition defined with an ExtensionPoint of GRAPH , VERTEX or EDGE with no path. |
| Path | An ExtensionDefinition defined with an ExtensionPoint of GRAPH , VERTEX or EDGE and a specified path. |
Consider the following code snippet from the SimpleRootExtension
extension class in the Sample Kibbles project:
ExtensionNaming(name = SimpleRootExtension.EXTENSION_NAME, namespace = SimpleRootExtension.EXTENSION_NAMESPACE)
public class SimpleRootExtension extends AbstractRexsterExtension {
public static final String EXTENSION_NAME = "simple-root";
public static final String EXTENSION_NAMESPACE = "tp";
@ExtensionDefinition(extensionPoint = ExtensionPoint.GRAPH)
@ExtensionDescriptor(description = "Do something on graph")
public ExtensionResponse doWorkOnGraph(@RexsterContext Graph graph) {
return toStringIt(graph);
}
}
will serve at:
http://{base}/graphs/{graph}/tp/simple-root
When defining an ExtensionDefinition
in this way, it is referred to as a “root extension” where the extension serves from the root of the ExtensionPoint
. A single root extension can be defined for a single extension point within a method, namespace and extension class. Therefore, the following extension would not be valid:
ExtensionNaming(name = SimpleRootExtension.EXTENSION_NAME, namespace = SimpleRootExtension.EXTENSION_NAMESPACE)
public class SimpleRootExtension extends AbstractRexsterExtension {
public static final String EXTENSION_NAME = "simple-root";
public static final String EXTENSION_NAMESPACE = "tp";
@ExtensionDefinition(extensionPoint = ExtensionPoint.GRAPH)
@ExtensionDescriptor(description = "Do something on the graph")
public ExtensionResponse doWorkOnGraph(@RexsterContext Graph graph) {
return toStringIt(graph);
}
@ExtensionDefinition(extensionPoint = ExtensionPoint.GRAPH)
@ExtensionDescriptor(description = "Do some more stuff on the graph")
public ExtensionResponse doWorkSomeNonsenseWorkOnGraph(@RexsterContext Graph graph) {
// DON'T INCLUDE TWO METHODS THAT EXTEND FROM THE SAME EXTENSIONPOINT
// UNLESS SPECIFYING A PATH EXTENSION (described below)
return toStringIt(graph.getVertex(1));
}
}
While Rexster does not complain if it comes across the above scenario, it may not behave as expected. Rexster will simply choose the first and best method match to the request.
In addition to root extensions, there are also path extensions. Path extensions allow an extension to have multiple service methods exposed from the same namespace, extension name and extension point. Consider the following code snippet from the SimplePathExtension
extension class in Sample Kibbles project:
@ExtensionNaming(name = SimplePathExtension.EXTENSION_NAME, namespace = SimplePathExtension.EXTENSION_NAMESPACE)
public class SimplePathExtension extends AbstractRexsterExtension {
public static final String EXTENSION_NAME = "simple-path";
public static final String EXTENSION_NAMESPACE = "tp";
@ExtensionDefinition(extensionPoint = ExtensionPoint.GRAPH, path = "some-work")
@ExtensionDescriptor(description = "Do something on the graph")
public ExtensionResponse doSomeWorkOnGraph(@RexsterContext Graph graph) {
return toStringIt(graph, "some");
}
@ExtensionDefinition(extensionPoint = ExtensionPoint.GRAPH, path = "other-work")
@ExtensionDescriptor(description = "Do more stuff on the graph")
public ExtensionResponse doOtherWorkOnGraph(@RexsterContext Graph graph){
return toStringIt(graph, "other");
}
}
Note that there are two ExtensionDefinition
annotations on two different methods that both specify the ExtensionPoint.GRAPH
. It was previously established in the root extension section that this specification is not permitted, however, the difference here is the usage of the path
parameter on the annotation. The value of the path
parameter helps to identify the method to be exposed on the extension, such that Rexster will serve those methods on the following URIs:
http://{base}/graphs/{graph}/tp/simple-path/some-work
http://{base}/graphs/{graph}/tp/simple-path/other-work
Like the root extension, the path extension will behave inconsistenly if there is more than one method on the extension that has the same namespace, extension name, extension point, method and path. Rexster will always serve the first method to match the request.


#include <stPageCache.h>
Public Member Functions | |
| virtual stPage * | Get (stPageID pageID)=0 |
| virtual void | SetModified (stPageID pageID)=0 |
| virtual stPage * | Add (stPage *page, bool &modified)=0 |
| virtual stPage * | Pop (bool &modified)=0 |
This class defines the basic interface for all page caches used by page manager implementations.
A cache is not suposed to destroy, create, read or write pages because it acts as an associative memory only. In other words, the hard work must be performed by the page manager.
Description of the usage is missing!!!
Definition at line 102 of file stPageCache.h.
Adds a new page into the cache. It may return the instance of the page that must be removed from the cache.
Returns a page with a given page id.
| pageID | The given page id. |
|
pure virtual |
Removes a page from the cache. This method must be used by page managers to flush all pages in the cache before its destruction.
| A | flag that tells if the returned page was modified since it was read for the first time. |
|
pure virtual |
Notifies the cache that a given page was modified. If the page is not registered in the cache, this method does nothing.


Facebook tests Instagram feed-like feature called "Popular Photos"
by SagarWhen you are watching a video on the Facebook app in full-screen mode and scroll down, you see videos recommended by Facebook. Well, according to a recent report, you might soon get a similar experience for photos as well, since the social network built a feature for images called "Popular Photos".
In the current setting, when you tap on a photo, you enter the full-screen mode with a black background. And when you scroll down or swipe on it, you are taken back.
But with the Popular Photos feature, you will now see more pictures from your friends and other public posts by scrolling down which will be curated for you by Facebook's algorithm, thus giving you an Instagram feed-like experience.
Facebook also ensured that photo captions don't look wordy by truncating them after 65 characters.
The social network confirmed to TechCrunch that testing of Popular Photos has concluded, but didn't reveal more details about it or share a timeline for its rollout.


My Team
Aaron D
Manager
ID: 1
Email:
<EMAIL_ADDRESS>Office number: 1200
Roger D
Engineer
ID: 2
Email:
<EMAIL_ADDRESS>GitHub:
rogerd
Kerwin D
Intern
ID: 3
Email:
<EMAIL_ADDRESS>School: UC Berkeley


What learnings did you take from the chapter?
Emotional intelligence is essential within a workplace / group, if maximum working-potential is to be achieved. Being self-aware,
empathetic, towards other people's emotions -- in general, just being mindful -- is important to
not only them, but to yourself and the success of a team.
"The aim of developing emotional intelligence is to help you optimise yourself and function at an
even higher level than what you are already capable of."
In that, emotional intelligence can be seen as supplementary to what you already know / can do;
it gives you an additional "edge" as a person and professional.
How did you find the two minutes of mindfulness?
Pretty difficult -- easy for your mind to wander / hard to re-focus. There is a sense of relaxation / de-stress, but I'm
going to attempt at later at night after unwinding, to see if I find it easier.
Can see how this practice of mindfulness -- even for two-minutes -- can be a good habit to get into.
Personally, I find doing completely nothing, other than listening to music perfect for me.


‘Mindhunter’ Season 3 won’t be out until David Fincher finishes his next film
'Mank' will come out in 2020
Season 3 of Mindhunter is set to have to wait until director David Fincher has finished his next movie.
The director is currently at work on Mank, a film by his late father.
Mank is due out next year, and according to a profile of Mindhunter star Jonathan Groff in The Hollywood Reporter, work on the film is putting the brakes on a third season of the Netflix series for now.
During the interview, it’s reported that “talk of a third season of Mindhunter is on hold while Fincher focuses on his next feature.”
Holden Ford and Bill Tench in Mindhunter
A third season of Mindhunter has never been confirmed by Netflix, but Fincher has previously said that he expects the show to run for five seasons or more.
Holt McCallany, who plays Groff’s co-star Bill Tench on the show, spoke to THR about the future of the show, and revealed that Fincher has grand plans for Mindhunter.
“He said ‘Listen, are you ready to do this for five seasons?
“So I’d like to think that we will continue, for as long as David is intrigued by telling this particular story.”
Season 2 of Mindhunter concluded in August with a finale that NME’s Christopher Hooton called “the best episode of the show yet”.


I’m restarting my blog! It’s been a long time since I’ve last written a post.  Life has been busy, I have a 18 month old son. Work has been busy, isn’t for everyone? My old blogging platform, custom built Django setup, was horrible to write in. I could have made it all work if I made it a priority but I didn’t.
So I’m resetting. New look, new platform (Hugo), and new thoughts. I’m going to be writing more often about more topics. Some of the blog posts are going to be shorter, like this one. I’m going to be blogging about new topics like managing, data science & analysis, in addition to programming and any other thoughts that I have.
I hope you enjoy.


Classes, IDs, And The Right Way to Use CSS
This paragraph will be green
This paragraph will be green
This table
is green
with envy
This paragraph will be blue
This list
will be
centered


Notebooks
Story: The death of an aunt
The death of an aunt
Title
The death of an aunt
Collection
Summary
Tamme's (or possibly !nanni's) aunt was killed by elephants at night.  Tamme's mother cried and the father kills another person the next day.
Comments
1) This story is found in Book XI & XII-3
Contributors
Date
3 January 1879
Categories
Keywords
elephants (killed Tamme's or !nanni's aunt) , Tamme (an aunt killed by elephant) , Tamme (his relations) , Tamme (his personal history) , death (of aunt) , death (of !nanni or Tamme's aunt, killed by elephants) , personal history (an aunt killed by elephants) , !nanni (an aunt killed by elephant) , !nanni (his relations) , !nanni (his personal history)
Story Pages
9208-9210


JavaScript support and JQuery methods
Each UI element communicates with device via JQuery. It has its function based on its event and specified object data. The framework consists of JQuery methods that allows you to build your own scripts and UI kits. Custom script should be included in HTML head section (remember about JQuery .ready).
If you want to manipulate the element parameters you can use JQuery .data() to access them. These parameters are: pin, pinNumber, pinType, value, min, max, step, fn
Where are the values?
The current values of each pin to send to the device are stored in two arrays:
involtPin[index] contains the values of each P pin. Index is the number without the letter.
involtString[index] is for S pin and strings.
The values received from device are stored in involtReceivedPin[index] and contains both numeric values and strings.
It's important to use these arrays and update their values so the framework can be consistent. Their names are same as in arduino sketch.
JQuery methods
Most basic example of defining the target pin, updating its value in array and send it to device. You should use this pattern as much as possible if you want to mix custom events with involt UI kit.
For more examples check the Involt as JQuery plugin.
.pinDefine(pin)
Defines the pin for selected element (pin, pinNumber, pinType data). You don't have to use this method each time, just define this once.
.sendValue(value)
Send the value to defined pin. If value is not defined, it will send the value stored in involtPin or involtString array with index same as target pin. Remember that without the .updateValue() the corresponding pin value will not be updated.
.updateValue(value)
Update the value in Involt arrays to keep the values up to date for other elements. It's highly recommended to use it when sending the values. If value is not defined it will use object value data. Of course you can update the variable directly in array without using this method.
.pinSwap(newPin)
Similar to pinDefine but checks if there is defined pin value in involtPin[] array. If not - set it to previous pin value.
$(this).pinDefine("P6").updateValue(100).pinSwap("P7");
.sendFn(functionName)
Send function. If not defined, send the fn data
.sendAndUpdate(pin, value)
Shorthand for sending and updating pin and its value.//is equal to:
$(this).pinDefine("P6").updateValue(255).sendValue();
//and...
$(this).sendAndUpdate(255);
//is equal to:
$(this).updateValue(255).sendValue();
.sendString(rawString)
Send raw string to Arduino outside of framework. Use it only if you really have to. If you work only with data outside of framework but using its JQuery methods you don't have to use Involt sketch (or you can customize the receive function). The same rule applies to involt.send function.
Javascript functions
If you want to avoid JQuery you can use some JS functions from involt object. There are more functions included but establishing connection and communication is handled automatically and shouldn't be changed.
involt.arduinoSend(pin, value);
Send value to target pin.
involt.send(data)
Send raw value/string to device.
involt.arduinoFn(name);
Send function name to device.
Reading the data
There are no methods related to reading the values. The involtReceivedPin is updated automatically. It can be used with JQuery functions or interval based script.
$(".yourbutton").click(function() {
$("div").css('font-size', involtReceivedPin[0]);
});


|
|
static void | printLocalTime (time_t t=time(NULL)) |
| |
|
static void | printGmtTime (time_t t) |
| |
|
static void | stampLocalStream (std::ostream &out, time_t t=time(NULL)) |
| |
|
static void | stampGMTStream (std::ostream &out, time_t t) |
| |
|
static std::string | gmtStamp (time_t date) |
| |
|
static std::string | localStamp (time_t date) |
| |
|
static std::string | gmtDateStamp (time_t date) |
| |
|
static void | gmtDateStream (std::ostream &out, time_t date) |
| |
|
static int | getLocalHour (time_t t) |
| | Returns local hour.
|
| |
|
static std::string | elasticsearch (std::chrono::system_clock::time_point t) |
| | Elastic Search TimeStamp format.
|
| |
|
static std::string | elasticsearch (time_t t) |
| |
|
static std::string | elasticsearch (time_t t, int ms) |
| |
|
static time_t | elasticsearch (const std::string &timeString) |
| |
|
static time_t | yyyymmdd (const std::string &timeString) |
| |
|
static time_t | yyyymmdd (const unsigned int &dateNumber) |
| |
|
static std::string | log () |
| | Elastic Search TimeStamp format for precise logs with milliseconds.
|
| |
The documentation for this class was generated from the following files:
- source/toolkit/timestamp/timestamp.h
- source/toolkit/timestamp/timestamp.cpp


eToys(6) eToys(6) NAME eToys - a media-rich model, simulation construction kit and authoring tool SYNOPSIS etoys etoys [ option... ] DESCRIPTION Squeak Etoys was inspired by LOGO, PARC-Smalltalk, Hypercard, and starL‐ OGO. It is a media-rich authoring environment with a simple powerful scripted object model for many kinds of objects created by end-users that runs on many platforms, and is free and open source. It includes 2D and 3D graphics, images, text, particles, pres-entations, web-pages, videos, sound and MIDI, etc. It includes the ability to share desktops with other Etoy users in real-time, so many forms of immersive mentoring and play can be done over the Internet. The development of Squeak has been done inside the ViewPoint Research Institute for several years. Since last years it's being done in collabo‐ ration with the OLPC project. INVOCATION etoys has no options or arguments. Simply run it. There several environment variables that can be set for the Squeak vir‐ tual machine. Take a look at the squeakvm man page for more info. OPTIONS To know all the options, take a look at the Environment section of the squeakvm man page. ENVIRONMENT To know all the environment variables that can affect the squeak image launching, take a look at the Environment section of the squeakvm man page. AUTHOR This manual page was written by JosÃ© L. Redrejo for the Debian project SEE ALSO http://wiki.laptop.org/go/Etoys http://www.squeakland.org JosÃ© L. Redrejo RodrÃguez April 20, 2008 eToys(6)


Setting a fee lower than may result in a longer confirmation time.
{{signedHex}}
The change for this transaction , which is below the standard limit of . This is considered "non standard" and may result in delays propagating the transaction through the Bitcoin network.
You can choose to roll this small change amount (A.K.A. "dust") in with the transaction fee, to be collected by the Bitcoin node that mines this transaction.
Alternatively, you can choose to lower the fee used to send this transaction. This option will potentially cause the first confirmation to take longer than usual.
Finally, you can also choose to ignore this and send the transaction to the network, but propagation and confirmation may be delayed.


| 1 | package fr.sii.ogham.helper.sms; | |
| 2 | ||
| 3 | import static fr.sii.ogham.helper.sms.util.SmsUtils.getSmsContent; | |
| 4 | ||
| 5 | import java.util.List; | |
| 6 | ||
| 7 | import org.jsmpp.bean.SubmitSm; | |
| 8 | import org.junit.Assert; | |
| 9 | ||
| 10 | import fr.sii.ogham.helper.sms.jsmpp.SubmitSmAdapter; | |
| 11 | ||
| 12 | /** | |
| 13 | * Utility class for checking if the received SMS content is as expected. | |
| 14 | * | |
| 15 | * @author Aurélien Baudet | |
| 16 | * | |
| 17 | */ | |
| 18 | public class AssertSms { | |
| 19 | ||
| 20 | /** | |
| 21 | * Assert that the fields of the received SMS using SMPP protocol are equal | |
| 22 | * to the expected values. It will check that: | |
| 23 | *
 | |
| 24 | *
The received sender address corresponds to the expected phone number | |
| 25 | * of the sender
 | |
| 26 | *
The received receiver address corresponds to the expected phone | |
| 27 | * number of the receiver
 | |
| 28 | *
The received message corresponds to the expected message
 | |
| 29 | *
 | |
| 30 | * | |
| 31 | * @param expected | |
| 32 | * all the fields with their expected values | |
| 33 | * @param actual | |
| 34 | * the received SMS | |
| 35 | */ | |
| 36 | public static void assertEquals(ExpectedSms expected, SubmitSm actual) { | |
| 37 |
2
1. assertEquals : All method instructions removed → NO_COVERAGE 2. assertEquals : All method instructions removed → SURVIVED |
Assert.assertEquals("Sender number should be " + expected.getSenderNumber().getNumber(), expected.getSenderNumber().getNumber(), actual.getSourceAddr()); |
| 38 | Assert.assertEquals("Sender ton should be " + expected.getSenderNumber().getTon(), expected.getSenderNumber().getTon(), actual.getSourceAddrTon()); | |
| 39 | Assert.assertEquals("Sender npi should be " + expected.getSenderNumber().getNpi(), expected.getSenderNumber().getNpi(), actual.getSourceAddrNpi()); | |
| 40 | ||
| 41 | Assert.assertEquals("Receiver number should be " + expected.getReceiverNumber().getNumber(), expected.getReceiverNumber().getNumber(), actual.getDestAddress()); | |
| 42 | Assert.assertEquals("Receiver ton should be " + expected.getReceiverNumber().getTon(), expected.getReceiverNumber().getTon(), actual.getDestAddrTon()); | |
| 43 | Assert.assertEquals("Receiver npi should be " + expected.getReceiverNumber().getNpi(), expected.getReceiverNumber().getNpi(), actual.getDestAddrNpi()); | |
| 44 | ||
| 45 | Assert.assertEquals("Message not consistent with expected", expected.getMessage(), getSmsContent(new SubmitSmAdapter(actual))); | |
| 46 | } | |
| 47 | ||
| 48 | /** | |
| 49 | * Assert that the fields of the received SMS using SMPP protocol are equal | |
| 50 | * to the expected values. It will check that: | |
| 51 | *
 | |
| 52 | *
The received sender address corresponds to the expected phone number | |
| 53 | * of the sender
 | |
| 54 | *
The received receiver address corresponds to the expected phone | |
| 55 | * number of the receiver
 | |
| 56 | *
The received message corresponds to the expected message
 | |
| 57 | *
 | |
| 58 | *
 | |
| 59 | * It also checks that there is exactly one received message. | |
| 60 | *
 | |
| 61 | *
 | |
| 62 | * This is a shortcut useful in unit testing. | |
| 63 | *
 | |
| 64 | * | |
| 65 | * @param expected | |
| 66 | * all the fields with their expected values | |
| 67 | * @param receivedMessages | |
| 68 | * the list of received SMS | |
| 69 | */ | |
| 70 | public static void assertEquals(ExpectedSms expected, List<SubmitSm> receivedMessages) { | |
| 71 |
1
1. assertEquals : All method instructions removed → NO_COVERAGE |
Assert.assertEquals("should have received exactly one message", 1, receivedMessages.size()); |
| 72 | assertEquals(expected, receivedMessages.get(0)); | |
| 73 | } | |
| 74 | ||
| 75 | /** | |
| 76 | * Assert that the fields of each received SMS using SMPP protocol are equal | |
| 77 | * to values of each expected message. For each message, it will check that: | |
| 78 | *
 | |
| 79 | *
The received sender address corresponds to the expected phone number | |
| 80 | * of the sender
 | |
| 81 | *
The received receiver address corresponds to the expected phone | |
| 82 | * number of the receiver
 | |
| 83 | *
The received message corresponds to the expected message
 | |
| 84 | *
 | |
| 85 | *
 | |
| 86 | * It also checks that there are exactly the same number of received message | |
| 87 | * as the expected number. | |
| 88 | *
 | |
| 89 | * | |
| 90 | * @param expected | |
| 91 | * all the fields with their expected values | |
| 92 | * @param receivedMessages | |
| 93 | * the received SMS | |
| 94 | */ | |
| 95 | public static void assertEquals(List<ExpectedSms> expected, List<SubmitSm> receivedMessages) { | |
| 96 |
2
1. assertEquals : All method instructions removed → NO_COVERAGE 2. assertEquals : All method instructions removed → SURVIVED |
Assert.assertEquals("should have received exactly " + expected.size() + " messages", expected.size(), receivedMessages.size()); |
| 97 | for (int i = 0; i < expected.size(); i++) { | |
| 98 | assertEquals(expected.get(i), receivedMessages.get(i)); | |
| 99 | } | |
| 100 | } | |
| 101 | ||
| 102 | /** | |
| 103 | *
 | |
| 104 | * When message is too long, the SMS is split into several parts. This | |
| 105 | * method helps to check this case. | |
| 106 | *
 | |
| 107 | * Assert that the fields of each received SMS using SMPP protocol are equal | |
| 108 | * to values of each expected message part. For each message part, it will | |
| 109 | * check that: | |
| 110 | *
 | |
| 111 | *
The received sender address corresponds to the expected phone number | |
| 112 | * of the sender
 | |
| 113 | *
The received receiver address corresponds to the expected phone | |
| 114 | * number of the receiver
 | |
| 115 | *
The received message corresponds to the expected message
 | |
| 116 | *
 | |
| 117 | *
 | |
| 118 | * It also checks that there are exactly the same number of received message | |
| 119 | * as the expected number of parts. | |
| 120 | *
 | |
| 121 | * | |
| 122 | * @param expected | |
| 123 | * all the fields with their expected values | |
| 124 | * @param receivedMessages | |
| 125 | * the received SMS | |
| 126 | */ | |
| 127 | public static void assertEquals(SplitSms expected, List<SubmitSm> receivedMessages) { | |
| 128 |
1
1. assertEquals : All method instructions removed → NO_COVERAGE |
assertEquals(expected.getParts(), receivedMessages); |
| 129 | } | |
| 130 | ||
| 131 | private AssertSms() { | |
| 132 | super(); | |
| 133 | } | |
| 134 | } | |
Mutations | ||
| 37 |
1.1 2.2 |
|
| 71 |
1.1 |
|
| 96 |
1.1 2.2 |
|
| 128 |
1.1 |


--- layout: post title: 'Gnip CEO on the Challenges of Handling the Real-Time, Big Data Firehose' url: http://readwrite.com/2011/05/25/gnip-ceo-on-the-challenges-of source: http://readwrite.com/2011/05/25/gnip-ceo-on-the-challenges-of domain: readwrite.com image: http://kinlane-productions.s3.amazonaws.com/ap-evangelist-site/curated/screenshots/9352_api500_com.png ---
Last fall, Twitter announced a partnership with Gnip, making the latter company the only commercial provider of the Twitter activity stream.And although the firehose metaphor has been beaten to death, says Gnip CEO Jud Valeski, it still holds true.Valeski spoke today at Gluecon about the challenges of handling the firehose - what it means to process high volume, real-time data streams and to be able to do so in a consistent and predictable manner.Recent statistics demonstrate just how high a volume this Twitter data really is.Twitter is seeing around 155,000,000 tweets per day.


|
Perl Weekly
Issue #20 - 2011-12-12 - Beginner and Advanced Perl Maven video courses
latest | archive | by Gabor Szabo
|
|
Hi,
Two weeks ago I published the Beginner Perl Maven online video course. This week it was followed by the Advanced course and an a discount for a few days. See details below.
In other news, Best Practical, the company of Jesse Vincent, is looking for a Perl Hacker. See further in this issue.
And now to the links on by one...
|
|
|
Headlines
|
Advanced Perl Maven online video course
When I announced the course I offered a 81% discount for 3 days. I'd like to offer this discount to you, the reader of the Perl Weekly as well: Until the 15th December 2011 you'll be able to buy the advanced course for $9 instead of $49 using the 'advanced_intro_9' coupon. The two parts of the Beginner course also have discount codes: 'beginner_15' and 'beginner2_15' respectively for $15 instead of $39 each.
|
|
|
|
Perl Rocks Latin America
Mark Keating (MDK) writes about the W3C competition and about the only Perl team that participated. And won. Leaving 46 other teams wishing they had better tools.
|
|
Articles
|
use B::Stats to check for less bloat
Reini Urban gives us a couple of examples where little, innocent looking modules eat up a lot of memory. He also points to tools to check memory footprint. Memory optimization might be an important field we have been neglecting in the Perl/CPAN community. Or maybe it's just me.
|
|
Create your own dualvars
In Perl, every scalar variable has both a string value and a numerical value. Usually they are related. brian d foy shows how to create such variables using Scalar::Util.
|
|
rjbs versus Encode
It's always fascinating to see a fight between man and machine. This time it is Ricardo Signes (RJBS) who had to deal with Encode, folding and Tibetian e-mail messages.
|
|
|
|
How to parse HTML, part 2
If you have been following the posts of Jeffrey Kegler - and I saw many people clicked on those links - then you might be interested in the second part of this article.
|
|
Discussion
|
The Ten Minute Thinking Rule
I love the way Chisel explains how to get people to start thinking about a problem they face. It isn't always possible but I think it can work very well. Much better than saying RTFM or by giving them the solution.
|
|
Code
|
|
|
Using system or exec safely on Windows
Graham Knop, who almost never uses Perl on Windows, invested his time creating a way to escape all the characters that need to be escaped on Windows. This sounds a lot simpler than it is. I wish someone packaged this solution and put it on CPAN.
|
|
Other
|
YAPC::NA has a suggestion box that you can vote on
Usually I don't link to the small blog entries regarding next years YAPC::NA but this one I liked very much. 'Mob Rater' lets you suggest ideas for YAPC::NA and vote on the other ideas already listed. I think this is a nice idea and the results could be used by any YAPC or Perl workshop. So go ahead, put in your suggestions and vote on the other ones.
|
|
(vi) stackoverflow perl report
This weeks 'top 10 Perl on Stack Overflow' got some very interesting links. Thanks to Miguel Prz (niceperl) for collecting them week after week.
|
|
|
|
Events
|
|
|
|
|
|
|
|
|
You know, you could get the Perl Weekly right in your mailbox. Every Week. Free of charge!
|


The Razer Deathadder Elite is only $29 at Newegg right now
by Bill ThomasThe Razer Deathadder Elite is only $29 at Newegg right now
Get one of the best gaming mice for less
(Image credit: Razer)
The Razer Deathadder Elite is by far one of the most beloved gaming mice on the market. It's kind of the holy grail of mouse design, with a comfortable design build and just the right amount of buttons. And, you can save big ahead of Black Friday.
Right now at Newegg, you can get the Razer Deathadder Elite for just $29, much lower than its $69 list price. That's a massive 70% discount on one of the best gaming mice on the market.
The Razer Deathadder Elite is one of the most popular gaming mice out there, and for good reason. It's got a robust sensor, a comfortable build and the perfect amount of buttons. And, it's just $29 ahead of Black Friday.View Deal
Now, this mouse isn't packed with some of the more luxurious features you'll find in some other mice. It doesn't have as many buttons as something like the Razer Naga Trinity, and it's not wireless. But, when you just need a reliable gaming mouse that'll do its job, you can't really do much better than the Razer Deathadder Elite, especially when it's this cheap.
Now, be sure to stay tuned to other Black Friday gaming deals, because we're sure we'll see a ton of amazing deals on peripherals from Razer, SteelSeries, Corsair and more.
- TechRadar is scouring every retailer and rounding up all the top deals over the Black Friday period, and we’ve put all the best Black Friday deals and Cyber Monday deals in easy-to-navigate articles to help you find the bargains you’re looking for.


Soli is a new sensing technology that uses miniature radar
to detect touchless gesture interactions.
The Soli chip incorporates the entire sensor and antenna array into an ultra-compact 8mm x 10mm package.
The concept of Virtual Tools is key to Soli interactions: Virtual Tools are gestures that mimic familiar interactions with physical tools. This metaphor makes it easier to communicate, learn, and remember Soli interactions.
Imagine an invisible button between your thumb and index fingers – you can press it by tapping your fingers together. Or a Virtual Dial that you turn by rubbing thumb against index finger. Imagine grabbing and pulling a Virtual Slider in thin air. These are the kinds of interactions we are developing and imagining.
Even though these controls are virtual, the interactions feel physical and responsive.
Feedback is generated by the haptic sensation of fingers touching each other. Without the constraints of physical controls, these virtual tools can take on the fluidity and precision of our natural human hand motion.
Soli sensor technology works by emitting electromagnetic waves in a broad beam.
Objects within the beam scatter this energy, reflecting some portion back towards the radar antenna. Properties of the reflected signal, such as energy, time delay, and frequency shift capture rich information about the object’s characteristics and dynamics, including size, shape, orientation, material, distance, and velocity.
Soli tracks and recognizes dynamic gestures expressed by fine motions of the fingers and hand. In order to accomplish this with a single chip sensor, we developed a novel radar sensing paradigm with tailored hardware, software, and algorithms. Unlike traditional radar sensors, Soli does not require large bandwidth and high spatial resolution; in fact, Soli’s spatial resolution is coarser than
the scale of most fine finger gestures. Instead, our fundamental sensing principles rely on motion resolution by extracting subtle changes in the received signal over time. By processing these temporal signal variations, Soli can distinguish complex finger movements and deforming hand shapes within its field.
The Soli software architecture consists of a generalized gesture recognition pipeline which is hardware agnostic and can work with different types of radar. The pipeline implements several stages of signal abstraction: from the raw radar data to signal transformations, core and abstract machine learning features, detection and tracking, gesture probabilities, and finally UI tools to interpret gesture controls.
The Soli SDK enables developers to easily access and build upon our gesture recognition pipeline. The Soli libraries extract real-time signals from radar hardware, outputting signal transformations, high precision position and motion data, and gesture labels and parameters at frame rates from 100 to 10,000 frames per second.
Sensor data showing four gestures performed by five users
The Soli sensor is a fully integrated, low-power radar operating in the 60-GHz ISM band. In our journey toward this form factor, we rapidly iterated through several hardware prototypes, beginning with a large bench-top unit built from off-the-shelf components -- including multiple cooling fans. Over the course of 10 months, we redesigned and rebuilt the entire radar system into a single solid-state component that can be easily integrated into small, mobile consumer devices and produced at scale.
The custom-built Soli chip greatly reduces radar system design complexity and power consumption compared to our initial prototypes. We developed two modulation architectures: a Frequency Modulated Continuous Wave (FMCW) radar and a Direct-Sequence Spread Spectrum (DSSS) radar. Both chips integrate the entire radar system into the package, including multiple beamforming antennas that enable 3D tracking and imaging with no moving parts.
The Soli chip can be embedded in wearables, phones, computers, cars and IoT devices in our environment.
Soli has no moving parts, it fits onto a chip and consumes little energy. It is not affected by light conditions and it works through most materials. Just imagine the possibilities...
Let's keep in touch.


These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements.
This change introduces DirectMemory reporting to the RegionServer status page. Oracle JDK6 (1.6.0_31 in my test) doesn't expose "java.nio:type=BufferPool,name=direct", so DirectMemoryUtils#getDirectMemoryUsage (and thus the change to rs-status#memoryStats) reports 0 on that environment, even when DirectMemory is being consumed.
A CP hook (postLogReplay) is added which will be called once distributed log replay on a region is getting over. Please remember that when distributed log replay is not enabled or there is nothing to be replayed for a region, this hook will not get called for that region.
This fix breaks src compatibility. If users try recompiling their CP impl with new HBase jar, they MAY have to change. (If they have overridden this method) This does not break binary compatibility
Thanks for the reviews! I've integrated the v1 patch into trunk, 0.98 & 0.96 branches.
This change also fixes a potential data loss issue when using ZK multi actions because region servers could try to failover themselves (the replication sync up tool acts as a RS too)
WARNING: No release note provided for this change.
Committed to 0.94 and 0.96 as well.
Changes the default split policy to avoid too many regions with default settings. The old policy calculates the split size at each RS as follows: MIN(maxFileSize, flushSize*NoRegions^2) (NoRegions is the number of regions for the table in question seen on this RS)
The new policy calculates the size this way: MIN(maxFileSize, flushSize*2*NoRegions^3) Note that the initial split size is now 2 * the flushSize. With default settings it increased from 128mb to 256mb.
The new policy still allows spreading out the regions over the cluster quickly, but then grows the desired size fairly quickly in order to avoid too many regions per RS.
Downgrades HBase's dependency on commons-math to 2.1, which is consistent with all stable releases of Hadoop.
Many of the metrics exposed in 0.94 were removed with the refactorization of metrics in 0.96. This patch restores the availability of the live and dead regionserver lists. In 0.94 this used to be found as a large nested structure which included regionserver lists and metrics from each region.
{ "name" : "hadoop:service=Master,name=Master", "modelerType" : "org.apache.hadoop.hbase.master.MXBeanImpl", "ZookeeperQuorum" : "localhost:2181", .... "RegionsInTransition" : [ ], "RegionServers" : [ { "key" : "localhost,48346,1390857257246", "value" : { "load" : 2, ....
In 0.96.0, 0.96.1.x and 0.98.0 did not contain this list -- it only contained counts of the number of live and dead regionservers. After this patch, the list are present in a ';' separated field like so:
{ "name" : "Hadoop:service=HBase,name=Master,sub=Server", "modelerType" : "Master,sub=Server", "tag.Context" : "master", "tag.liveRegionServers" : "localhost,56196,1391992019130", "tag.deadRegionServers" : "localhost,40010,1391035309673;localhost,41408,1391990380724;localhost,38682,1390950017735", ... }
Multithread the region mover so can run more than one region move at a time. Specify how many threads on the command line. Feature will make rolling restart complete the sooner (if with a little more disruption as more regions are in flight at a time).
See parent issue for release note on how to use this new feature.
Introduces a new scan attribute to allow a scan operation with explicit columns (Scan.addColumn) to opportunistically look ahead a few KeyValues (columns/versions) before scheduling a seek operation to seek between columns.
A seek is efficient when it can seek past 5-10 KeyValue (columns) or 512-1024 bytes. With small rows and few versions look ahead is typically more efficient.
API: {code} Scan s = new Scan(...); s.addColumn(...); // instructs the RegionServer to attempt two iterations of next before scheduling a seek s.setAttribute(Scan.HINT_LOOKAHEAD, Bytes.toBytes(2)); table.getScanner(s); {code}
HTablePool and HTableFactory are relics and are going away. See HConnection#getTable instead.


--- layout: post title: Great Book Review for Tweens date: 2011-04-03 16:35:54.000000000 -07:00 type: post parent_id: '0' published: true pd: '' status: publish categories: - Book Reviews - Classroom Talk tags: - book review for tweens - Gennifer Choldenko - If a Tree Falls at Lunch Period - reading - storysnoops author: login: k email: k@k display_name: mcary first_name: '' last_name: '' ---
If a Tree Falls at Lunch Period
Author: Gennifer Choldenko
Book review written by StorySnoops.com
This is the story of Kirsten McKenna and Walker Jones, who are both starting seventh grade at the same school, but have never met. Kirsten is thrilled that summer is over so she can get back to her best friend and away from her parents, who only communicate through an intermediary, which may explain why she's gained so much weight in the past few months. Walk just wants to keep his head down at the predominantly white private school his mom transferred him to so that he can stay out of trouble. When Kirsten and Walk meet, they instantly take a liking to one another, but they are completely unprepared for the shocking truth that links them together forever.
Told from the alternating perspectives of Kirsten and Walk, If a Tree Falls at Lunch Period is an engaging read with a startling plot twist that unifies the main characters' stories. Fast-paced and engaging, this book tackles real adolescent issues with an authentic voice. The characters face challenges involving the following themes: racism, body image, popularity, feeling like you don't fit in, parental pressure, queen bee behavior, friendship troubles, cheating, socioeconomic-based snobbery, and conflict between parents. While the publisher's recommended age for this book is nine-twelve, it would appeal most to middle schoolers and is an ideal book club selection.


This candidate does not have a booking at {{slashSeperatedTestCentres}} for today.
This candidate does not have a booking at {{slashSeperatedTestCentres}} for tomorrow.


Get Mappings APIedit
Get Mappings Requestedit
A GetMappingsRequest
can have an optional list of indices and optional list of types:
Optional argumentsedit
The following arguments can also optionally be provided:
|
Timeout to connect to the master node as a |
|
|
Timeout to connect to the master node as a |
Synchronous Executionedit
GetMappingsResponse getMappingResponse = client.indices().getMapping(request, RequestOptions.DEFAULT);
Asynchronous Executionedit
The asynchronous execution of a get mappings request requires both the
GetMappingsRequest
instance and an ActionListener
instance to be passed to
the asynchronous method:
The asynchronous method does not block and returns immediately. Once it is
completed the ActionListener
is called back using the onResponse
method if
the execution successfully completed or using the onFailure
method if it
failed.
A typical listener for GetMappingsResponse
looks like:
Get Mappings Responseedit
The returned GetMappingsResponse
allows to retrieve information about the
executed operation as follows:


| open |
/ |
|
| sendKeys |
id=search_field |
Abbott, TX |
| clickAndWait |
css=a.search-a |
|
| waitForText |
//div[@id='child_of_div_85']/div |
Signed inspection approval delivery |
| click |
//div[@id='child_of_div_85']/div |
|
| waitForText |
css=#qa_85_fields > div.field_help_text |
exact:How do you receive signed approvals for inspections in this jurisdiction? |
| verifyElementPresent |
id=field_mail_85 |
|
| verifyElementPresent |
id=field_email_85 |
|
| verifyElementPresent |
id=field_onsite_85 |
|
| verifyElementPresent |
id=save_85 |
|
| verifyElementPresent |
id=cancel_85 |
|


Lost in Living
Our Members
See Projects (as)
The Mission
Misty Nickle
Bio
It's Bebe
Portfolio
MistyNickle.github.io
Hails From
Seattle WA -> L.A. CA -> Austin TX
Seph Reed
Bio
It's Bebe
Portfolio
SephReed.github.io/portfolio/
Hails From
Santa Cruz CA -> Portland OR -> Austin TX


Sensor Stream Pipe
Sensor Stream Pipe
Class Hierarchy
Go to the textual class hierarchy
Generated by
1.8.13


These two both can be applied to different elements within CSS. Below are examples of how they might look on a css file:
div {
display: inline;
OR
display: inline-block;
}
So what do these do and what are their differences? The inline value is a default for all elements. If the user doesn't tell the code to do anything else than it will be inline. The inline element will accept margin and padding. However, it will only push other elements away horizontally and not vertically. This causes problems when the user wants to stack the elements in a row. Thus bringing in inline-block.
Inline-block allows other elements to sit to the right and left while also accepting margin and padding. Inline-block will also allow the element's height and width to be set while inline doesn't. Inline-block is good to know as it simply allows the user to do more.


DISHONEST pizza eaters pretend they've eaten more pizza than others.
(We're not sure what their motives are)
We tried many different methods of pizza IDs
Tl;DR it also didn't work
72.1% accurate!


Evox plugin is used to handle UC800 evox/var protocol.
The plugin send the batch request every 1 second. And send a single write request every 100 ms if has any. If the write command is coming too fast from Lobster main program, at most 100 write commands will be buffered. The rest will be dropped.
Evox plugin need to configure the server ip and port(can not be empty) in Settings widget.
The tool widget shows the network errors.


The TextChangeEventMode
defines the way the changes are transmitted to the server to cause a server-side
event. There are 3 predefined event modes:
LAZY
(default) - an event is triggered when there is a pause in editing the text. The length of
the pause can be modified with setInputEventTimeout()
. A text change event is forced before a
possible ValueChangeEvent
, even if the user did not keep a pause while entering the text.
TIMEOUT
- an event is triggered after a timeout period. If more changes are made during this
period, the event sent to the server-side includes the changes made up to the last change. The length of the
timeout can be set with setInputEventTimeout()
.
EAGER
- an event is triggered immediately for every change in the text content, typically caused
by a key press. The requests are separate and are processed sequentially one after another. Change events
are nevertheless communicated asynchronously to the server, so further input can be typed while event
requests are being processed.


--- layout: paper title: Publications --- Frustratingly Short Attention Spans in Neural Language Modeling, , Proceedings of International Conference on Learning Representations (ICLR) 2017 [pdf]
@article{daniluk2017frustratingly, journal={Proceedings of International Conference on Learning Representations (ICLR)}, month={November}, year={2017}, author={Daniluk, Michal and Rocktaschel, Tim and Welbl, Johannes and Riedel, Sebastian}, title={Frustratingly Short Attention Spans in Neural Language Modeling}, }


SCENT OF A WOMAN A film review by Anton J. Panagos Copyright 1993 Anton J. Panagos
SCENT OF A WOMAN is one of the best movies of the year. The main reason for the above statement: Al Pacino. This is Pacino's best film role since DOG DAY AFTERNOON. The role is a fully rich one for Pacino, and he plays it to the hilt. SCENT OF A WOMAN is the story of a college kid, aloofingly played by Chris O'Donnell, who spends the Thanksgiving weekend as a paid housesitter for a blind, and totally obnoxious, Vietnam vet, Al Pacino.
Without spoiling the movie's many wonderful surprises, the movie contains a nice mix of drama and comedy. There is also beautifully filmed tango danced by one of the principal characters and newcomer actress Gabrielle Anwar. (This is not a spoiler, just look at any movie ad for SCENT OF A WOMAN in any newspaper!)
What makes the story fascinating? The explanation of Al Pacino's character by others and Pacino himself. His relationship with the young and innocent O'Donnell, who becomes his protege in life. Pacino "teaches" O'Donnell about basic instincts of life and surprisingly Pacino learns a few things as well. The movie's ending was fittingly great. SCENT OF A WOMAN may be nominated for an Oscar in April, but Al Pacino definitely deserves an Oscar for this winning role of a lifetime.
I'd rate SCENT OF A WOMAN **** stars out of possible **** The film is rated (R) for profanity.
Anton J. Panagos
.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews