time skew (third subcomponent), sampling frequency (fifth component), minimum
data value (first subcomponent of component 6), or maximum data value (second
subcomponent) is not present in any repetition of the OBX-5-observation
value field, the value given in the last repetition in which the item
was present may used by the receiver system. This is referred to as a
"sticky default." For example, if all channels have the same sensitivity,
sensitivity correction factor/baseline/time skew, sampling frequency, and
minimum/maximum data values, these may be specified for the first channel but
omitted in all subsequent channel definitions in the same CHN category result
segment, thus reducing the length of the segment. If the sensitivity
correction factor, baseline, or time skew is not present in the first channel
being defined, values of 1, 0, and 0 (respectively) may be used. No other
default values are assumed for components which are not present.
Definition:
The WAV category OBX result segment is used to transmit the actual waveform
data (the time-series digitized values from an analog-to-digital converter
(ADC) or other source of sampled digital data). WAV category result segments
are associated with their corresponding channel definitions (CHN category OBX
result segment) via the Observation Sub-ID. The number of channels defined in
the CHN category result segment specifies the number of channels of multiplexed
data contained in the WAV category result segments associated with it. For
example, if a CHN category result segment contains only a single channel
definition, then each WAV category result segment with the same Observation
Sub-ID contains only one channel of data. However, if a CHN category result
segment contains three channel definitions then each WAV category result
segment with the same Observation Sub-ID must contain three channels of data.
A given set of waveform data for all channels and at multiple successive times
may be transmitted in a single WAV category result segment (provided that the
length of the observation value field does not exceed the maximum defined field
length for OBX segments, 65536), or in multiple successive WAV category result
segments, possibly with interspersed result segments of other types (for
example, containing annotations, or comments).
The data type of the WAV category result segment can be NA (Numeric Array) or
MA (Multiplexed Array). Using the NA data type, the data values are formatted
in "channel-block", or "unmultiplexed" format. The digital samples for each
channel are separated using component delimiters, and successive channels are
separated using the repeat delimiter. Using the MA data type, the data values
are formatted in "channel multiplexed" format, i.e., the values for the first
time sample (all channels) are transmitted first, then the values for the
second time sample (all channels) are transmitted, and so on until all samples
have been transmitted. The digital samples for each channel are separated by
the component delimiter, and successive samples are separated by the repeat
delimiter. Channel multiplexed format can only be used if all of the
multiplexed channels have the same effective sampling frequency.
Definition:
The ANO category OBX segment is used to transmit waveform annotations (coded
entry associated with a given point in time during the waveform recording).
The ANO category result segments are referenced to their corresponding channel
definitions (CHN category OBX result segment ) via the Observation Sub-ID. The
number of channels defined in the CHN category result segment specifies the
number of channels of annotation contained in any ANO category result segments
associated with it. For example, if a CHN category result segment contains
only a single channel definition, then any ANO category result segments with
the same Observation Sub-ID will contain only one annotation coded entry.
However, if a CHN category result segment contains three channel definitions
then any ANO category result segments with the same Observation Sub-ID must
contain three separate annotation coded entries.
The data type of the ANO category result segment is CE. The annotation
coded entries for successive channels are separated using the repeat delimiter.
Adjacent repeat delimiters are used when there is no annotation coded entry for
a channel in a multichannel result segment. Refer to User defined
Table 0317 - Annotations for suggested values.
Value |
Description |
|---|---|
9900 |
Pace spike |
9901 |
SAS marker |
9902 |
Sense marker |
9903 |
Beat marker |
9904 |
etc. |
Response messages containing waveform results are identified by the trigger event provided in the message header segment (MSH-09, second component of message type). Separate trigger events have been defined to differentiate the solicited and unsolicited modes of transmission.
The waveform response unsolicited trigger event identifies ORU messages used to transmit waveform data which are results of an ordered test or series of observations. The W01 trigger event may also be used to identify ORU messages sent as the eventual response to a QRY message specifying a deferred mode query for waveform results/observations with record-oriented format (similar to the deferred response display mode DSR message type described in Chapter 2). One or more ORU messages with the W01 trigger event may result from this type of QRY message.
The W02 trigger event identifies QRF messages which are a response to a QRY message specifying an immediate mode query for waveform results/observations with record-oriented format.
A waveform result "battery" may contain one or more channels of digital waveform data. The Observation Sub-ID is used to logically associate the TIM, CHN and WAV category OBX segments which pertain to a given set of channels in the result "battery." Each Sub-ID group must contain at least one TIM, one CHN and one WAV category segment and at least one of the TIM category result segments must precede the first WAV category result segment in that group.
The
result category for a given OBX segment determines how specific fields in that
segment are valued. The following tables indicate the use of the OBX segment
for waveform components. The data types, lengths, optionality, and repeat
values listed do not replace the basic definition of the OBX segment in section
7.4.2.
The OPT/X column can take the values of R = Required, O = Optional, or X =
Ignored and not valued. OBX Fields marked with an X should not be valued in
Waveform response messages of specified Suffix type. Valuation of the
fields must match the value provided in the associated wave category OBX
segments, i.e., OBX with the same sub-ID must share the same result status.
When
using the OBX for the TIM category, OBX-2 should be valued to TS.
Consequently, OBX-5 should have a length of 26 given the format of the
TS data type. Note the expectations on which fields are required as well as the
fields that should not be valued.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
|
SI |
O |
00569 |
Set ID - OBX |
||
2 |
2 |
ID |
R |
0125 |
00570 |
Value Type |
|
3 |
250 |
CE |
R |
00571 |
Observation Identifier |
||
4 |
20 |
ST |
R |
00572 |
Observation Sub-ID |
||
5 |
26 |
TS |
R |
00573 |
Observation Value |
||
6 |
250 |
CE |
X |
00574 |
Units |
||
7 |
60 |
ST |
X |
00575 |
References Range |
||
8 |
5 |
ID |
X |
0078 |
00576 |
Abnormal Flags |
|
9 |
5 |
NM |
X |
Y/5 |
00577 |
Probability |
|
10 |
2 |
ID |
X |
0080 |
00578 |
Nature of Abnormal Test |
|
11 |
1 |
ID |
R |
0085 |
00579 |
Observation Result Status |
|
12 |
26 |
TS |
X |
00580 |
Date Last Observation Normal Values |
||
13 |
20 |
ST |
X |
00581 |
User Defined Access Checks |
||
14 |
26 |
TS |
X |
00582 |
Date/Time of the Observation |
||
15 |
250 |
CE |
X |
00583 |
Producer's ID |
||
16 |
250 |
CN |
X |
00584 |
Responsible Observer |
||
17 |
250 |
CE |
X |
Y |
00936 |
Observation Method |
|
18 |
22 |
EI |
O |
Y |
01479 |
Equipment Instance Identifier |
|
19 |
26 |
TS |
O |
01480 |
Date/Time of the Analysis |
When
using the OBX for the CHN category, OBX-2 should be valued to CD.
Consequently, OBX-5 could have a length of up to 65536 given the format
of the CD data type. Note the expectations on which fields are required as well
as the fields that should not be valued.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
|
SI |
O |
00569 |
Set ID - OBX |
||
2 |
2 |
ID |
R |
0125 |
00570 |
Value Type |
|
3 |
250 |
CE |
R |
00571 |
Observation Identifier |
||
4 |
20 |
ST |
R |
00572 |
Observation Sub-ID |
||
5 |
65536 |
CD |
R |
00573 |
Observation Value |
||
6 |
250 |
CE |
X |
00574 |
Units |
||
7 |
60 |
ST |
X |
00575 |
References Range |
||
8 |
5 |
ID |
X |
0078 |
00576 |
Abnormal Flags |
|
9 |
5 |
NM |
X |
Y/5 |
00577 |
Probability |
|
10 |
2 |
ID |
X |
0080 |
00578 |
Nature of Abnormal Test |
|
11 |
1 |
ID |
R |
0085 |
00579 |
Observation Result Status |
|
12 |
26 |
TS |
X |
00580 |
Date Last Observation Normal Values |
||
13 |
20 |
ST |
X |
00581 |
User Defined Access Checks |
||
14 |
26 |
TS |
X |
00582 |
Date/Time of the Observation |
||
15 |
250 |
CE |
X |
00583 |
Producer's ID |
||
16 |
250 |
CN |
X |
00584 |
Responsible Observer |
||
17 |
250 |
CE |
X |
Y |
00936 |
Observation Method |
|
18 |
22 |
EI |
O |
Y |
01479 |
Equipment Instance Identifier |
|
19 |
26 |
TS |
O |
01480 |
Date/Time of the Analysis |
Note: The length of the observation value field is variable, depending upon number of channels defined.
When
using the OBX for the WAV category, OBX-2 can be valued as either NM or
MA. Consequently, OBX-5 could have a length of up to 65536 given the
format of the data types. Note the expectations on which fields are required as
well as the fields that should not be valued.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
|
SI |
O |
00569 |
Set ID - OBX |
||
2 |
2 |
ID |
R |
0125 |
00570 |
Value Type |
|
3 |
250 |
CE |
R |
00571 |
Observation Identifier |
||
4 |
20 |
ST |
R |
00572 |
Observation Sub-ID |
||
5 |
65536 |
NA or MA |
C |
00573 |
Observation Value |
||
6 |
250 |
CE |
X |
00574 |
Units |
||
7 |
60 |
ST |
X |
00575 |
References Range |
||
8 |
5 |
ID |
O |
0078 |
00576 |
Abnormal Flags |
|
9 |
5 |
NM |
X |
Y/5 |
00577 |
Probability |
|
10 |
2 |
ID |
X |
0080 |
00578 |
Nature of Abnormal Test |
|
11 |
1 |
ID |
R |
0085 |
00579 |
Observation Result Status |
|
12 |
26 |
TS |
X |
00580 |
Date Last Observation Normal Values |
||
13 |
20 |
ST |
X |
00581 |
User Defined Access Checks |
||
14 |
26 |
TS |
X |
00582 |
Date/Time of the Observation |
||
15 |
250 |
CE |
X |
00583 |
Producer's ID |
||
16 |
250 |
CN |
O |
00584 |
Responsible Observer |
||
17 |
250 |
CE |
X |
00936 |
Observation Method |
||
18 |
22 |
EI |
O |
Y |
01479 |
Equipment Instance Identifier |
|
19 |
26 |
TS |
O |
01480 |
Date/Time of the Analysis |
Notes:
1. The length of the observation value field is variable, depending upon number
of channels and number of data points sampled.
2. Fields 8, 11 and 16 apply exclusively to the set of data points in the OBX.
They do not map to a particular data point or channel.
When
using the OBX for the ANO category, OBX-2 should be valued to CE.
Consequently, OBX-5 could have a length of up the 65536 given the format
of the data types. Note the expectations on which fields are required as well
as the fields that should not be valued.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
4 |
SI |
O |
00569 |
Set ID - OBX |
||
2 |
2 |
ID |
R |
0125 |
00570 |
Value Type |
|
3 |
250 |
CE |
R |
00571 |
Observation Identifier |
||
4 |
20 |
ST |
R |
00572 |
Observation Sub-ID |
||
5 |
250 |
CE |
C |
00573 |
Observation Value |
||
6 |
250 |
CE |
X |
00574 |
Units |
||
7 |
60 |
ST |
X |
00575 |
References Range |
||
8 |
5 |
ID |
O |
Y/5 |
0078 |
00576 |
Abnormal Flags |
9 |
5 |
NM |
X |
00577 |
Probability |
||
10 |
2 |
ID |
X |
0080 |
00578 |
Nature of Abnormal Test |
|
11 |
1 |
ID |
R |
0085 |
00579 |
Observation Result Status |
|
12 |
26 |
TS |
X |
00580 |
Date Last Observation Normal Values |
||
13 |
20 |
ST |
X |
00581 |
User Defined Access Checks |
||
14 |
26 |
TS |
O |
00582 |
Date/Time of the Observation |
||
15 |
250 |
CE |
X |
00583 |
Producer's ID |
||
16 |
250 |
CN |
O |
00584 |
Responsible Observer |
||
17 |
250 |
CE |
X |
Y |
00936 |
Observation Method |
|
18 |
22 |
EI |
O |
Y |
01479 |
Equipment Instance Identifier |
|
19 |
26 |
TS |
O |
01480 |
Date/Time of the Analysis |
Note: The length of the observation value field is variable, depending upon number of channels defined.
This
section gives four example messages of type ORU (unsolicited) that each contain
a three-channel waveform recording, with the same waveform in each channel.
These examples contain data for one patient. In these example message
transmissions, <cr> indicates an ASCII carriage return character
(ASCII 13).
The following is a detailed explanation of each of the segments contained in
the example messages:
Message Header (MSH) Segment - This specifies the delimiters
(|^~\&), sending application (SVL, meaning Sunnyville
Laboratory), receiving application (SVC, meaning Sunnyville Clinic),
date and time of transmission (March 24, 1990 at 10:12:15), message type
(ORU) and trigger event (W01), a message control ID that
identifies this message uniquely among all messages transmitted by this sender
(19264), processing ID (P, meaning production), and specification
version ID (2.3).
Patient ID (PID) Segment - This contains a sequence number
(1), external and internal patient IDs (both 4567890), and a
patient name (Mr. John Q Doe, Jr).
Order (OBR) Segment - This contains a sequence number (1),
placer order number (5678) and placer ID (SVC, meaning Sunnyville
Clinic), filler order number (1234) and filler ID (SVL, meaning
Sunnyville Laboratory), and test/observation ID (5, using a local coding
system that is known to the intended receiver, meaning a three-channel waveform
recording).
CHN Category Result (OBX) Segments - Using a value type of
CD (channel definition), these define each of the three data channels by
number and specify a label (waveform source) for each. The channel sensitivity
(0.5 mV), sampling frequency (200), and minimum and maximum data
values (-2048 to 2047) are specified for each channel in examples
1 and 2 and 4. In example 3, these are specified only for channel 1, but apply
by default to all subsequent channels. No baseline or calibration parameters
are specified, so defaults are used for all channels.
TIM Category Result (OBX) Segments - Using the data type TS (time
stamp), these define the start of the waveform data at a time 525 ms past
8:12:37 on March 24, 1990.
WAV Category Result (OBX) Segments - The data may be transmitted
in either "channel-block" (unmultiplexed) format using the NA data type, or in
"channel-multiplexed" format using the MA data type. The three examples
demonstrate different ways of transmitting 3 waveform channels, with 25 samples
from each waveform channel. Note that in these examples, each waveform channel
is identical.
ANO Category Result (OBX) Segments - Annotation segments with a
single channel definition contain a single annotation string. Annotation
segments with multiple channel definitions contain a separate annotation string
for each defined channel - successive annotation strings are separated from
each other by the repeat delimiter. In the following examples, channel 1 has
been annotated at a time 565 ms past 8:12:37 on March 24, 1990; channel 3 has
been annotated at a time 605 ms past 8:12:37 on March 24, 1990.
MSH|^~\&|SVL||SVC||19900324101215||ORU^W01|...<cr>
PID|1||4567890||Doe^John^Q^Jr^Mr|...<cr>
OBR|1|5678^SVC|1234^SVL|5^three-channel waveform
recording^99SVL|...<cr>
OBX|1|CD|5&CHN^^99SVL|1|1^ONE^0.5&mv^^200^-2048&2047||||||F|...<cr>
OBX|2|TS|5&TIM^^99SVL|1|19900324081237.525||||||F|...<cr>
OBX|3|NA|5&WAV^^99SVL|1|0^1^2^3^4^5^6^7^8^7^6^5^4^3^2^1^0^-1^-2^-3^-4^-5^-6^-7^-8||||||F|...<cr>
OBX|4|CE|5&ANO^^99SVL|1|^Channel passing through
maxima||||||F|||19900324081237.565|...<cr>
OBX|5|CD|5&CHN^^99SVL|2|2^TWO^0.5&mv^^200^-2048&2047||||||F|...<cr>
OBX|6|TS|5&TIM^^99SVL|2|19900324081237.525||||||F|...<cr>
OBX|7|NA|5&WAV^^99SVL|2|0^1^2^3^4^5^6^7^8^7^6^5^4^3^2^1^0^-1^-2^-3^-4^-5^-6^-7^-8||||||F|...<cr>
OBX|8|CD|5&CHN^^99SVL|3|3^THREE^0.5&mv^^200^-2048&2047||||||F|...<cr>
OBX|9|TS|5&TIM^^99SVL|3|19900324081237.525||||||F|...<cr>
OBX|10|NA|5&WAV^^99SVL|3|0^1^2^3^4^5^6^7^8^7^6^5^4^3^2^1^0^-1^-2^-3^-4^-5^-6^-7^-8||||||F|...<cr>
OBX|11|CE|5&ANO^^99SVL|3|^Channel passing through
zero||||||F|||19900324081237.605|...<cr>
...
MSH|^~\&|SVL||SVC||19900324101215||ORU^W01|...<cr>
PID|1||4567890||Doe^John^Q^Jr^Mr|...<cr>
OBR|1|5678^SVC|1234^SVL|5^three-channel waveform
recording^99SVL|...<cr>
OBX|1|CD|5&CHN^^99SVL|1|1^ONE^0.5&mv^^200^-2048&2047~2^TWO^0.5&mv^^200^-2048&2047~3^THREE^0.5&mv^^200^-2048&2047||||||F|...<cr>
OBX|2|TS|5&TIM^^99SVL|1|19900324081237.525||||||F|...<cr>
OBX|3|NA|5&WAV^^99SVL|1|
0^1^2^3^4^5^6^7^8^7^6^5^4^3^2^1^0^-1^-2^-3^-4^-5^-6^-7^-8~
0^1^2^3^4^5^6^7^8^7^6^5^4^3^2^1^0^-1^-2^-3^-4^-5^-6^-7^-8~
0^1^2^3^4^5^6^7^8^7^6^5^4^3^2^1^0^-1^-2^-3^-4^-5^-6^-7^-8||||||F|...<cr>
OBX|4|CE|5&ANO^^99SVL|1|^Channel passing through
maxima||||||F|||19900324081237.565|...<cr>
OBX|5|CE|5&ANO^^99SVL|1|~~^Channel passing through
zero||||||F|||19900324081237.605|...<cr>
Note: This is an illegal construct per the message construction rules from
chapter 1: the repetition separator is used only if more than one occurrence is
transmitted. There is only one occurrence being sent here.
...
MSH|^~\&|SVL||SVC||19900324101215||ORU^W01|...<cr>
PID|1||4567890||Doe^John^Q^Jr^Mr|...<cr>
OBR|1|5678^SVC|1234^SVL|5^three-channel waveform
recording^99SVL|...<cr>
OBX|1|CD|5&CHN^^99SVL|1|1^ONE^0.5&mv^^200^-2048&2047~2^TWO~3^THREE||||||F|...<cr>
OBX|2|TS|5&TIM^^99SVL|1|19900324081237.525||||||F|...<cr>
OBX|3|MA|5&WAV^^99SVL|1|0^0^0~1^1^1~2^2^2~3^3^3~4^4^4~5^5^5~6^6^6~7^7^7~8^8^8~7^7^7~6^6^6~5^5^5~4^4^4~3^3^3~2^2^2~1^1^1~0^0^0~-1^-1^-1~-2^-2^-2~-3^-3^-3~-4^-4^-4~-5^-5^-5~-6^-6^-6~-7^-7^-7~-8^-8^-8||||||F|...<cr>
OBX|4|CE|5&ANO^^99SVL|1|^Channel passing through
maxima||||||F|||19900324081237.565|...<cr>
OBX|5|CE|5&ANO^^99SVL|1|~~^Channel passing through
zero||||||F|||19900324081237.605|...<cr>
Note: This is an illegal construct per the message construction rules from
chapter 1: "the repetition separator is used only if more than one occurrence
is transmitted." There is only one occurrence being sent here.
...
MSH|^~\&|SVL||SVC||19900324101215||ORU^W01|...<cr>
PID|1||4567890||Doe^John^Q^Jr^Mr|...<cr>
OBR|1|5678^SVC|1234^SVL|5^three-channel waveform
recording^99SVL|...<cr>
OBX|1|CD|5&CHN^^99SVL|1|1^ONE^0.5&mv^^200^-2048&2047||||||F|...<cr>
OBX|2|TS|5&TIM^^99SVL|1|19900324081237.525||||||F|...<cr>
OBX|3|NA|5&WAV^^99SVL|1|0^1^2^3^4^5^6^7^8||||||F|...<cr>
OBX|4|CE|5&ANO^^99SVL|1|^Channel passing through
maxima||||||F|||19900324081237.565|...<cr>
OBX|5|NA|5&WAV^^99SVL|1|7^6^5^4^3^2^1^0^-1^-2^-3^-4^-5^-6^-7^-8||||||F|...<cr>
OBX|6|CD|5&CHN^^99SVL|2|2^TWO^0.5&mv^^200^-2048&2047||||||F|...<cr>
OBX|7|TS|5&TIM^^99SVL|2|19900324081237.525||||||F|...<cr>
OBX|8|NA|5&WAV^^99SVL|2|0^1^2^3^4^5^6^7^8^7^6^5^4^3^2^1^0^-1^-2^-3^-4^-5^-6^-7^-8||||||F|...<cr>
OBX|9|CD|5&CHN^^99SVL|3|3^THREE^0.5&mv^^200^-2048&2047||||||F|...<cr>
OBX|10|TS|5&TIM^^99SVL|3|19900324081237.525||||||F|...<cr>
OBX|11|NA|5&WAV^^99SVL|3|0^1^2^3^4^5^6^7^8^7^6^5^4^3^2^1^0||||||F|...<cr>
OBX|12|CE|5&ANO^^99SVL|3|^Channel passing through
zero||||||F|||19900324081237.605|...<cr>
OBX|13|NA|5&WAV^^99SVL|3|-1^-2^-3^-4^-5^-6^-7^-8||||||F|...<cr>
...
Referenced
in 7.1.5 Cod
ing
Schemes
Value |
Description |
Comment / Source |
Category |
99zzz or L |
Local general code (where z is an alphanumeric character) |
Locally defined codes for purpose of sender or receiver. Local codes can be identified by L (for backward compatibility) or 99zzz (where z is an alphanumeric character). |
General code |
ACR |
American College of Radiology finding codes |
Index for Radiological Diagnosis Revised, 3rd Edition 1986, American College of Radiology, Reston, VA. |
Specific Non-Drug Code |
ART |
WHO Adverse Reaction Terms |
WHO Collaborating Centre for International Drug Monitoring, Box 26, S-751 03, Uppsala, Sweden. |
Drug code |
AS4 |
ASTM E1238/ E1467 Universal |
American Society for Testing & Materials and CPT4 (see Appendix X1 of Specification E1238 and Appendix X2 of Specification E1467). |
Specific Non-Drug Code |
AS4E |
AS4 Neurophysiology Codes |
ASTM's diagnostic codes and test result coding/grading systems for clinical neurophysiology. See ASTM Specification E1467, Appendix 2. |
Specific Non-Drug Code |
ATC |
American Type Culture Collection |
Reference cultures (microorganisms, tissue cultures, etc.), related biological materials and associated data. American Type Culture Collection, 12301 Parklawn Dr, Rockville MD, 20852.<PHONE_NUMBER>. http://www.atcc.org |
Specific Non-Drug Code |
C4 |
CPT-4 |
American Medical Association, P.O. Box 10946, Chicago IL 60610. |
Specific Non-Drug Code |
C5 |
CPT-5 |
(under development - same contact as above) |
Specific Non-Drug Code |
CAS |
Chemical abstract codes |
These include unique codes for each unique chemical, including all generic drugs. The codes do not distinguish among different dosing forms. When multiple equivalent CAS numbers exist, use the first one listed in USAN. USAN 1990 and the USP dictionary of drug names, William M. Heller, Ph.D., Executive Editor, United States Pharmacopeial Convention, Inc., 12601 Twinbrook Parkway, Rockville, MD 20852. |
Drug code |
CD2 |
CDT-2 Codes |
American Dental Association's Current Dental Terminology (CDT-2) code. American Dental Association, 211 E. Chicago Avenue,. Chicago, Illinois 60611. |
Specific Non-Drug Code |
CDCA |
CDC Analyte Codes |
As above, for CDCM |
|
CDCM |
CDC Methods/Instruments Codes |
Public Health Practice Program Office, Centers for Disease Control and Prevention, 4770 Buford Highway, Atlanta, GA, 30421. Also available via FTP: ftp.cdc.gov/pub/laboratory _info/CLIA and Gopher: gopher.cdc.gov:70/11/laboratory_info/CLIA |
Drug code |
CDS |
CDC Surveillance |
CDC Surveillance Codes. For data unique to specific public health surveillance requirements. Epidemiology Program Office, Centers for Disease Control and Prevention, 1600 Clifton Rd, Atlanta, GA, 30333.<PHONE_NUMBER>. |
Specific Non-Drug Code |
CE |
CEN ECG diagnostic codes |
CEN PT007. A quite comprehensive set of ECG diagnostic codes (abbreviations) and descriptions published as a pre-standard by CEN TC251. Available from CEN TC251 secretariat, c/o Georges DeMoor, State University Hospital Gent, De Pintelaan 185-5K3, 9000 Gent, Belgium or Jos Willems, University of Gathuisberg, 49 Herestraat, 3000 Leuven, Belgium. |
Specific Non-Drug Code |
CLP |
CLIP |
Simon Leeming, Beth Israel Hospital, Boston MA. Codes for radiology reports. |
Specific Non-Drug Code |
CPTM |
CPT Modifier Code |
Available from the AMA at the address listed for CPT above. These codes are found in Appendix A of CPT 2000 Standard Edition. (CPT 2000 Standard Edition, American Medical Association, Chicago, IL). |
Specific Non-Drug Code |
CST |
COSTART |
International coding system for adverse drug reactions. In the USA, maintained by the FDA, Rockville, MD. |
Drug code |
CVX |
CDC Vaccine Codes |
National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333 |
Drug code |
DCL |
DICOM Class Label |
From the Message Standards Classes table of the SNOMED-DICOM-Microglossary. College of American Pathologists, Skokie, IL, 60077-1034 |
Specific Non-Drug Code |
DCM |
DICOM modality codes |
Dean Bidgood, MD; Duke University Medical Center, Durham NC. Digital Imaging and Communications in Medicine (DICOM). From NEMA Publications PS-3.1 - PS 3.12: The ACR-NEMA DICOM Standard. National Electrical Manufacturers Association (NEMA). Rosslyn, VA, 22209., 1992, 1993, 1995 |
Specific Non-Drug Code |
DQL |
DICOM Query Label |
HL7 Image Management Special Interest Group, Health Level Seven, Ann Arbor, MI. |
Specific Non-Drug Code |
E |
EUCLIDES |
Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60. |
Specific Non-Drug Code |
E5 |
Euclides quantity codes |
Available from Euclides Foundation International nv (see above) |
Specific Non-Drug Code |
E6 |
Euclides Lab method codes |
Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60. |
Specific Non-Drug Code |
E7 |
Euclides Lab equipment codes |
Available from Euclides Foundation International nv (see above) |
Specific Non-Drug Code |
ENZC |
Enzyme Codes |
Enzyme Committee of the International Union of Biochemistry and Molecular Biology. Enzyme Nomenclature: Recommendations on the Nomenclature and Classification of Enzyme-Catalysed Reactions. London: Academic Press, 1992. |
Specific Non-Drug Code |
FDDC |
First DataBank Drug Codes |
National Drug Data File. Proprietary product of First DataBank, Inc.<PHONE_NUMBER>, or http://www.firstdatabank.com. |
Drug code |
FDDX |
First DataBank Diagnostic Codes |
Used for drug-diagnosis interaction checking. Proprietary product of First DataBank, Inc. As above for FDDC. |
Drug code |
FDK |
FDA K10 |
Dept. of Health & Human Services, Food & Drug Administration, Rockville, MD 20857. (device & analyte process codes). |
Specific Non-Drug Code |
HB |
HIBCC |
Health Industry Business Communications Council, 5110 N. 40th St., Ste 120, Phoenix, AZ 85018. |
Specific Non-Drug Code |
HCPCS |
HCFA Common Procedure Coding System |
HCPCS: contains codes for medical equipment, injectable drugs, transportation services, and other services not found in CPT4. |
Specific Non-Drug Code |
HHC |
Home Health Care |
Home Health Care Classification System; Virginia Saba, EdD, RN; Georgetown University School of Nursing; Washington, DC. |
Specific Non-Drug Code |
HI |
Health Outcomes |
Health Outcomes Institute codes for outcome variables available (with responses) from Stratis Health (formerly Foundation for Health Care Evaluation and Health Outcomes Institute), 2901 Metro Drive, Suite 400, Bloomington, MN, 55425-1525;<PHONE_NUMBER> (voice);<PHONE_NUMBER> (fax<EMAIL_ADDRESS>See examples in the Implementation Guide. |
Specific Non-Drug Code |
HL7nnnn |
HL7 Defined Codes where nnnn is the HL7 table number |
Health Level Seven where nnnn is the HL7 table number |
General code |
HPC |
HCFA Procedure Codes (HCPCS) |
Health Care Financing Administration (HCFA) Common Procedure Coding System (HCPCS) including modifiers.[4] |
http://www.hcfa.gov/stats/anhcpcdl.ht[m]www.ntis.go[v]
Specific Non-Drug Code |
|||
I10 |
ICD-10 |
World Health Publications, Albany, NY. |
Specific Non-Drug Code |
I10P |
ICD-10 Procedure Codes |
Procedure Coding System (ICD-10-PCS.) See http://www/hcfa.gov/stats/icd10.icd10.htm for more information. |
Specific Non-Drug Code |
I9 |
ICD9 |
World Health Publications, Albany, NY. |
Specific Non-Drug Code |
I9C |
ICD-9CM |
Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105 (includes all procedures and diagnostic tests). |
Specific Non-Drug Code |
IBT |
ISBT |
International Society of Blood Transfusion. Blood Group Terminology 1990. VOX Sanquines 1990 58(2):152-169. |
Specific Non-Drug Code |
IC2 |
ICHPPC-2 |
International Classification of Health Problems in Primary Care, Classification Committee of World Organization of National Colleges, Academies and Academic Associations of General Practitioners (WONCA), 3rd edition. An adaptation of ICD9 intended for use in General Medicine, Oxford University Press. |
Specific Non-Drug Code |
ICDO |
International Classification of Diseases for Oncology |
International Classification of Diseases for Oncology, 2nd Edition. World Health Organization: Geneva, Switzerland, 1990. Order from: College of American Pathologists, 325 Waukegan Road, Northfield, IL, 60093-2750.<PHONE_NUMBER>. |
Specific Non-Drug Code |
ICS |
ICCS |
Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105. |
Specific Non-Drug Code |
ICSD |
International Classification of Sleep Disorders |
International Classification of Sleep Disorders Diagnostic and Coding Manual, 1990, available from American Sleep Disorders Association, 604 Second Street SW, Rochester, MN 55902 |
Specific Non-Drug Code |
ISOnnnn |
ISO Defined Codes where nnnn is the ISO table number |
International Standards Organization where nnnn is the ISO table number |
General code |
IUPP |
IUPAC/IFCC Property Codes |
International Union of Pure and Applied Chemistry/International Federation of Clinical Chemistry. The Silver Book: Compendium of terminology and nomenclature of properties in clinical laboratory sciences. Oxford: Blackwell Scientific Publishers, 1995. Henrik Olesen, M.D., D.M.Sc., Chairperson, Department of Clinical Chemistry, KK76.4.2, Rigshospitalet, University Hospital of Copenhagen, DK-2200, Copenhagen. http://inet.uni-c.dk/~qukb7642/ |
Specific Non-Drug Code |
IUPC |
IUPAC/IFCC Component Codes |
Codes used by IUPAC/IFF to identify the component (analyte) measured. Contact Henrik Olesen, as above for IUPP. |
Specific Non-Drug Code |
JC8 |
Japanese Chemistry |
Clinical examination classification code. Japan Association of Clinical Pathology. Version 8, 1990. A multiaxial code including a subject code (e.g., Rubella = 5f395, identification code (e.g., virus ab IGG), a specimen code (e.g., serum =023) and a method code (e.g., ELISA = 022) |
Specific Non-Drug Code |
LB |
Local billing code |
Local billing codes/names (with extensions if needed). |
General code |
LN |
Logical Observation Identifier Names and Codes (LOINC®) |
Regenstrief Institute, c/o LOINC, 1050 Wishard Blvd., 5th floor, Indianapolis, IN 46202. 317/630-7433. Available from the Regenstrief Institute server at http://www.regenstrief.org/loinc/loinc.htm. January 2000 version has identifiers, synonyms and cross-reference codes for reporting over 26,000 laboratory and related observations and 1,500 clinical measures. |
Specific Non-Drug Code |
MCD |
Medicaid |
Medicaid billing codes/names. |
Specific Non-Drug Code |
MCR |
Medicare |
Medicare billing codes/names. |
Specific Non-Drug Code |
MDDX |
Medispan Diagnostic Codes |
Codes Used for drug-diagnosis interaction checking. Proprietary product. Hierarchical drug codes for identifying drugs down to manufacturer and pill size. MediSpan, Inc., 8425 Woodfield Crossing Boulevard, Indianapolis, IN 46240. Tel:<PHONE_NUMBER>. WWW: http://www.espan.com/medispan/pages/ medhome.html. As above for MGPI. |
Drug code |
MEDC |
Medical Economics Drug Codes |
Proprietary Codes for identifying drugs. Proprietary product of Medical Economics Data, Inc.<PHONE_NUMBER>. |
Drug code |
MEDR |
Medical Dictionary for Drug Regulatory Affairs (MEDDRA) |
Dr. Louise Wood, Medicines Control Agency, Market Towers, 1 Nine Elms Lane, London SW85NQ, UK Tel: (44)0<PHONE_NUMBER> WWW: http://www.open.gov.uk/mca/mcahome.htm |
Drug code |
MEDX |
Medical Economics Diagnostic Codes |
Used for drug-diagnosis interaction checking. Proprietary product of Medical Economics Data, Inc.<PHONE_NUMBER>. |
Drug code |
MGPI |
Medispan GPI |
Medispan hierarchical drug codes for identifying drugs down to manufacturer and pill size. Proprietary product of MediSpan, Inc., 8425 Woodfield Crossing Boulevard, Indianapolis, IN 46240. Tel:<PHONE_NUMBER>. |
Drug code |
MVX |
CDC Vaccine Manufacturer Codes |
As above, for CVX |
Drug code |
NDA |
NANDA |
North American Nursing Diagnosis Association, Philadelphia, PA. |
Specific Non-Drug Code |
NDC |
National drug codes |
These provide unique codes for each distinct drug, dosing form, manufacturer, and packaging. (Available from the National Drug Code Directory, FDA, Rockville, MD, and other sources.) |
Drug code |
NIC |
Nursing
Interventions |
Iowa Intervention Project, College of Nursing, University of Iowa, Iowa City, Iowa |
Specific Non-Drug Code |
NPI |
National Provider Identifier |
Health Care Finance Administration, US Dep't. of Health and Human Services, 7500 Security Blvd., Baltimore, MD 21244. |
Specific Non-Drug Code |
OHA |
Omaha System |
Omaha Visiting Nurse Association, Omaha, NB. |
Specific Non-Drug Code |
OHA |
Omaha |
Omaha Visiting Nurse Association, Omaha, NB. |
Specific Non-Drug Code |
POS |
POS Codes |
HCFA Place of Service Codes for Professional Claims (see http://www.hcfa.gov/medicare/poscode.htm). |
Specific Non-Drug Code |
RC |
Read Classification |
The Read Clinical Classification of Medicine, Park View Surgery, 26 Leicester Rd., Loughborough LE11 2AG (includes drug procedure and other codes, as well as diagnostic codes). |
Specific Non-Drug Code |
SDM |
SNOMED- DICOM Microglossary |
College of American Pathologists, Skokie, IL, 60077-1034. (formerly designated as 99SDM). |
Specific Non-Drug Code |
SNM |
Systemized Nomenclature of Medicine (SNOMED) |
Systemized Nomenclature of Medicine, 2nd Edition 1984 Vols 1, 2, College of American Pathologists, Skokie, IL. |
Specific Non-Drug Code |
SNM3 |
SNOMED International |
SNOMED International, 1993 Vols 1-4, College of American Pathologists, Skokie, IL, 60077-1034.. |
Specific Non-Drug Code |
SNT |
SNOMED topology codes (anatomic sites) |
College of American Pathologists, 5202 Old Orchard Road, Skokie, IL 60077-1034. |
Specific Non-Drug Code |
UC |
UCDS |
Uniform Clinical Data Systems. Ms. Michael McMullan, Office of Peer Review Health Care Finance Administration, The Meadows East Bldg., 6325 Security Blvd., Baltimore, MD 21207;<PHONE_NUMBER>. |
Specific Non-Drug Code |
UMD |
MDNS |
Universal Medical Device Nomenclature System. ECRI, 5200 Butler Pike, Plymouth Meeting, PA 19462 USA. Phone:<PHONE_NUMBER>, Fax:<PHONE_NUMBER>. |
Device code |
UML |
Unified Medical Language |
National Library of Medicine, 8600 Rockville Pike, Bethesda, MD 20894. |
Specific Non-Drug Code |
UPC |
Universal Product Code |
The Uniform Code Council. 8163 Old Yankee Road, Suite J, Dayton, OH 45458;<PHONE_NUMBER> |
Specific Non-Drug Code |
UPIN |
UPIN |
Medicare/HCFA's universal physician identification numbers, available from Health Care Financing Administration, U.S. Dept. of Health and Human Services, Bureau of Program Operations, 6325 Security Blvd., Meadows East Bldg., Room 300, Baltimore, MD 21207 |
Specific Non-Drug Code |
W1 |
WHO rec# drug codes |
World Health organization record number code. A unique sequential number is assigned to each unique single component drug and to each multi-component drug. Eight digits are allotted to each such code, six to identify the active agent, and 2 to identify the salt, of single content drugs. Six digits are assigned to each unique combination of drugs in a dispensing unit. The six digit code is identified by W1, the 8 digit code by W2. |
Drug code |
W2 |
WHO rec# drug codes |
World Health organization record number code. A unique sequential number is assigned to each unique single component drug and to each multi-component drug. Eight digits are allotted to each such code, six to identify the active agent, and 2 to identify the salt, of single content drugs. Six digits are assigned to each unique combination of drugs in a dispensing unit. The six digit code is identified by W1, the 8 digit code by W2. |
Drug code |
W4 |
WHO rec# code with ASTM extension |
With ASTM extensions (see Implementation Guide), the WHO codes can be used to report serum (and other) levels, patient compliance with drug usage instructions, average daily doses and more (see Appendix X1 the Implementation Guide). |
Drug code |
WC |
WHO ATC |
WHO's ATC codes provide a hierarchical classification of drugs by therapeutic class. They are linked to the record number codes listed above. |
Drug code |
Referenced
in <IP_ADDRESS> Coding Schemes
Value |
Description |
|---|---|
BE |
Bilateral Ears |
OU |
Bilateral Eyes |
BN |
Bilateral Nares |
BU |
Buttock |
CT |
Chest Tube |
LA |
Left Arm |
LAC |
Left Anterior Chest |
LACF |
Left Antecubital Fossa |
LD |
Left Deltoid |
LE |
Left Ear |
LEJ |
Left External Jugular |
OS |
Left Eye |
LF |
Left Foot |
LG |
Left Gluteus Medius |
LH |
Left Hand |
LIJ |
Left Internal Jugular |
LLAQ |
Left Lower Abd Quadrant |
LLFA |
Left Lower Forearm |
LMFA |
Left Mid Forearm |
LN |
Left Naris |
LPC |
Left Posterior Chest |
LSC |
Left Subclavian |
LT |
Left Thigh |
LUA |
Left Upper Arm |
LUAQ |
Left Upper Abd Quadrant |
LUFA |
Left Upper Forearm |
LVG |
Left Ventragluteal |
LVL |
Left Vastus Lateralis |
NB |
Nebulized |
PA |
Perianal |
PERIN |
Perineal |
RA |
Right Arm |
RAC |
Right Anterior Chest |
RACF |
Right Antecubital Fossa |
RD |
Right Deltoid |
RE |
Right Ear |
REJ |
Right External Jugular |
OD |
Right Eye |
RF |
Right Foot |
RG |
Right Gluteus Medius |
RH |
Right Hand |
RIJ |
Right Internal Jugular |
RLAQ |
Rt Lower Abd Quadrant |
RLFA |
Right Lower Forearm |
RMFA |
Right Mid Forearm |
RN |
Right Naris |
RPC |
Right Posterior Chest |
RSC |
Right Subclavian |
RT |
Right Thigh |
RUA |
Right Upper Arm |
RUAQ |
Right Upper Abd Quadrant |
RUFA |
Right Upper Forearm |
RVL |
Right Vastus Lateralis |
RVG |
Right Ventragluteal |
Referenced
in <IP_ADDRESS> Coding Schemes
Referenced
in <IP_ADDRESS>.2 - ISO and ANSI customary units abbreviations
Code/Abbr. |
Name |
|---|---|
/(arb_u) |
*1 / arbitrary unit |
/iu |
*1 / international unit |
/kg |
*1 / kilogram |
/L |
1 / liter |
1/mL |
*1 / milliliter |
10.L/min |
*10 x liter / minute |
10.L /(min.m2) |
*10 x (liter / minute) / meter2 = liter / (minute × meter2) |
10*3/mm3 |
*103 / cubic millimeter (e.g., white blood cell count) |
10*3/L |
*103 / Liter |
10*3/mL |
*103 / milliliter |
10*6/mm3 |
*106 / millimeter3 |
10*6/L |
*106 / Liter |
10*6/mL |
*106 / milliliter |
10*9/mm3 |
*109 / millimeter3 |
10*9/L |
*109 / Liter |
10*9/mL |
*109 / milliliter |
10*12/L |
*1012 / Liter |
10*3(rbc) |
*1000 red blood cells[dagger] |
a/m |
Ampere per meter |
(arb_u) |
*Arbitrary unit |
bar |
Bar (pressure; 1 bar = 100 kilopascals) |
/min |
Beats or Other Events Per Minute |
bq |
Becquerel |
(bdsk_u) |
*Bodansky Units |
(bsa) |
*Body surface area |
(cal) |
*Calorie |
1 |
*Catalytic Fraction |
/L |
Cells / Liter |
cm |
Centimeter |
cm_h20 |
* Centimeters of water =H20 (pressure) |
cm_h20.s/L |
Centimeters H20 / (liter / second) = (centimeters H20 × second) / liter (e.g., mean pulmonary resistance) |
cm_h20/(s.m) |
(Centimeters H20 / second) / meter = centimeters H20 / (second × meter) (e.g., pulmonary pressure time product) |
(cfu) |
*Colony Forming Units |
m3/s |
Cubic meter per second |
d |
Day |
db |
Decibels |
dba |
*Decibels a Scale |
cel |
Degrees Celsius |
deg |
Degrees of Angle |
(drop) |
Drop |
10.un.s/cm5 |
Dyne × Second / centimeter5 (1 dyne = 10 micronewton = 10 un) (e.g., systemic vascular resistance) |
10.un.s/(cm5.m2) |
((Dyne × second) / centimeter5) / meter2 = (Dyne × second) / (centimeter5 × meter2) (1 dyne = 10 micronewton = 10 un) (e.g., systemic vascular resistance/body surface area) |
ev |
Electron volts (1 electron volt = 160.217 zeptojoules) |
eq |
Equivalent |
f |
Farad (capacitance) |
fg |
Femtogram |
fL |
Femtoliter |
fmol |
Femtomole |
/mL |
*Fibers / milliliter |
g |
Gram |
g/d |
*Gram / Day |
g/dL |
Gram / Deciliter |
g/hr |
Gram / Hour |
g/(8.hr) |
*Gram / 8 Hour Shift |
g/kg |
Gram / Kilogram (e.g., mass dose of medication per body weight) |
g/(kg.d) |
(Gram / Kilogram) / Day = gram / (kilogram × day) (e.g., mass dose of medication per body weight per day) |
g/(kg.hr) |
(Gram / Kilogram) / Hour = gram / (kilogram × hour) (e.g., mass dose of medication per body weight per hour) |
g/(8.kg.hr) |
(Gram / Kilogram) /8 Hour Shift = gram / (kilogram × 8 hour shift) (e.g., mass dose of medication per body weight per 8 hour shift) |
g/(kg.min) |
(Gram / Kilogram) / Minute = gram / (kilogram × minute) (e.g., mass dose of medication per body weight per minute) |
g/L |
Gram / Liter |
g/m2 |
Gram / Meter2 (e.g., mass does of medication per body surface area) |
g/min |
Gram / Minute |
g.m/(hb) |
Gram × meter / heart beat (e.g., ventricular stroke work) |
g.m/((hb).m2) |
(Gram × meter/ heartbeat) / meter2 = (gram × meter) /
(heartbeat × meter2) |
g(creat) |
*Gram creatinine |
g(hgb) |
*Gram hemoglobin |
g.m |
Gram meter |
g(tot_nit) |
*Gram total nitrogen |
g(tot_prot) |
*Gram total protein |
g(wet_tis) |
*Gram wet weight tissue |
gy |
Grey (absorbed radiation dose) |
hL |
Hectaliter = 102 liter |
h |
Henry |
in |
Inches |
in_hg |
Inches of Mercury (=Hg) |
iu |
*International Unit |
iu/d |
*International Unit / Day |
iu/hr |
*International Unit / Hour |
iu/kg |
International Unit / Kilogram |
iu/L |
*International Unit / Liter |
iu/mL |
*International Unit / Milliliter |
iu/min |
*International Unit / Minute |
j/L |
Joule/liter (e.g., work of breathing) |
kat |
*Katal |
kat/kg |
*Katal / Kilogram |
kat/L |
*Katal / Liter |
k/watt |
Kelvin per watt |
(kcal) |
Kilocalorie (1 kcal = 6.693 kilojoule) |
(kcal)/d |
*Kilocalorie / Day |
(kcal)/hr |
*Kilocalorie / Hour |
(kcal)/(8.hr) |
*Kilocalorie / 8 Hours Shift |
kg |
Kilogram |
kg(body_wt) |
* kilogram body weight |
kg/m3 |
Kilogram per cubic meter |
kh/h |
Kilogram per hour |
kg/L |
Kilogram / liter |
kg/min |
Kilogram per minute |
kg/mol |
Kilogram / mole |
kg/s |
Kilogram / second |
kg/(s.m2) |
(Kilogram / second)/ meter2 = kilogram / (second × meter2) |
kg/ms |
Kilogram per square meter |
kg.m/s |
Kilogram meter per second |
kpa |
Kilopascal (1 mmHg = 0.1333 kilopascals) |
ks |
Kilosecond |
(ka_u) |
King-Armstrong Unit |
(knk_u) |
*Kunkel Units |
L |
Liter |
L/d |
*Liter / Day |
L/hr |
Liter / hour |
L/(8.hr) |
*Liter / 8 hour shift |
L/kg |
Liter / kilogram |
L/min |
Liter / minute |
L/(min.m2) |
(Liter / minute) / meter2 = liter / (minute ×
meter2) |
L/s |
Liter / second (e.g., peak expiratory flow) |
L.s |
Liter / second / second2 = liter × second |
lm |
Lumen |
lm/m2 |
Lumen / Meter2 |
(mclg_u) |
*MacLagan Units |
mas |
Megasecond |
m |
Meter |
m2 |
Meter2 (e.g., body surface area) |
m/s |
Meter / Second |
m/s2 |
Meter / Second2 |
ueq |
*Microequivalents |
ug |
Microgram |
ug/d |
Microgram / Day |
ug/dL |
Microgram / Deciliter |
ug/g |
Microgram / Gram |
ug/hr |
*Microgram / Hour |
ug(8hr) |
Microgram / 8 Hour Shift |
ug/kg |
Microgram / Kilogram |
ug/(kg.d) |
(Microgram / Kilogram) /Day = microgram / (kilogram × day) (e.g., mass dose of medication per patient body weight per day) |
ug/(kg.hr) |
(Microgram / Kilogram) / Hour = microgram / (kilogram × hours) (e.g., mass dose of medication per patient body weight per hour) |
ug/(8.hr.kg) |
(Microgram / Kilogram) / 8 hour shift = microgram / (kilogram × 8 hour
shift) |
ug/(kg.min) |
(Microgram / Kilogram) / Minute = microgram / (kilogram × minute) |
ug/L |
Microgram / Liter |
ug/m2 |
Microgram / Meter2 (e.g., mass dose of medication per patient body surface area) |
ug/min |
Microgram / Minute |
uiu |
*Micro international unit |
ukat |
*Microkatel |
um |
Micrometer (Micron) |
umol |
Micromole |
umol/d |
Micromole / Day |
umol/L |
Micromole / Liter |
umol/min |
Micromole / Minute |
us |
Microsecond |
uv |
Microvolt |
mbar |
Millibar (1 millibar = 100 pascals) |
mbar.s/L |
Millibar / (liter / second) =(millibar × second) / liter (e.g., expiratory resistance) |
meq |
*Milliequivalent |
meq/d |
*Milliequivalent / Day |
meq/hr |
*Milliequivalent / Hour |
meq/(8.hr) |
Milliequivalent / 8 Hour Shift |
meq/kg |
Milliequivalent / Kilogram (e.g., dose of medication in milliequivalents per patient body weight) |
meq/(kg.d) |
(Milliequivalents / Kilogram) / Day = milliequivalents / (kilogram × day) (e.g., dose of medication in milliequivalents per patient body weight per day) |
meq/(kg.hr) |
(Milliequivalents / Kilogram) / Hour = milliequivalents / (kilogram × hour) (e.g., dose of medication in milliequivalents per patient body weight per hour) |
meq/(8.hr.kg) |
(Milliequivalents / Kilogram) / 8 Hour Shift = milliequivalents / (kilogram × 8 hour shift) (e.g., dose of medication in milliequivalents per patient body weight per 8 hour shift) |
meq/(kg.min) |
(Milliequivalents / Kilogram) / Minute = milliequivalents / (kilogram × minute) (e.g., dose of medication in milliequivalents per patient body weight per minute) |
meq/L |
Milliequivalent / Liter |
Milliequivalent / Meter2 (e.g., dose of medication in milliequivalents per patient body surface area) |
|
meq/min |
Milliequivalent / Minute |
mg |
Milligram |
mg/m3 |
Milligram / Meter3 |
mg/d |
Milligram / Day |
mg/dL |
Milligram / Deciliter |
mg/hr |
Milligram / Hour |
mg/(8.hr) |
Milligram / 8 Hour shift |
mg/kg |
Milligram / Kilogram |
mg/(kg.d) |
(Milligram / Kilogram) / Day = milligram / (kilogram × day) (e.g., mass dose of medication per patient body weight per day) |
mg/(kg.hr) |
(Milligram / Kilogram) / Hour = milligram/ (kilogram × hour) (e.g., mass dose of medication per patient body weight per hour) |
mg/(8.hr.kg) |
(Milligram / Kilogram) /8 Hour Shift = milligram / (kilogram × 8 hour shift) (e.g., mass dose of medication per patient body weight per 8 hour shift) |
mg/(kg.min) |
(Milligram / Kilogram) / Minute = milligram / (kilogram × minute) (e.g., mass dose of medication per patient body weight per hour) |
mg/L |
Milligram / Liter |
mg/m2 |
Milligram / Meter2 (e.g., mass dose of medication per patient body surface area) |
mg/min |
Milligram / Minute |
mL |
Milliliter |
mL/cm_h20 |
Milliliter / Centimeters of Water (H20) (e.g., dynamic lung compliance) |
mL/d |
*Milliliter / Day |
mL/(hb) |
Milliliter / Heart Beat (e.g., stroke volume) |
mL/((hb).m2) |
(Milliliter / Heart Beat) / Meter2 = Milliliter / (Heart Beat × Meter2) (e.g., ventricular stroke volume index) |
mL/hr |
*Milliliter / Hour |
mL/(8.hr) |
*Milliliter / 8 Hour Shift |
mL/kg |
Milliliter / Kilogram (e.g., volume dose of medication or treatment per patient body weight) |
mL/(kg.d) |
(Milliliter / Kilogram) / Day = milliliter / (kilogram × day) (e.g., volume dose of medication or treatment per patient body weight per day) |
mL/(kg.hr) |
(Milliliter / Kilogram) / Hour = milliliter / (kilogram × hour) (e.g., volume dose of medication or treatment per patient body weight per hour) |
mL/(8.hr.kg) |
(Milliliter / Kilogram) / 8 Hour Shift = milliliter / (kilogram × 8 hour shift) (e.g., volume dose of medication or treatment per body weight per 8 hour shift) |
mL/(kg.min) |
(Milliliter / Kilogram) / Minute = milliliter / (kilogram × minute) (e.g., volume dose of medication or treatment per patient body weight per minute) |
mL/m2 |
Milliliter / Meter2 (e.g., volume of medication or other treatment per patient body surface area) |
mL/mbar |
Milliliter / Millibar (e.g., dynamic lung compliance) |
mL/min |
Milliliter / Minute |
mL/(min.m2) |
(Milliliter / Minute) / Meter2 = milliliter / (minute × meter2) (e.g., milliliters of prescribed infusion per body surface area; oxygen consumption index) |
mL/s |
Milliliter / Second |
mm |
Millimeter |
mm(hg) |
*Millimeter (HG) (1 mm Hg = 133.322 kilopascals) |
mm/hr |
Millimeter/ Hour |
mmol/kg |
Millimole / Kilogram (e.g., molar dose of medication per patient body weight) |
mmol/(kg.d) |
(Millimole / Kilogram) / Day = millimole / (kilogram × day) (e.g., molar dose of medication per patient body weight per day) |
mmol/(kg.hr) |
(Millimole / Kilogram) / Hour = millimole / (kilogram × hour) (e.g., molar dose of medication per patient body weight per hour) |
mmol/(8.hr.kg) |
(Millimole / Kilogram) / 8 Hour Shift = millimole / (kilogram × 8 hour shift) (e.g., molar dose of medication per patient body weight per 8 hour shift) |
mmol/(kg.min) |
(Millimole / Kilogram) / Minute = millimole / (kilogram × minute) (e.g., molar dose of medication per patient body weight per minute) |
mmol/L |
Millimole / Liter |
mmol/hr |
Millimole / Hour |
mmol/(8hr) |
Millimole / 8 Hour Shift |
mmol/min |
Millimole / Minute |
mmol/m2 |
Millimole / Meter2 (e.g., molar dose of medication per patient body surface area) |
mosm/L |
*Milliosmole / Liter |
ms |
Milliseconds |
mv |
Millivolts |
miu/mL |
*Milliunit / Milliliter |
mol/m3 |
Mole per cubic meter |
mol/kg |
Mole / Kilogram |
mol/(kg.s) |
(Mole / Kilogram) / Second = mole / (kilogram × second) |
mol/L |
Mole / Liter |
mol/s |
Mole / Second |
ng |
Nanogram |
ng/d |
Nanogram / Day |
ng/hr |
*Nanogram / Hour |
ng/(8.hr) |
Nanogram / 8 Hour shift |
ng/L |
Nanogram / Liter |
ng/kg |
Nanogram / Kilogram (e.g., mass dose of medication per patient body weight) |
ng/(kg.d) |
(Nanogram / Kilogram) / Day = nanogram / (kilogram × day) (e.g., mass dose of medication per patient body weight per day) |
ng/(kg.hr) |
(Nanogram / Kilogram) / Hour = nanogram / (kilogram × hour) (e.g., mass dose of medication per patient body weight per hour) |
ng/(8.hr.kg) |
(Nanogram / Kilogram) / 8 Hour Shift = nanogram / (kilogram × 8 hour shift) (e.g., mass dose of medication per patient body weight per 8 hour shift) |
ng/(kg.min) |
(Nanogram / Kilogram) / Minute = nanogram / (kilogram × minute) (e.g., mass dose of medication per patient body weight per minute) |
ng/m2 |
Nanogram / Meter2 (e.g., mass dose of medication per patient body surface area) |
ng/mL |
Nanogram / Milliliter |
ng/min |
*Nanogram / Minute |
ng/s |
*Nanogram / Second |
nkat |
*Nanokatel |
nm |
Nanometer |
nmol/s |
Nanomole / Second |
ns |
Nanosecond |
n |
Newton (force) |
n.s |
Newton second |
(od) |
*O.D. (optical density) |
ohm |
Ohm (electrical resistance) |
ohm.m |
Ohm meter |
osmol |
Osmole |
osmol/kg |
Osmole per kilogram |
osmol/L |
Osmole per liter |
/m3 |
*Particles / Meter3 |
/L |
*Particles / Liter |
/(tot) |
*Particles / Total Count |
(ppb) |
*Parts Per Billion |
(ppm) |
*Parts Per Million |
(ppth) |
Parts per thousand |
(ppt) |
Parts per trillion (10^12) |
pal |
Pascal (pressure) |
/(hpf) |
*Per High Power Field |
(ph) |
*pH |
pa |
Picoampere |
pg |
Picogram |
pg/L |
Picogram / Liter |
pg/mL |
Picogram / Milliliter |
pkat |
*Picokatel |
pm |
Picometer |
pmol |
*Picomole |
ps |
Picosecond |
pt |
Picotesla |
(pu) |
*P.U. |
% |
Percent |
dm2/s2 |
Rem (roentgen equivalent man) = 10-2 meter2 / second2 = decimeter2 / second2 Dose of ionizing radiation equivalent to 1 rad of x-ray or gamma ray) [From Dorland's Medical Dictionary] |
sec |
Seconds of arc |
sie |
Siemens (electrical conductance) |
sv |
Sievert |
m2/s |
Square meter / second |
cm2/s |
Square centimeter / second |
t |
Tesla (magnetic flux density) |
(td_u) |
Todd Unit |
v |
Volt (electric potential difference) |
1 |
Volume Fraction |
wb |
Weber (magnetic flux) |
*Starred
items are not genuine ISO, but do not conflict. |
None.
The length of the observation field is
variable, depending upon value type. See OBX-2 value type.[2] May repeat for multipart, single answer results with
appropriate data types, e.g., CE, TX, and FT data types.
[3] LOINC® Committee. Logical Observation
Identifier Names and Codes. Indianapolis: Regenstrief Institute and LOINC®
Committee, 1995. Regenstrief Institute c/o LOINC, 1050 Wishard Blvd., RG-5,
Indianapolis, IN 46202. 317/630-7433. Available at
http://www:regenstrief.org/loinc/loinc.html. The LOINC® Code System is
described in Forrey AW, McDonald CJ, DeMoor G, Huff SM, Leavelle D, Leland D,
et.al. Logical Observation Identifier Names and Codes (LOINC®) database: a
public use set of codes and names for electronic reporting of clinical
laboratory test results. Clinical Chemistry 1996;42:81-90[4] The HCPCS code is divided into three "levels." Level I
includes the entire CPT-4 code by reference. Level II includes the American
Dental Association's Current Dental Terminology (CDT-2) code by reference.
Level II also includes the genuine HCPCS codes, approved and maintained jointly
by the Alpha-Numeric Editorial Panel, consisting of HCFA, the Health Insurance
Association of America, and the Blue Cross and Blue Shield Association. Level
III are codes developed locally by Medicare carriers. The HCPCS modifiers are
divided into the same three levels, I being CPT-4 modifiers, II CDT-2 and
genuine HCPCS modifiers, and III being locally agreed modifiers.
The
genuine HCPCS codes and modifiers of level II can be found at [. HCFA distributes the HCPCS codes via the National Technical
Information Service (NTIS, ) and NTIS distribution includes the CDT-2 part of
HCPCS Level II, but does not include the CPT-4 part (Level I). HCFA may
distribute the CPT-4 part to its contractors.


lwres_context_create, lwres_context_destroy, lwres_context_nextserial, lwres_context_initserial, lwres_context_freemem, lwres_context_allocmem, lwres_context_sendrecv — lightweight resolver context management
#include <lwres/lwres.h>
lwres_result_t
lwres_context_create( |
lwres_context_t ** | contextp, |
| void * | arg, | |
| lwres_malloc_t | malloc_function, | |
| lwres_free_t |
free_function) ; |
lwres_result_t
lwres_context_destroy( |
lwres_context_t ** |
contextp) ; |
void
lwres_context_initserial( |
lwres_context_t * | ctx, |
| lwres_uint32_t |
serial) ; |
lwres_uint32_t
lwres_context_nextserial( |
lwres_context_t * |
ctx) ; |
void
lwres_context_freemem( |
lwres_context_t * | ctx, |
| void * | mem, | |
| size_t |
len) ; |
void
lwres_context_allocmem( |
lwres_context_t * | ctx, |
| size_t |
len) ; |
void *
lwres_context_sendrecv( |
lwres_context_t * | ctx, |
| void * | sendbase, | |
| int | sendlen, | |
| void * | recvbase, | |
| int | recvlen, | |
| int * |
recvd_len) ; |
lwres_context_create()
creates a lwres_context_t structure for use in
lightweight resolver operations. It holds a socket and other
data needed for communicating with a resolver daemon. The new
lwres_context_t is returned through
contextp
, a pointer to a
lwres_context_t pointer. This
lwres_context_t pointer must initially be NULL, and
is modified to point to the newly created
lwres_context_t.
When the lightweight resolver needs to perform dynamic memory
allocation, it will call
malloc_function
to allocate memory and
free_function
to free it. If
malloc_function
and
free_function
are NULL, memory is allocated using
malloc(3).
and
free(3).
It is not permitted to have a NULL
malloc_function
and a non-NULL
free_function
or vice versa.
arg
is passed as the first parameter to
the memory allocation functions. If
malloc_function
and
free_function
are NULL,
arg
is unused and should be passed as
NULL.
Once memory for the structure has been allocated,
it is initialized using
lwres_conf_init(3)
and returned via *contextp
.
lwres_context_destroy()
destroys a lwres_context_t, closing its socket.
contextp
is a pointer to a pointer to the
context that is to be destroyed. The pointer will be set to
NULL when the context has been destroyed.
The context holds a serial number that is used to identify
resolver request packets and associate responses with the
corresponding requests. This serial number is controlled using
lwres_context_initserial()
and
lwres_context_nextserial()
.
lwres_context_initserial()
sets the serial
number for context *ctx
to
serial
.
lwres_context_nextserial()
increments the
serial number and returns the previous value.
Memory for a lightweight resolver context is allocated and freed
using lwres_context_allocmem()
and
lwres_context_freemem()
. These use
whatever allocations were defined when the context was created
with lwres_context_create()
.
lwres_context_allocmem()
allocates
len
bytes of memory and if successful
returns a pointer to the allocated storage.
lwres_context_freemem()
frees
len
bytes of space starting at location
mem
.
lwres_context_sendrecv()
performs I/O for the context ctx
. Data
are read and written from the context's socket. It writes data
from sendbase
— typically a
lightweight resolver query packet — and waits for a reply
which is copied to the receive buffer at
recvbase
. The number of bytes that were
written to this receive buffer is returned in
*recvd_len
.
lwres_context_create()
returns LWRES_R_NOMEMORY if memory for
the struct lwres_context could not be allocated,
LWRES_R_SUCCESS otherwise.
Successful calls to the memory allocator
lwres_context_allocmem()
return a pointer to the start of the allocated space.
It returns NULL if memory could not be allocated.
LWRES_R_SUCCESS
is returned when
lwres_context_sendrecv()
completes successfully.
LWRES_R_IOERROR
is returned if an I/O error occurs and
LWRES_R_TIMEOUT
is returned if
lwres_context_sendrecv()
times out waiting for a response.


Stammbaum
Make a family tree!
Add a new person
Add a new parent/child relationship
Add a new union (ie, marriage, civil union, domestic partnership)


About UsThe Barrier Reef Orchestra is a product of North Queensland Ensembles Inc which is an Incorporated Association registered in the State of Queensland. It is also a tax deductible fund listed on the Register of Cultural Organisations under Subdivision 30-B of the Income tax Assessment Act 1997. It is based in Townsville, North Queensland, Australia. History of the OrchestraOver a two-year period in the late nineties, Townsville musicians, arts workers and a group of people who had a love for music realised the potential for developing a community-based Orchestra, one that would flourish and become an integral part of the city’s cultural life. In 2000 to ‘test’ the viability of establishing an Orchestra a weekend workshop was arranged and musicians were invited to participate. This resulted in the establishment of the Barrier Reef Orchestra. Now in a typical year the Barrier Reef Orchestra performs three times generally with a guest conductor and occasionally with other performing groups. In addition, smaller ensembles, using players from the Orchestra, regularly give concerts. There is also a concert organised for the Australian Festival Of Chamber Music and the Orchestra contributes to the Australian Concerto Vocal Competition. |


Spark Application
|
An "Application Action" is a simple Spark Action that can launch any Application.
You can also use a Document Action to launch an Application,
but Application Action have an advantage:
if the Application you choose is deplaced on an other Volume (or anything else that normally brakes an Alias),
an Application Action will try to find your Application, and not a Document Action.
To create a new Application Key, choose "Application" in "New Action" Menu or double clic on the Application List.
Then you can choose the Application you want launch with this Action by clicking on the "Choose…" Button.
There are 3 possible actions:
• Launch: Launch an Application or bring it on the foreground if it is already running. In fact Launch has the same effect as double clicking the Application Icon.
• Quit: Send a Quit signal to the Application. It has the same effect as choose "Quit" in the Application Menu.
• Force Quit: Use this option with precaution. It has the same effect as choose "Force Quit" in the "Apple Menu".
When you Launch an Application, you have 4 options:
- "Launch Without Activation": The Action doesn't bring the Application to the the foreground.
- "Launch And Hide Others": Once the Application is launched, all others Applications are hiden.
- "Launch And Hide": Launch the Application and then Hide it.
- "Launch a New Instance": If the application is not running, it launchs the Application. If it is already running, instead of bringing it to the foreground, the Action launchs another copy of the Application.
This function may not work with all Applications.


We help the young startup in getting recognised by various govt. agencies
If you are planning a startup, then you should register it. Registration of business is very important, it will give you many benefits, and it will protect your business and secure your rights against the third party and in the case of failure of registration you may have to face legal consequences. Registration of business is a primary thing for any business during incorporation. Registration of business will give you protection under the laws. For e.g., if you register your business under company laws or under LLP laws, then it will protect your business and you also.
MSME contribute largely in the socio-economic development of our country. MSMEs come under the Ministry of Micro, Small & Medium Enterprises and are required to be registered to avail benefits under the Micro, Small and Medium Enterprises Development (MSMED) Act. MSME registration is highly important, as it enables these enterprises in availing benefits from various government initiated schemes. MSMEs are classified in two categories, such as manufacturing and service enterprises.We also provide MSME registration services
Startups are becoming very popular in India. The government under the leadership of PM Narendra Modi has started and promoted Startup India. DIPP certification is needed to get government fund.
DIPP Certified business excels in Govt. tenders and get full support from government.Public procurement forms a very important part of Government activity and reform in Public Procurement is one of the top priorities of the present Government. Government e-Marketplace (GeM - gem.gov.in) is a very bold step of the Government with the aim to transform the way in which procurement of goods and services is done by the Government Ministries and Departments, Public Sector Undertakings and other apex autonomous bodies of the Central Government.


array wincache_ucache_meminfo ( void )
Retrieves information about memory usage by user cache.
Array of meta data about user cache memory usage or FALSE on failure The array returned by this function contains the following elements: memory_total - amount of memory in bytes allocated for the user cache memory_free - amount of free memory in bytes available for the user cache num_used_blks - number of memory blocks used by the user cache num_free_blks - number of free memory blocks available for the user cache memory_overhead - amount of memory in bytes used for the user cache internal structures


Last updated: 2018-01-19
Code version: 9094f4b
Tutor: Jan van de Broek
Think about the sampling unit (e.g. patient, cow).
1 person with multiple observations = ‘dependent’ data
Random independent variables
Add common fixed effect
If \(\epsilon\) were independent, so are \(y\).
(This is equivalent to the ANOVA)
Add a random number to both epsilons
This gives correlated data, due to the random effect.
With \(i\) subjects, \(j\) observations per subject
\(y_{ij} = \beta_0 + b_{0i} + \epsilon_{ij}\)
\(b_{0i} \sim N(0,\sigma_{int})\)
Equivalent to ANOVA model, but - group-effect = subject effect
If you take subject effect as fixed, you cannot generalize to other subjects Taking subject-effect as random with a known distribution, will allow you to generalize.
As all \(b_{0i}\) are drawn from the same distribution \(N(0, \sigma_{int})\). The correlation between intra-subject observation will be the same. This correlation structure is called the exchangeable correlation structure (equivalent to compound symmetry).
Target is not to get estimates of the subject-effects for individual subjects, but the distribution (variance) of the random subject effects
Difference intercept the same slope, analysis of covariance
\(y_{ij} = \alpha_i + \beta x + \epsilon_{ij}\)
\(y_{ij} = \alpha + (\alpha_i - \alpha) + \beta x + \epsilon_{ij}\)
\(y_{ij} = \beta_0 + b_{0i} + \beta_1 x + \epsilon_{ij}\)
Where \(b_{0i}\) as the random effect per subject, \(\beta_1\) the same for all subjects.
\(b_{0i} \sim N(0, \sigma_{intercept})\) Variance of population of which you draw ‘intercepts’
We can also take a fixed intercept, and random slopes for each subject. Then \(\beta_{i1} \sim N(0, \sigma_{slope})\)
Then the correlation between different time-points can be different.
So correlation \(cov(y_{i1}, y_{i2}) > cov(y_{i1}, y_{i3})\)
Random effects parts will be biased (variances \(/\sqrt{n}\) vs \(/\sqrt{n-1}\).
Get transformed likelihood that does not depend on fixed effects.
Restriced maximul likelihood estimating: REML
Wrong way to do it:
Fixed model 1 -> transformation 1 -> random effects part 1 Fixed model 2 -> transformation 2 -> random effects part 2
Comparing models: both fixed parts, and random effects parts; Both can vary at the same time (which makes it impossible to see if fixed parts are different and/or random effects are different)
In a mixed effects model:
Modelling is sequential
With full-model determine random part. Then get more parsimonious model for fixed-model.
Works with generalized linear models
require(dplyr)
data("ChickWeight")
str(ChickWeight)
Classes 'nfnGroupedData', 'nfGroupedData', 'groupedData' and 'data.frame': 578 obs. of 4 variables:
$ weight: num 42 51 59 64 76 93 106 125 149 171 ...
$ Time : num 0 2 4 6 8 10 12 14 16 18 ...
$ Chick : Ord.factor w/ 50 levels "18"<"16"<"15"<..: 15 15 15 15 15 15 15 15 15 15 ...
$ Diet : Factor w/ 4 levels "1","2","3","4": 1 1 1 1 1 1 1 1 1 1 ...
- attr(*, "formula")=Class 'formula' language weight ~ Time | Chick
.. ..- attr(*, ".Environment")=<environment: R_EmptyEnv>
- attr(*, "outer")=Class 'formula' language ~Diet
.. ..- attr(*, ".Environment")=<environment: R_EmptyEnv>
- attr(*, "labels")=List of 2
..$ x: chr "Time"
..$ y: chr "Body weight"
- attr(*, "units")=List of 2
..$ x: chr "(days)"
..$ y: chr "(gm)"
library(nlme)
fit1 <- lme(weight ~ factor(Time)+factor(Time):Diet,
random = ~factor(Time)+1|Chick,
data = ChickWeight %>% filter(Time <= 6 & Diet %in% c(1,2)),
method = "REML") # REML is default value for method
fit2 <- lme(weight ~ factor(Time)+factor(Time):Diet,
random = ~factor(Time)-1|Chick,
data = ChickWeight %>% filter(Time <= 6 & Diet %in% c(1,2)),
method = "REML")
fit3 <- lme(weight ~ factor(Time)+factor(Time):Diet,
random = ~1|Chick,
data = ChickWeight %>% filter(Time <= 6 & Diet %in% c(1,2)),
method = "REML")
summary(fit1)
Linear mixed-effects model fit by REML
Data: ChickWeight %>% filter(Time <= 6 & Diet %in% c(1, 2))
AIC BIC logLik
569.7023 621.0114 -265.8511
Random effects:
Formula: ~factor(Time) + 1 | Chick
Structure: General positive-definite, Log-Cholesky parametrization
StdDev Corr
(Intercept) 0.7591715 (Intr) fc(T)2 fc(T)4
factor(Time)2 3.3334221 0.509
factor(Time)4 3.6299054 0.388 0.772
factor(Time)6 6.8250079 0.187 0.455 0.865
Residual 0.9016205
Fixed effects: weight ~ factor(Time) + factor(Time):Diet
Value Std.Error DF t-value p-value
(Intercept) 41.40000 0.2635584 81 157.08091 0.0000
factor(Time)2 5.85000 0.7980458 81 7.33041 0.0000
factor(Time)4 14.54375 0.8704857 81 16.70763 0.0000
factor(Time)6 24.82898 1.5846995 81 15.66794 0.0000
factor(Time)0:Diet2 -0.70000 0.4564966 81 -1.53342 0.1291
factor(Time)2:Diet2 2.15000 1.5038361 81 1.42968 0.1567
factor(Time)4:Diet2 3.85625 1.5885473 81 2.42753 0.0174
factor(Time)6:Diet2 9.17102 2.7543575 81 3.32964 0.0013
Correlation:
(Intr) fc(T)2 fc(T)4 fc(T)6 f(T)0: f(T)2: f(T)4:
factor(Time)2 0.113
factor(Time)4 0.056 0.730
factor(Time)6 0.018 0.442 0.831
factor(Time)0:Diet2 -0.577 -0.065 -0.032 -0.011
factor(Time)2:Diet2 -0.235 -0.550 -0.397 -0.238 0.407
factor(Time)4:Diet2 -0.197 -0.419 -0.557 -0.459 0.341 0.770
factor(Time)6:Diet2 -0.106 -0.265 -0.484 -0.577 0.184 0.478 0.832
Standardized Within-Group Residuals:
Min Q1 Med Q3 Max
-1.47771978 -0.32984263 -0.02271753 0.30794810 1.89642815
Number of Observations: 118
Number of Groups: 30
summary(fit2)
Linear mixed-effects model fit by REML
Data: ChickWeight %>% filter(Time <= 6 & Diet %in% c(1, 2))
AIC BIC logLik
569.7023 621.0114 -265.8511
Random effects:
Formula: ~factor(Time) - 1 | Chick
Structure: General positive-definite, Log-Cholesky parametrization
StdDev Corr
factor(Time)0 0.7988770 fc(T)0 fc(T)2 fc(T)4
factor(Time)2 3.7849248 0.617
factor(Time)4 3.9943178 0.516 0.812
factor(Time)6 7.0108704 0.276 0.497 0.858
Residual 0.8666594
Fixed effects: weight ~ factor(Time) + factor(Time):Diet
Value Std.Error DF t-value p-value
(Intercept) 41.40000 0.2635624 81 157.07854 0.0000
factor(Time)2 5.85000 0.7980412 81 7.33045 0.0000
factor(Time)4 14.54375 0.8704832 81 16.70767 0.0000
factor(Time)6 24.82897 1.5846905 81 15.66803 0.0000
factor(Time)0:Diet2 -0.70000 0.4565035 81 -1.53339 0.1291
factor(Time)2:Diet2 2.15000 1.5038328 81 1.42968 0.1567
factor(Time)4:Diet2 3.85625 1.5885508 81 2.42753 0.0174
factor(Time)6:Diet2 9.17103 2.7543518 81 3.32965 0.0013
Correlation:
(Intr) fc(T)2 fc(T)4 fc(T)6 f(T)0: f(T)2: f(T)4:
factor(Time)2 0.113
factor(Time)4 0.056 0.730
factor(Time)6 0.018 0.442 0.831
factor(Time)0:Diet2 -0.577 -0.065 -0.032 -0.011
factor(Time)2:Diet2 -0.235 -0.550 -0.397 -0.238 0.407
factor(Time)4:Diet2 -0.197 -0.419 -0.557 -0.459 0.341 0.770
factor(Time)6:Diet2 -0.106 -0.265 -0.484 -0.577 0.184 0.478 0.832
Standardized Within-Group Residuals:
Min Q1 Med Q3 Max
-1.42044678 -0.31703810 -0.02182896 0.29601019 1.82286018
Number of Observations: 118
Number of Groups: 30
Without main effect of Diet, Diet is modeled as a nested effect.
getVarCov(fit1, type = "marginal")
Chick 1
Marginal variance covariance matrix
1 2 3 4
1 1.3893 1.8643 1.6464 1.5431
2 1.8643 15.0770 12.2710 13.1890
3 1.6464 12.2710 16.7060 24.0310
4 1.5431 13.1890 24.0310 49.9040
Standard Deviations: 1.1787 3.8829 4.0872 7.0642
anova(fit1, fit2, fit3)
Model df AIC BIC logLik Test L.Ratio p-value
fit1 1 19 569.7023 621.0114 -265.8511
fit2 2 19 569.7023 621.0114 -265.8511
fit3 3 10 657.7868 684.7916 -318.8934 2 vs 3 106.0845 <.0001
Does not work yet
library(lme4)
fit1 <-
ChickWeight %>%
filter(Time <= 10 & Diet %in% c(1,2)) %>%
lme4::lmer(formula = weight ~ Diet +
(factor(Time)|Chick), REML = T)
sessionInfo()
R version 3.4.3 (2017-11-30)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Sierra 10.12.6
Matrix products: default
BLAS: /Library/Frameworks/R.framework/Versions/3.4/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.4/Resources/lib/libRlapack.dylib
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] bindrcpp_0.2 nlme_3.1-131 dplyr_0.7.4
loaded via a namespace (and not attached):
[1] Rcpp_0.12.14 lattice_0.20-35 assertthat_0.2.0 digest_0.6.13
[5] rprojroot_1.2 grid_3.4.3 R6_2.2.2 backports_1.1.2
[9] git2r_0.20.0 magrittr_1.5 evaluate_0.10.1 pillar_1.1.0
[13] rlang_0.1.6 stringi_1.1.6 rmarkdown_1.8 tools_3.4.3
[17] stringr_1.2.0 glue_1.2.0 yaml_2.1.16 compiler_3.4.3
[21] pkgconfig_2.0.1 htmltools_0.3.6 bindr_0.1 knitr_1.18
[25] tibble_1.4.1
This R Markdown site was created with workflowr


This is a dataset corresponding to the paper "Longevity Returns to Political Office" by Barfort, Klemmensen & Larsen (2019). The purpose of this study was to find out whether and how winning an election influences the lifespan of politicians. To answer this question, the authors collected data on all U.S. gubernatorial elections from 1945 to 2012. In addition to the names and votes of the running candidates, the data includes information on their pre- and post-election life spans. See also the 'Details' section below.
governors
A tibble with 1,092 observations and 11 variables:
character variable indicating the state in which an election took place
integer variable indicating the year in which an election took place
character variable indicating the first name of a candidate
character variable indicating the last name of a candidate
character variable indicating a member's party
character variable indicating a member's sex
date variable indicating the candidate's date of death
character variable indicating whether a candidate was the challenger or incumbent
double variable indicating the percentage margin by which the election was won (positive values) or lost (negative values)
integer variable indicating the number of days a candidate lived after the election took place
integer variable indicating the number of days a candidate lived before the election took place
https://doi.org/10.7910/DVN/IBKYRX
To facilitate subsequent analysis, the raw data collected by the authors was edited in three ways. First, for a given election, only the two candidates who received the highest number of votes were included. Second, candidates with unknown dates of death were excluded, resulting in fewer observations for elections in recent years. Third, in a few instances, only the year of birth or death could be determined; in these cases, the date was taken to be July 1 of that year.
Table: Data summary
| Name | governors |
| Number of rows | 1092 |
| Number of columns | 11 |
| _______________________ | |
| Column type frequency: | |
| character | 6 |
| Date | 1 |
| numeric | 4 |
| ________________________ | |
| Group variables | None |
Variable type: character
| skim_variable | n_missing | complete_rate | min | max | empty | n_unique | whitespace |
| state | 0 | 1 | 4 | 14 | 0 | 50 | 0 |
| first_name | 0 | 1 | 2 | 11 | 0 | 299 | 0 |
| last_name | 0 | 1 | 3 | 11 | 0 | 615 | 0 |
| party | 0 | 1 | 8 | 11 | 0 | 3 | 0 |
| sex | 0 | 1 | 4 | 6 | 0 | 2 | 0 |
| status | 0 | 1 | 9 | 10 | 0 | 2 | 0 |
Variable type: Date
| skim_variable | n_missing | complete_rate | min | max | median | n_unique |
| died | 0 | 1 | 1946-12-21 | 2019-08-18 | 1996-07-20 | 683 |
Variable type: numeric
| skim_variable | n_missing | complete_rate | mean | sd | p0 | p25 | p50 | p75 | p100 | hist |
| year | 0 | 1 | 1964.85 | 13.38 | 1945.00 | 1954.00 | 1962.00 | 1974.00 | 2011 | ▇▆▃▂▁ |
| win_margin | 0 | 1 | 3.22 | 26.07 | -82.43 | -9.87 | 0.97 | 12.18 | 100 | ▁▃▇▁▁ |
| alive_post | 0 | 1 | 10309.56 | 4885.95 | 46.00 | 6418.75 | 10811.00 | 14123.75 | 22067 | ▃▆▇▆▂ |
| alive_pre | 0 | 1 | 18892.42 | 3181.47 | 11450.00 | 16561.00 | 18757.50 | 20995.75 | 30633 | ▂▇▆▂▁ |
David Kane


References
Adams, A. A. (2013). Bootstrapping Trust in Online Dating: Social Verification of Online Dating Profiles. Financial cryptography and data security: FC 2013 Workshops, USEC and WAHC 2013, Okinawa, Japan, April 1, 2013: Revised selected papers.
link.springer.com/chapter/10.1007/978-3-642-41320-9_10#page-2
Bargh, J. A., & Mckenna, K. Y. (2004). The Internet and Social Life. Annual Review of Psychology Annu. Rev. Psychol., 55(1), 573-590.
www.annualreviews.org/doi/pdf/10.1146/annurev.psych.55.090902.141922
Baumeister, R. F., & Leary, M. R. (1995). The need to belong: Desire for interpersonal attachments as a fundamental human motivation. Psychological Bulletin, 117, 497–529.
Boyd, d. m. and Ellison, N. B. (2007), Social Network Sites: Definition, History, and Scholarship. Journal of Computer-Mediated Communication, 13: 210–230.
onlinelibrary.wiley.com/doi/10.1111/j.1083-6101.2007.00393.x/full
Durning, A. T. (1992). How much is enough?: The consumer society and the future of the earth.
www.imagoearth.org/files/programs/Durning.pdf
Dutton, W. E. (1996). Information and Communication Technologies: Visions and Realities. Oxford: Oxford University Press
Ellison, N., Heino, R., Gibbs, J. (2006), Managing Impressions Online: Self-Presentation Processing the Online Dating Environment.
onlinelibrary.wiley.com/doi/10.1111/j.1083-6101.2006.00020.x/full
Finkel, E. J., Eastwick, P. W., Karney, B. R., Reis, H. T., & Sprecher, S. (2012). Online Dating: A Critical Analysis From the Perspective of Psychological Science. Psychological Science in the Public Interest, 13(1), 3-66.
https://www.psychologicalscience.org/pdf/PSPI-online_dating-proof.pdf
Higgins, E. T. (1987). Self-discrepancy: A theory relating self and affect. Psychological Review, 94(3), 319–340.
www.columbia.edu/cu/psychology/higgins/papers/HIGGINS=PSYCH%20REVIEW%201987.pdf
Hoffman, D. (2012). Internet indispensability, online social capital, and consumer well-being. Transformative consumer research for personal and collective well-being, 193-203.
Putnam, R. D. (2000). Bowling alone: The collapse and revival of American community. New York: Simon & Schuster.
archive.realtor.org/sites/default/files/BowlingAlone.pdf
Schacter, H. (2015). Love me tinder: A Psychological perspective on swiping. Psychology In Action.
www.psychologyinaction.org/2015/04/16/love-me-tinder-a-psychological-perspective-on-swiping/
Sritharan, R., Heilpern, K., Wilbur, C. J. and Gawronski, B. (2010), I think I like you: Spontaneous and deliberate evaluations of potential romantic partners in an online dating context. Eur. J. Soc.
onlinelibrary.wiley.com/doi/10.1002/ejsp.703/full


4
Name:
Justin Williams
Role:
DG Analyst
You have 4 pending actions of 10
60%
60% Complete
Settings
Logout
{{link.linkname}}
{{sublink.subLinkName}}


{% extends 'cooperazione_base.html' %} {% block container %}
The activities of Italian Development Cooperation are ruled by Italian Law n. 49 of 1987, which established the Directorate General for Development Cooperation of the Ministry of Foreign Affairs. Initiatives and beneficiary countries are selected according to international guidelines and commitments. Our activities are mainly focused on the African continent (Sub-Saharan Africa), on countries with which we have signed important international commitments (Afghanistan, Lebanon) and on areas where the presence of our country has deep historical roots (Latin America, Middle East and Mediterranean region).
Our primary areas of intervention are: the environment with particular attention to rural development, organic or conventional farming, alternative and renewable sources, gender policies and female empowerment, health and education.
Official Development Assistance (ODA), in quantitative terms, is not the main source of funding for development. Significant amounts are derived from the mobilization of the developing countries internal resources, from foreign investments, and international trade participation.
The ODA, particularly in less developed countries, plays a vital role in supporting local strategies to modernize institutions and commerce so that they benefit from global market opportunities, while, at the same time, protecting the most vulnerable segments of their populations.
Our main partners in the realization of cooperation programs are: Italian ministries, central and local public agencies, universities, NGOs, companies, the European Union, international organizations and developing countries.
{% endblock container %}


{{ title }} - JKW Wood Works
☰ Menu
Home
Products
Contact Us
About Us
{% block content %} {% endblock %}


| Package | Description |
|---|---|
| fotoshop |
fotoshop package contains the primary image editor and various command
processing methods.
|
| fotoshop.Events |
The Events package contains classes related to the applications controller.
|
| fotoshop.Filter |
Package containing the Filters that may be applied to the images being edited
by the application.
|
| Class and Description |
|---|
| ColorImage
Extends standard BufferedImage class with convenience functions
for getting/setting pixel values using the standard Color class
and converting the raster to a standard 24-bit direct colour format.
|
| Command
This class is adapted from the "World of Zuul" application.
|
| CommandWord
Representations for all the valid command words for the game
along with a string in a particular language.
|
| ImageStack
Image stack stores a stack of
ColorImage instances up to the
maximum . |
| Class and Description |
|---|
| Editor
Adapted from the fotoshop assignment example by Richard Jones
|
| Class and Description |
|---|
| ColorImage
Extends standard BufferedImage class with convenience functions
for getting/setting pixel values using the standard Color class
and converting the raster to a standard 24-bit direct colour format.
|


The cultured history of True American.
It was originally played on New Girl, introduced in season 1, episode 20: Normal.
The entire point of the game is to confuse anyone watching or playing, while getting really drunk. Naturally, we found some rules online and were pumped to try it.
We never considered that a game designed to be confusing wouldn't be that much fun.
You basically walked in circles for an hour playing the same three mini games the whole time.
So we made our own version!
Is every bit as ridiculous as the original game, but we added a lot of elements so it doesn't get boring if you play for a while.
Since our version requires special game cards, we made this site.
After we made some cards, we invited a few of our close friends over for the beta test on October 24, 2020.
They loved it, and the rest is history


Unit testing¶
Tests are setup using pythons default testing framework unittest. These tests are run each time new code is pushed to our Github repository using Travis. They can also be edited and run on your local machine as explained below.
In these explanations, we assume you have cloned a version of the qucat repository to your computer.
Running tests¶
Tests are located in the the tests
directory. These can be run from the command line
after navigating to the root directory of the qucat repository with the command
python -m unittest discover -v -s ./tests -p test_*.py
Each test file is dedicated to a specific part of the library,
and is generally paired with a specific file of the source code,
for example the file test/test_core.py
tests the functionalities of the
src/test_core.py
file.
To run only run one of the test files, test_core.py
for example, one can also run
python tests/test_core.py
Executing only a single test from a file is also possible by running for example
python tests/test_core.py SeriesRLC.test_frequency
Note
Some GUI tests have failed for a mysterious reason on certain operating systems, even thought the functionality they test works when tested manually.
Writing a basic test¶
Let us assume that a developer wishes to contribute a new module src/new.py
which contains a function f
which adds two numbers
One should then create a test/test_new.py
file which test if the
function works as expected.
This is one way of doing it
# Import python test framework
import unittest
import os
import sys
# Add the ./src/ folder to the system path
sys.path.append(os.path.join(os.path.join(os.path.dirname(os.path.dirname(__file__)),'src')))
# Import function to be tested
from new import f
class TestCase(unittest.TestCase):
def test_f_function(self):
# Check if f(1,2) is indeed equal to 3
self.assertEqual(f(1,2),3)
if __name__ == '__main__':
unittest.main()
For more details on the unittest framework, check this link.
Writing a test for a GUI functionality¶
Testing the GUI functionalities i.e. what
happens if I click here? is also possible in an automatic
way by simulating mouse motion, clicks or keystrokes events.
These test are located in test/test_gui.py
Creating these tests is also done through the GUI, and we present here a short tutorial on how to do so.
Let’s assume we want to test moving a resistor by clicking, dragging then dropping.
The correct location to add this test is in the
test/test_gui.py
file, with the following code
class TestMovingComponentsAround(AutomaticTesting):
def test_moving_resistor(self):
self.launch_gui_testing(force_build=False,run_slower=False)
The first time we run this file,
an empty GUI will open.
**Step 1: ** here we set the initial configuration for the
test, in this example we create and place a resistor, then close the GUI.
This circuit will be saved in the file
tests/gui_testing_files/test_moving_resistor/initial_netlist.txt
**Step 2: ** a second GUI will open in the initial configuration, and we now
perform the task we are testing.
Our actions will be recorded in the file
tests/gui_testing_files/test_moving_resistor/events.txt
later repeated in an automatic way when running this test. In this
example, we drag and drop the resistor to another location, then
close the GUI.
Upon closing the GUI, the final configuration of the circuit
is recorded in the file
tests/gui_testing_files/test_moving_resistor/final_netlist
The subsequent times we run this test no human intervention
is necessary.
A GUI will be opened in the initial configuration,
a sequence of events will be triggered,
and the final configuration of the circuit will be stored in the file
tests/gui_testing_files/test_moving_resistor/final_after_events_netlist.txt
and compared to the configuration created manually
tests/gui_testing_files/test_moving_resistor/final_netlist
.
If the files are identical, the test passes.
The function AutomaticTesting.launch_gui_testing
which implements
these functionalities takes two arguments.
By setting force_build = True
, the test is run as if for the first
time.
By setting run_slower = True
, the test is run very slowly
so that one can observe what the automatically generated sequence
of events is doing to the GUI.
This enables easy debugging of the test.
Writing a test based on a tutorial¶
All tutorials featured on the website are
jupyter notebooks
located in the folder docs_src/source/tutorials
and are
also run as tests.
These tests are located in test/test_tutorials.py
.
If one adds a new notebook, for example new_tutorial.ipynb
in the tutorials folder, one can test it by adding the following code
to the test/test_tutorials.py
script
class TestNewTutorial(TestTutorials):
def test_if_it_runs(self):
'''Runs the notebook new_tutorial.ipynb.
If an error is encountered the test fails
'''
self.run_tutorial('new_tutorial.ipynb')
def test_if_it_produces_the_right_answer(self):
'''Runs the notebook new_tutorial.ipynb
and stores all the variables defined in the notebook
as a dictionary called variables.
We then check if the variable called
"name_of_variable" is equal to 10,
the test will fail if it isnt.
'''
variables = self.run_tutorial('new_tutorial.ipynb')
x = variables['name_of_variable']
expected_value_of_variable = 10
self.assertEqual(x,expected_value_of_variable)


An interface is a set of property keys whose associated values match a specific specification. Any object that provides all the properties as described by an interface's specification conforms to that interface. An interface is not represented by a distinct object. There may be many separately implemented objects that conform to any interface. An individual object may conform to multiple interfaces.
The Disposable interface includes the property described in
| Property | Value | Requirements |
|---|---|---|
| `@@dispose` | A function. |
Invoking this method notifies the Disposable object that the caller does not intend to continue to use this object. This method should perform any necessary logic to perform explicit clean-up of the resource including, but not limited to, file system handled, streams, host objects, etc. When an exception is thrown from this method, it typically means that the resource could not be explicitly freed. If called more than once on the same object, the function should not throw an exception. However, this requirement is not enforced. When using a Disposable object, it is good practice to create the instance with a `try`-`using` statement, as the resource will be automatically disposed when the code within the `try`-`using` statement has been evaluated. |
The AsyncDisposable interface includes the property described in
| Property | Value | Requirements |
|---|---|---|
| `@@asyncDispose` | A function that returns a promise. |
Invoking this method notifies the AsyncDisposable object that the caller does not intend to continue to use this object. This method should perform any necessary logic to perform explicit clean-up of the resource including, but not limited to, file system handled, streams, host objects, etc. When an exception is thrown from this method, it typically means that the resource could not be explicitly freed. An AsyncDisposable object is not considered "disposed" until the resulting Promise has been fulfilled. If called more than once on the same object, the function should not throw an exception. However, this requirement is not enforced. When using an AsyncDisposable object, it is good practice to create the instance with a `try`-`using`-`await` statement, as the resource will be automatically disposed when the code within the `try`-`using`-`await` statement has been evaluated. |


Expand-assets Class
These docs have moved here.Reference for DEVELOPERS of new frames only!
Mixin to allow users to provide audio/video and image source values as either relative paths
within a base directory or as full paths.
If using along with other mixins, this should be listed LAST to enable those mixins to add to the set
of assets that need to be expanded if needed.
When adding this mixin to a frame, you will need to define a property of the frame
assetsToExpand
, which indicates which parameters might be source objects that need
expansion. assetsToExpand
should be an object with keys image
, video
, and audio
,
and each value should be an Array of parameter names that provide sources for resources
of the corresponding type. E.g.,
{
'image': ['leftObjectPic', 'rightObjectPic'],
'audio': ['introAudio', 'testAudio'],
'video': ['objectDemoVideo']
}
This is defined directly within your frame, e.g.:
export default ExpFrameBaseComponent.extend(ExpandAssets, {
...
type: 'exp-my-cool-frame',
assetsToExpand: {
'image': ['leftObjectPic', 'rightObjectPic'],
'audio': ['introAudio', 'testAudio'],
'video': ['objectDemoVideo']
},
...,
meta: {...},
actions: {...}
});
The user of your frame can then optionally provide baseDir
, audioTypes
, and
videoTypes
parameters to indicate how to expand relative paths.
How expansion works:
- Images: Suppose the list
assetsToExpand['image']
containscenterStimulus
. IfcenterStimulus
is provided as a full URL (with://
in it), nothing will happen to it. But ifcenterStimulus
is a string that is not a full URL, it will be transformed during thedidReceiveAttrs
hook tobaseDir + 'img/' + centerStimulus
. - Audio: Suppose the list
assetsToExpand['audio']
containsutterance1
. Ifutterance1
is a nonempty string (rather than an object/Array), e.g.,goodmorning
, andaudioTypes
has been set to['typeA', 'typeB']
, thenutterance1
will be expanded out to
[
{
src: 'baseDir' + 'typeA/goodmorning.typeA',
type: 'audio/typeA'
},
{
src: 'baseDir' + 'typeB/goodmorning.typeB',
type: 'audio/typeB'
}
]
- Video: Same as audio, but using the types from
videoTypes
. Important: During thedidReceiveAttrs
hook, your frame will acquire new properties[parameterName]_parsed
for each of the parameters named inassetsToExpand
. These properties will hold the expanded values. E.g., in the example above, you would now have acenterStimulus_parsed
property. This is what you should use for showing/playing images/audio/video in your frame template. Advanced use: the property names inassetsToExpand
can be either full parameter names as in the examples above, or can be of the formparameterName/subProperty
. If using theparameterName/subProperty
syntax, instead of processing the parameterparameterName
, we will expect that that parameter is either an object with propertysubProperty
(which will be expanded) or an Array of objects with propertysubProperty
(which will be expanded). The original value of theparameterName
parameter may in this case be mutated as assets are expanded. However, your frame will still also acquire a new property[parameterName]_parsed
which you should use for accessing the processed values. This avoids potential problems with the template being rendered using the original values and not updated.
Item Index
Properties
Properties
audioTypes
String[]
List of audio types to expect for any audio specified just
with a string rather than with a list of src/type objects.
If audioTypes is ['typeA', 'typeB']
and an audio source
is given as intro
, the audio source will be
expanded out to
[
{
src: 'baseDir' + 'typeA/intro.typeA',
type: 'audio/typeA'
},
{
src: 'baseDir' + 'typeB/intro.typeB',
type: 'audio/typeB'
}
]
Default: ['mp3', 'ogg']
baseDir
String
Base directory for where to find stimuli. Any image src
values that are not full paths will be expanded by prefixing
with baseDir
+ img/
. Any audio/video src values provided as
strings rather than objects with src
and type
will be
expanded out to baseDir/avtype/[stub].avtype
, where the potential
avtypes are given by audioTypes
and videoTypes
.
baseDir should include a trailing slash
(e.g., http://stimuli.org/myexperiment/
); if a value is provided that
does not end in a slash, one will be added.
Default: ''
videoTypes
String[]
List of video types to expect for any audio specified just
with a string rather than with a list of src/type objects.
If videoTypes is ['typeA', 'typeB']
and a video source
is given as intro
, the video source will be
expanded out to
[
{
src: 'baseDir' + 'typeA/intro.typeA',
type: 'video/typeA'
},
{
src: 'baseDir' + 'typeB/intro.typeB',
type: 'video/typeB'
}
]
Default: ['mp4', 'webm']


Projector constraints
[Using finite integer sets]
Collaboration diagram for Projector constraints:
Classes | |
| class | Gecode::SetExprCode |
| Code representing set-valued expressions for finite set projectors. More... | |
| class | Gecode::SetExpr |
| Set-valued expressions for finite set projectors. More... | |
| class | Gecode::Projector |
| Finite set projector specification. More... | |
| class | Gecode::ProjectorSet |
| Group of finite set projector specifications. More... | |
Specifying finite set projectors | |
| SetExpr | Gecode::operator- (const SetExpr &s) |
| Return set expression for the complement of s. | |
| SetExpr | Gecode::operator|| (const SetExpr &s, const SetExpr &t) |
| Return set expression for the union of s and t. | |
| SetExpr | Gecode::operator && (const SetExpr &, const SetExpr &) |
| Return set expression for the intersection of s and t. | |
| SetExpr | Gecode::operator- (const SetExpr &, const SetExpr &) |
| Return set expression for the difference of s and t. | |
Posting projection propagators | |
| void | Gecode::projector (Space *home, const SetVar &xa, const SetVar &ya, ProjectorSet &ps, bool negated=false) |
| Post projection propagators for binary constraint. | |
| void | Gecode::projector (Space *home, const SetVar &xa, const SetVar &ya, const BoolVar &bv, ProjectorSet &ps) |
| Post reified projection propagators for binary constraint. | |
| void | Gecode::projector (Space *home, const SetVar &xa, const SetVar &ya, const SetVar &za, ProjectorSet &ps, bool negated=false) |
| Post projection propagators for ternary constraint. | |
| void | Gecode::projector (Space *home, const SetVar &xa, const SetVar &ya, const SetVar &za, const BoolVar &bv, ProjectorSet &ps) |
| Post reified projection propagators for ternary constraint. | |
| void | Gecode::projector (Space *home, const SetVar &xa, const SetVar &ya, const IntVar &i, Projector &p) |
| Post projection propagator for cardinality constraint. | |
| void | Gecode::projector (Space *home, const SetVar &xa, const SetVar &ya, const SetVar &za, const IntVar &i, Projector &p) |
| Post projection propagator for cardinality constraint. |
Function Documentation
|
|
Return set expression for the complement of s.
Definition at line 62 of file set-expr.icc. |
|
|
Return set expression for the union of s and t.
Definition at line 65 of file set-expr.icc. |
|
|
Return set expression for the intersection of s and t.
Definition at line 70 of file set-expr.icc. |
|
|
Return set expression for the difference of s and t.
Definition at line 75 of file set-expr.icc. |
|
|
Post projection propagators for binary constraint. Post projection propagators for binary constraint on variables xa and ya, specified by ps. If negated is true, the negation of the specified constraint is propagated. Definition at line 28 of file projectors.cc. |
|
|
Post reified projection propagators for binary constraint. Post projection propagators for binary constraint on variables xa and ya, specified by ps, reified with bv. Definition at line 45 of file projectors.cc. |
|
|
Post projection propagators for ternary constraint. Post projection propagators for ternary constraint on variables xa, ya and za, specified by ps. If negated is true, the negation of the specified constraint is propagated. Definition at line 56 of file projectors.cc. |
|
|
Post reified projection propagators for ternary constraint. Post projection propagators for ternary constraint on variables xa, ya and za, specified by ps, reified with bv. Definition at line 74 of file projectors.cc. |
|
|
Post projection propagator for cardinality constraint. Post propagator for the constraint that i is the cardinality of the set represented by p, interpreted over the variables xa and ya. Definition at line 86 of file projectors.cc. |
|
|
Post projection propagator for cardinality constraint. Post propagator for the constraint that i is the cardinality of the set represented by p, interpreted over the variables xa, ya, and za. Definition at line 96 of file projectors.cc. |


Nectar robbery plant set Native data Fruit unpublished herbivory Navarro, flower fitness species yes effects effect damage floral native nectar Exotic exotic studies plants natural Ecol size herbivores {border-style Florivory px;} #ffffff;} impact results florivory reproductive < Fig levels novel robbing -., Plant mean sample artificial cost number study success Ecology enemies invasion meta-analysis negative Maron Seeds fruit habitats herbivory, included interactions introduced new performed significant stronger using Acanthaceae Zhang analysis community examined important invasive leaf px; {font-family Asteraceae Hendrix Irwin Navarro Oecologia Seed different enemy experimental font-size herbivory. hypothesis indicates indicating original plants, reproduction residence resistance role species. status type ERH Ericaceae Evol Lamiaceae Lett double; exotics female flowers importance indicate moderator perennial production records revealed species, susceptibility tolerance Amsberry Bot Corydalis Effects Fitness Gesneriaceae Hedges Isomeris Krupnick MMM Orobanchaceae Pollen RM. Scrophulariaceae Trapp Weis absence arborea border-color border-width ecological florivores grandiflora greater high information male pollination pollinators present publication random release robbers significantly simulated solid; vulgaris zero {font-style {font-weight (site Alpinia Apiaceae Balsamorhiza Click Ecological Effect Floral Fumariaceae Glechoma Gurevitch Linaria Oikos Pastinaca Ranunculaceae Sci Strauss Table Verbenaceae Viable additional analyzed bias biotic bold calculated compared consequences contingent courier; damage, distribution em; evolutionary foliar herbivore herbivorous higher imposed including level longituba magnitude needs newly plants. previous processes pt;} reduced related response result sagittata scale seed seeds spread suggest used


* The most basic workflow for working with a mouse: begin -> move -> end * Possibility to send update event (e.g. autoscroll, after container was scrolled top,left of its elements was changed)


Offense: Mario
Defense: Link
Flexible: Joker
These are just on the 3 characters I believe should be looked into by players who are still finding their preferred fighting style. More guides will come on the remaining characters in the game.


WorldWind Annotations
Label
Opacity
Scale
Corner radius
Leader size
Background color
Text color
Insets
Your browser does not support HTML5 Canvas.