2004
DOI: 10.1007/978-3-540-24606-0_21
|View full text |Cite
|
Sign up to set email alerts
|

Lessons from a Sensor Network Expedition

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

4
238
0
3

Year Published

2004
2004
2007
2007

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 325 publications
(245 citation statements)
references
References 16 publications
4
238
0
3
Order By: Relevance
“…The water made the humidity sensor malfunction and return abnormally high readings. This kind of physical failure is not uncommon and is recoverable [11]. After being dried, the sensor returned to normal operation.…”
Section: Light (Adc Mv)mentioning
confidence: 96%
See 1 more Smart Citation
“…The water made the humidity sensor malfunction and return abnormally high readings. This kind of physical failure is not uncommon and is recoverable [11]. After being dried, the sensor returned to normal operation.…”
Section: Light (Adc Mv)mentioning
confidence: 96%
“…Both GDI ([8] [11]) and PODS [2] deployed sensor networks in outdoor environments mainly for the purpose of system performance study. Specifically, GDI deployed a multi-tier sensor network for habit monitoring whereas PODS was deployed in Hawaii Volcanoes National Park.…”
Section: Related Workmentioning
confidence: 99%
“…Szewczyk et al 9 11 This approach solely focuses on identifying faults, and is based on their stated assumption that identifying a fault consumes a majority of the time involved in handling a failure for Internet service providers. The authors postulate that once a fault has been detected, the fix involves simple techniques such as rebooting a node.…”
Section: -Fault Detection-mentioning
confidence: 99%
“…1,2 In sensor networks, interactions between sensor hardware, protocols, and environmental characteristics are hard to predict, making application design an iterative process between debugging and deployment. 3 For example, owing to flaky or variable link connectivity, post-deployment environments can present unexpected combinations of inputs, or stimulate untested control paths in routing and transport code, uncovering new bugs and necessitating different application designs.…”
mentioning
confidence: 99%
“…In the life cycle of a WSN it becomes necessary to add new nodes to the network. Nodes cease to operate due to empty batteries, electrial or mechanical failure and need replacement [4]. In LEAP, K I is present in the hostile environment every time new nodes are added.…”
Section: Introductionmentioning
confidence: 99%