|
|
| (4 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | <div style=background:#c62828 border:#f44336>
| |
| − | [[Image:MC1-2019.jpg|200px|Logo]]
| |
| − | <font size = 5; color="#FAFAFA"><b>VAST Challenge 2019: Mini-Challenge 1</b></font>
| |
| − | </div>
| |
| − | {|style="background-color:#d32f2f; color:#7fc6cb; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
| |
| − | | style="background:none;" width="1%" |
| |
| − | | style="padding:0.3em; font-size:100%; background-color:#d32f2f; text-align:center; color:#7fc6cb" width="25%" |
| |
| − | [[Temp_file_RLzx |
| |
| − | <font color="#FAFAFA" size=2><b>Problem & Tasks</b></font>]]
| |
| | | | |
| − | | style="background:none;" width="1%" |
| |
| − | | style="padding:0.3em; font-size:100%; background-color:#d32f2f; text-align:center; color:#7fc6cb" width="25%" |
| |
| − | [[Temp file RLzx_DataAnalysisTransformation |
| |
| − | <font color="#FAFAFA" size=2><b>Data Analysis & Transformation</b></font>]]
| |
| − |
| |
| − | |style="padding:0.3em; font-size:100%; background-color:#d32f2f; text-align:center; color:#7fc6cb" width="25%" |
| |
| − | [[Temp_file_RLzx_Interaction_Visualization |
| |
| − | <font color="#FAFAFA" size=2><b>Interactive Visualization</b></font>]]
| |
| − |
| |
| − | | style="background:none;" width="1%" |
| |
| − | | style="padding:0.3em; font-size:100%; background-color:#d32f2f; text-align:center; color:#7fc6cb" width="25%" |
| |
| − | [[Temp_file_RLzx_Answers |
| |
| − | <font color="#FAFAFA" size=2><b>Answers</b></font>]]
| |
| − |
| |
| − | |}
| |
| − |
| |
| − | === Q1: Emergency responders will base their initial response on the earthquake shake map. Use visual analytics to determine how their response should change based on damage reports from citizens on the ground. How would you prioritize neighborhoods for response? Which parts of the city are hardest hit? ===
| |
| − |
| |
| − | <strong>STATIC SENSOR READINGS</strong></br>
| |
| − |
| |
| − | In terms of radiation level, healthy reading level was set at 25cpm, when any sensor readings that exceed this healthy level; attention need to be given to the respective sensor. Based on the readings, before '''8 April 2020 04:00PM''', radiation level shows minor fluctuation (relatively stable in terms of changes in reading); however, after '''8 April 2020 04:00PM''', there are significant spikes of radiation readings spotted across all sensors but especially sensor '''12-JadeBridge, 13-SafeTown, 14-CheddarFord, and 15-SafeTown_Nuclear''' have the noisiest spikes among other sensors on this day. In addition, notable that after '''8 April 2020 10:06:25PM''', sensor 15-SafeTown_Nuclear has some missing readings but the readings start to appear again on '''10 April 2020 8:47PM'''. Some possible reason could be due to location sensor 15-SafeTown_Nuclear that located near to the power plant.
| |
| − |
| |
| − | === Q2: Use visual analytics to show uncertainty in the data. Compare the reliability of neighborhood reports. Which neighborhoods are providing reliable reports? Provide a rationale for your response. ===
| |
| − |
| |
| − | <center><strong>Measure reliability among neighbourhoods</strong></center></br>
| |
| − |
| |
| − | <div><center><ul>
| |
| − | <li style="display: inline-block;" id="F1.1"> [[File:Ronald.Lay.2017_Reliability_Among_Neighbourhoods.PNG|thumb|none|500px|''Figure 2.1 - Overall intensity readings over time period'']] </li>
| |
| − | </ul></center></div>
| |
| − |
| |
| − | Based on Figure 2.1, there are 3 key analysis:
| |
| − | * <b>Downtown, Northwest and Weston </b> provide the most reliable reports among all the neighborhoods
| |
| − | * <b>Wilson Forest</b> provides the least reliable reports
| |
| − | * As highlighted in oval red, there are occasional periods where there are simply no reports. The possible cause may point to power/server outages
| |
| − | <p>Need to add more here</p>
| |
| − |
| |
| − | <center><strong>Delayed reports</strong></center></br>
| |
| − |
| |
| − | <div><center><ul>
| |
| − | <li style="display: inline-block;" id="F1.1"> [[File:Ronald.Lay.2017_Delayed_Report.PNG|thumb|none|500px|''Figure 2.1 - Delayed reporting'']] </li>
| |
| − | </ul></center></div>
| |
| − | Power outages and other infrastructural problem result in delayed reports (Indicated by red ovals) and the server does not process the information until the power is restored. The explanation of number annotation is as followed: <br/>
| |
| − | *<p><b>1&3</b>: There are very few amount of reported damage reports due to occasional power outages occurring in many of the neighborhoods. </p>
| |
| − | *<p><b>2</b>:The timestamp is only recorded when the power is restored as indicated in number 2, resulting in sudden increase in the amount of reports recorded on Thursday 3 to 5 PM. </p>
| |
| − |
| |
| − | <center><strong>Delayed reports per neighbour</strong></center></br>
| |
| − |
| |
| − | <div><center><ul>
| |
| − | <li style="display: inline-block;" id="F1.1"> [[File:Ronald.Lay.2017_Delayed_Report_Per_Neighbour.PNG|thumb|none|500px|''Figure 2.2 - Delayed reporting per neighbour'']] </li>
| |
| − | </ul></center></div>
| |
| − |
| |
| − | === Q3: How do conditions change over time? How does uncertainty in data change over time? Describe the key changes you see. ===
| |
