Template:Interval Censored - Revision history

Kate Racaza: Redirected page to Types of Life Data

2012-08-14T07:01:52Z

← Older revision		Revision as of 07:01, 14 August 2012
Line 1:		Line 1:
	~~=====Interval Censored Data=====~~		#REDIRECT[[Types_of_Life_Data]]
	The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. For example, if we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. Specifically, if we inspect a certain unit at 100 hours and find it operating, and then perform another inspection at 200 hours to find that the unit is no longer operating, then the only information we have is that the unit failed at some point in the interval between 100 and 200 hours. This type of censored data is also called ''inspection data'' by some authors.

	[[~~Image:interval censoring.png\|center\|400px\|~~]]

Kate Racaza at 10:45, 2 July 2012

2012-07-02T10:45:19Z

← Older revision		Revision as of 10:45, 2 July 2012
Line 1:		Line 1:
	=====Interval Censored=====		=====Interval Censored Data=====
	The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. If we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. ~~More specifically~~, if we inspect a certain unit at 100 hours and find it is operating and then perform another inspection at 200 hours to find that the unit is no longer operating, we ~~know~~ that ~~a failure occurred~~ in the interval between 100 and 200 hours. ~~In other words, the only information we have is that it failed in a certain interval~~ of ~~time. This~~ is also called ''inspection data'' by some authors.		The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. For example, if we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. Specifically, if we inspect a certain unit at 100 hours and find it operating, and then perform another inspection at 200 hours to find that the unit is no longer operating, then the only information we have is that the unit failed at some point in the interval between 100 and 200 hours. This type of censored data is also called ''inspection data'' by some authors.

	[[Image:interval censoring.png\|center\|~~250px~~\|]]		[[Image:interval censoring.png\|center\|400px\|]]

Nicolette Young: /* Interval Censored */

2012-04-25T17:22:37Z

Interval Censored

← Older revision		Revision as of 17:22, 25 April 2012
Line 2:		Line 2:
	The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. If we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. More specifically, if we inspect a certain unit at 100 hours and find it is operating and then perform another inspection at 200 hours to find that the unit is no longer operating, we know that a failure occurred in the interval between 100 and 200 hours. In other words, the only information we have is that it failed in a certain interval of time. This is also called ''inspection data'' by some authors.		The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. If we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. More specifically, if we inspect a certain unit at 100 hours and find it is operating and then perform another inspection at 200 hours to find that the unit is no longer operating, we know that a failure occurred in the interval between 100 and 200 hours. In other words, the only information we have is that it failed in a certain interval of time. This is also called ''inspection data'' by some authors.

	[[Image:interval censoring.png\|center\|~~400px~~\|]]		[[Image:interval censoring.png\|center\|250px\|]]

Nicolette Young: /* Interval Censored */

2012-03-13T15:58:22Z

Interval Censored

← Older revision		Revision as of 15:58, 13 March 2012
Line 2:		Line 2:
	The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. If we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. More specifically, if we inspect a certain unit at 100 hours and find it is operating and then perform another inspection at 200 hours to find that the unit is no longer operating, we know that a failure occurred in the interval between 100 and 200 hours. In other words, the only information we have is that it failed in a certain interval of time. This is also called ''inspection data'' by some authors.		The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. If we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. More specifically, if we inspect a certain unit at 100 hours and find it is operating and then perform another inspection at 200 hours to find that the unit is no longer operating, we know that a failure occurred in the interval between 100 and 200 hours. In other words, the only information we have is that it failed in a certain interval of time. This is also called ''inspection data'' by some authors.

	[[Image:~~ldachp4fig3~~.~~gif\|thumb~~\|center\|400px\|]]		[[Image:interval censoring.png\|center\|400px\|]]

Pantelis: /* Interval Censored */

2011-10-29T14:22:51Z

Interval Censored

← Older revision		Revision as of 14:22, 29 October 2011
Line 2:		Line 2:
	The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. If we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. More specifically, if we inspect a certain unit at 100 hours and find it is operating and then perform another inspection at 200 hours to find that the unit is no longer operating, we know that a failure occurred in the interval between 100 and 200 hours. In other words, the only information we have is that it failed in a certain interval of time. This is also called ''inspection data'' by some authors.		The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. If we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. More specifically, if we inspect a certain unit at 100 hours and find it is operating and then perform another inspection at 200 hours to find that the unit is no longer operating, we know that a failure occurred in the interval between 100 and 200 hours. In other words, the only information we have is that it failed in a certain interval of time. This is also called ''inspection data'' by some authors.

	[[Image:ldachp4fig3.gif\|thumb\|center\|~~300px~~\|]]		[[Image:ldachp4fig3.gif\|thumb\|center\|400px\|]]

Pantelis: Created page with '=====Interval Censored===== The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the unit…'

2011-10-29T14:21:17Z

Created page with '=====Interval Censored===== The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the unit…'

New page

=====Interval Censored=====
The second type of censoring is commonly called ''interval censored data''. Interval censored data reflects uncertainty as to the exact times the units failed within an interval. This type of data frequently comes from tests or situations where the objects of interest are not constantly monitored. If we are running a test on five units and inspecting them every 100 hours, we only know that a unit failed or did not fail between inspections. More specifically, if we inspect a certain unit at 100 hours and find it is operating and then perform another inspection at 200 hours to find that the unit is no longer operating, we know that a failure occurred in the interval between 100 and 200 hours. In other words, the only information we have is that it failed in a certain interval of time. This is also called ''inspection data'' by some authors.

[[Image:ldachp4fig3.gif|thumb|center|300px|]]