27.03.2013 Views

SPSS® 12.0 Command Syntax Reference

SPSS® 12.0 Command Syntax Reference

SPSS® 12.0 Command Syntax Reference

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1550 SURVIVAL<br />

• INTERVALS produces life tables computed from 0 to 12 months at one-month intervals<br />

and from 13 to 24 months at three-month intervals.<br />

Example<br />

SURVIVAL ONSSURV BY TREATMNT (1,3)<br />

/STATUS = OUTCOME (3,4) FOR ONSSURV<br />

/INTERVALS = THRU 50 BY 6.<br />

• On the INTERVALS subcommand, the value following BY (6) does not divide evenly into<br />

the period to which it applies (50). Thus, the endpoint of the period is adjusted upward to<br />

the next even multiple of the BY value, resulting in a period of 54 with 9 intervals of 6<br />

units each.<br />

Example<br />

SURVIVAL ONSSURV BY TREATMNT (1,3)<br />

/STATUS = OUTCOME (3,4) FOR ONSSURV<br />

/INTERVALS = THRU 50 BY 6 THRU 100 BY 10 THRU 200 BY 20.<br />

• Multiple THRU and BY specifications are used on the INTERVAL subcommand to divide<br />

the period of time under examination into intervals of different lengths.<br />

• The first THRU and BY specifications are adjusted to produce even intervals as in the<br />

previous example. As a result, the following THRU and BY specifications are automatically<br />

readjusted to generate 5 intervals of 10 units (through 104), followed by 5 intervals<br />

of 20 units (through 204).<br />

STATUS Subcommand<br />

To determine whether the terminal event has occurred for a particular observation, SURVIVAL<br />

checks the value of a status variable. STATUS lists the status variable associated with each<br />

survival variable and the codes that indicate that a terminal event occurred.<br />

• Specify a status variable followed by a value range enclosed in parentheses. The value<br />

range identifies the codes that indicate that the terminal event has taken place. All<br />

cases with non-negative times that do not have a code in the value range are classified<br />

as censored cases, which are cases for which the terminal event has not yet occurred.<br />

• If the status variable does not apply to all the survival variables, specify FOR and the name<br />

of the survival variable(s) to which the status variable applies.<br />

• Each survival variable on TABLES must have an associated status variable identified by a<br />

STATUS subcommand.<br />

• Only one status variable can be listed on each STATUS subcommand. To specify multiple<br />

status variables, use multiple STATUS subcommands.<br />

• If FOR is omitted on the STATUS specification, the status-variable specification applies to<br />

all of the survival variables not named on another STATUS subcommand.<br />

• If more than one STATUS subcommand omits the keyword FOR, the final STATUS<br />

subcommand without FOR applies to all survival variables not specified by FOR on other<br />

STATUS subcommands. No warning is printed.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!