kstrehlow commited on
Commit
2ff782c
·
verified ·
1 Parent(s): decd1c0

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +15 -20
README.md CHANGED
@@ -1,13 +1,11 @@
1
- UNICORN Project - Lava emergency management platform example data
2
 
3
  Partner: MITIGA, INGV-OE
4
 
5
  Project: UNICORN
6
 
7
 
8
-
9
-
10
- Overview
11
 
12
  The lava tool developed in the Unicorn project represents a coherent and easy-to-access platform for emergency managers and other stakeholders that integrates:
13
 
@@ -23,28 +21,26 @@ This dataset represents exemplary data produced by the lava platform for the Jun
23
 
24
  Note: the outputs included in this dataset are illustrative samples intended to showcase the system's capabilities, and do not represent final production outputs.
25
 
26
-
27
-
28
 
29
- Explanation of individual files
 
 
30
 
31
- 1. example-report_June2026-eruption.pdf
32
  This is the report that end-users signed up for the lava service receive upon triggering of the tool by INGV. It contains hazard maps, satellite imagery and impact
33
  forecasts for the ongoing eruption.
34
   
35
- 3. example-hazardmap_medium-scenario_June2026-eruption.tif
 
36
  This is the data behind the hazard map for the medium scenario shown in the pdf report in a geotiff format. Note that end-users are not receiving these data directly;
37
  this is only for exemplary purposes.
38
   
39
- 5. example-simulation_medium-scenario_June2026-eruption
 
40
  This is one example simulation file created by the system for the medium scenario. Note that end-users are not receiving these data directly; this is only for exemplary
41
  purposes.
42
 
43
-
44
-
45
   
46
- Methodology summary
47
-
48
 
49
  While the lava platform is built and maintained by Mitiga, its operational use depends on the local volcano observatory (the “operator”). The operator is distinguished from
50
  end-users, who only receive the final pdf report once the operator has launched the service.
@@ -55,20 +51,19 @@ the eruption has ended or is still ongoing.
55
  The service then runs on Mitiga computing systems following the below process:
56
 
57
  1. Create eruption scenarios consisting each of a vent location and a flow volume. Vent locations are placed along a grid considering the vent location uncertainty. The flow volume is calculated:
58
- - For finished eruptions: the flow volume is either provided or based on eruption duration and effusion rate.
59
- - For ongoing eruptions: three future scenarios are considered, assuming a further duration of 2 hours, 1 day or 1 month. These durations are then combined with the effusion rate to calculate the flow volume.
60
- - If the effusion rate is not provided by the user, default values for Etna volcano are stored on Mitiga systems.
61
  2. For each scenario, lava flow simulations are run using the MrLavaLoba simulator, which was tuned to Etna eruptions.
62
  3. The individual simulation footprints are combined into hazard maps.
63
  4. The hazard maps are combined with building locations from Open Street Map to estimate possible impact of the eruption.
64
  5. Pre- and posteruption satellite images are created using Sentinel-2 and MODIS data.
65
  6. A pdf report is created and send by email to the operator and the end-user
66
- 7.
67
  The overall time from triggering the service to receiving the email is usually less than 30 minutes.
68
 
69
-
70
 
71
- Application to the June 2026 eruption
72
 
73
  The system was run for the 26th June 2026 eruption to demonstrate capabilities. The flow was active for around 8 days. The following parameters were used:
74
  - Vent location 37.75452 / 15.005 with an uncertainty of 100m
 
1
+ # UNICORN Project - Lava emergency management platform example data
2
 
3
  Partner: MITIGA, INGV-OE
4
 
5
  Project: UNICORN
6
 
7
 
8
+ ## Overview
 
 
9
 
10
  The lava tool developed in the Unicorn project represents a coherent and easy-to-access platform for emergency managers and other stakeholders that integrates:
11
 
 
21
 
22
  Note: the outputs included in this dataset are illustrative samples intended to showcase the system's capabilities, and do not represent final production outputs.
23
 
 
 
24
 
25
+ ## Explanation of individual files
26
+
27
+ ### example-report_June2026-eruption.pdf
28
 
 
29
  This is the report that end-users signed up for the lava service receive upon triggering of the tool by INGV. It contains hazard maps, satellite imagery and impact
30
  forecasts for the ongoing eruption.
31
   
32
+ ### example-hazardmap_medium-scenario_June2026-eruption.tif
33
+
34
  This is the data behind the hazard map for the medium scenario shown in the pdf report in a geotiff format. Note that end-users are not receiving these data directly;
35
  this is only for exemplary purposes.
36
   
37
+ ### example-simulation_medium-scenario_June2026-eruption
38
+
39
  This is one example simulation file created by the system for the medium scenario. Note that end-users are not receiving these data directly; this is only for exemplary
40
  purposes.
41
 
 
 
42
   
43
+ ## Methodology summary
 
44
 
45
  While the lava platform is built and maintained by Mitiga, its operational use depends on the local volcano observatory (the “operator”). The operator is distinguished from
46
  end-users, who only receive the final pdf report once the operator has launched the service.
 
51
  The service then runs on Mitiga computing systems following the below process:
52
 
53
  1. Create eruption scenarios consisting each of a vent location and a flow volume. Vent locations are placed along a grid considering the vent location uncertainty. The flow volume is calculated:
54
+ - For finished eruptions: the flow volume is either provided or based on eruption duration and effusion rate.
55
+ - For ongoing eruptions: three future scenarios are considered, assuming a further duration of 2 hours, 1 day or 1 month. These durations are then combined with the effusion rate to calculate the flow volume.
56
+ - If the effusion rate is not provided by the user, default values for Etna volcano are stored on Mitiga systems.
57
  2. For each scenario, lava flow simulations are run using the MrLavaLoba simulator, which was tuned to Etna eruptions.
58
  3. The individual simulation footprints are combined into hazard maps.
59
  4. The hazard maps are combined with building locations from Open Street Map to estimate possible impact of the eruption.
60
  5. Pre- and posteruption satellite images are created using Sentinel-2 and MODIS data.
61
  6. A pdf report is created and send by email to the operator and the end-user
62
+
63
  The overall time from triggering the service to receiving the email is usually less than 30 minutes.
64
 
 
65
 
66
+ ### Application to the June 2026 eruption
67
 
68
  The system was run for the 26th June 2026 eruption to demonstrate capabilities. The flow was active for around 8 days. The following parameters were used:
69
  - Vent location 37.75452 / 15.005 with an uncertainty of 100m