Hazard assessment module - Revision history

Admin: /* Information shared within the InfoEx */

2019-11-17T23:31:04Z

‎Information shared within the InfoEx

Admin: /* Settings */

2019-11-17T23:29:53Z

‎Settings

Admin at 23:23, 17 November 2019

2019-11-17T23:23:40Z

Admin: /* Step 1: Avalanche problems (Fig. 1) */

2017-11-10T23:08:57Z

‎Step 1: Avalanche problems (Fig. 1)

Admin: /* Step 1: Avalanche problems (Fig. 1) */

2017-11-10T23:08:35Z

‎Step 1: Avalanche problems (Fig. 1)

Admin at 00:05, 10 November 2017

2017-11-10T00:05:33Z

Admin: /* Functionality */

2017-03-25T18:09:43Z

‎Functionality

Admin: /* Information shared within the InfoEx */

2017-03-20T23:55:49Z

‎Information shared within the InfoEx

Admin: /* Step 2: Avalanche hazard (Fig. 3) */

2017-03-20T23:44:07Z

‎Step 2: Avalanche hazard (Fig. 3)

Admin: /* Step 1: Avalanche problems (Fig. 1) */

2017-03-20T23:32:49Z

‎Step 1: Avalanche problems (Fig. 1)

@@ Line 137: / Line 137: @@
 * The hazard assessments are presented in the 'Avalanche Hazard' table of reports.
 * The assessments are presented for the location(s) that were associated with the workflow.
-* For a given day, reports only show the latest assessments submitted for a workflow location. For example, if you include the hazard assessment module both in your AM and PM workflows, reports will only show one of these assessments. Depending on the time of the day, it will be either the AM or PM assessments.
+* For a given day, reports only show the latest assessments submitted for a workflow location. For example, if you include the hazard assessment module both in your AM and PM workflows, reports will only show one of these assessments. Depending on the time of the day, it will be either the AM or PM assessments. Use the "Include Proprietary Data?" checkbox to view all modules for a day.
 ==Other workflow modules==

@@ Line 121: / Line 121: @@
 * '''Name'''<br/>Name of the workflow step shown in the header of the workflow. It is recommended that you choose a short name (e.g., 'Av Hzd' instead of 'Avalanche Hazard') to keep the navigation bar of the workflow as tidy as possible.
 * '''Elevation Bands'''<br/>Specify whether you want to rate the conditions for each elevation band (alpine, treeline, below treeline) individually or just a single, general rating. With the three elevation band setting you will be presented with three hazard charts in the second step of the assessment process (one for each elevation band); with the general setting only a single general hazard chart.
 * '''Hazard'''<br/>Specify whether you want to include hazard ratings or no ratings at all in your assessment process.
 ==<span style="color: #CC0000;">Information shared within the InfoEx</span>==

@@ Line 12: / Line 12: @@
 * If you are online when you initiate a [[Definitions#WorkflowInstance|workflow instance]] the fields will be prefilled from the last workflow instance with the same location(s). Once the workflow instance has been loaded, you can complete the workflow in an offline mode.
 * You can initiate a [[Definitions#WorkflowInstance|workflow instance]] when you are offline, and the fields will be filled with the latest cached information on the computer. This will be up to date unless workflows have been submitted using other computers since you were last online on the computer you are currently using.
-* If you submit whilst offline the workflow will be uploaded to the InfoEx server the next time you are online. WARNING: If the internet connection is lost whilst this is being done, the workflow will not be submitted and you will lose the data.
+* If you submit whilst offline the workflow will be uploaded to the InfoEx server the next time you are online. WARNING: If the internet connection is lost whilst this is being done, the workflow may not be submitted and you may lose the data.
 ==Functionality==
@@ Line 19: / Line 19: @@
 # Assessing the overall hazard given the existing avalanche problems
-If you are not interested in the highly structured approach of the conceptual model of avalanche hazard, the [[Hazard comment module]] offers a low-tech alternative that allows you to enter a free-form description of the current avalanche problems and the resulting avalanche hazard. It is only possible to have either a single hazard assessment or a single hazard comment step in your workflow, not both.
+If you are not interested in the highly structured approach of the conceptual model of avalanche hazard, the [[Hazard comment module]] offers a low-tech alternative that allows you to enter a free-form description of the current avalanche problems and the resulting avalanche hazard.
 The data entry fields of this workflow module are automatically pre-populated with the last Avalanche Problems and Hazard Ratings that were submitted for the location(s) associated with the workflow.
@@ Line 26: / Line 26: @@
 Any workflow template with a hazard assessment module step will automatically have a [[Workflow summary]] step added at the end of the workflow. This summary allows users to review their observations and assessments before they are submitted.
-The assessments submitted via the hazard assessment module are associated with the location(s) specified for the workflow in 'Manage Workflow Definitions'.
+The assessments submitted via the hazard assessment module are associated with the location(s) specified for the workflow in 'Manage Workflow Definitions' (or the location(s) associated with this hazard assessment module step if you have more than one hazard assessment module in the workflow).
 It is possible to complete the hazard assessment step in a workflow without internet connectivity.
@@ Line 40: / Line 40: @@
 |class="StepNum" | 1.
 |Click on {{ButtonBlue|Add Av Problem}} to add a new avalanche problem. The new problem is added to the top of the list of existing avalanche problems.
-{{Issue|Although a new avalanche problem is added to the top of the list, avalanche problems have no ordering associated with them anywhere they are present in InfoEx so could appear in any order at any time. |IssueNoImage|518|Jan.11, 2017}}
 |-
 |class="StepNum" | 2.
@@ Line 71: / Line 71: @@
 * '''Sensitivity to Trigger''' (mandatory)<br/>Determine the Sensitivity to Triggers based on what kind of triggering will initiate avalanches of any size within the defined location.<br/>See [[Sensitivity to triggers definition table]] for more information on sensitivity to triggers.
 * [[File:HzdChart.png|300px|thumb|right|Fig. 2: Hazard chart with handles for minimum, typical and maximum values for likelihood of triggering and destructive size.]] '''Likelihood of Triggering and Destructive Size''' (mandatory)<br/>Use the blobber on the hazard chart (Fig. 2) to indicate:

@@ Line 77: / Line 77: @@
 : Click on the blobber and drag to move the entire shape around on the chart. Click on the individual handles and drag to change the locations of the minimum, typical and maximum values for likelihood of triggering and destructive size. The handles automatically snap to the grid points of the chart.
 {{Note|The size and location of the blobber of an avalanche problem represent the typical expected values (center point) and the expected variability (min-max) in the terrain. The size of the blobber is not intended to represent the confidence of the forecasters.|NoteWithImage}}
-{{Note|If multiple handles are collapsed in a single point (e.g., minimum and typical value for destructive size on same grid point), you need to move the handle for the min or max value off before you can can access the handle for the typical values again. Or click on the {{ButtonGrey|Reset Chart;}} button to start again.|NoteWithImage}}
+{{Note|If multiple handles are collapsed in a single point (e.g., minimum and typical value for destructive size on same grid point), you need to move the handle for the min or max value off before you can can access the handle for the typical values again. Or click on the {{ButtonGrey|Reset Chart}} button to start again.|NoteWithImage}}
 * '''Comment'''<br/> Add any additional comments that help describe the character of the avalanche problem.

@@ Line 77: / Line 77: @@
 : Click on the blobber and drag to move the entire shape around on the chart. Click on the individual handles and drag to change the locations of the minimum, typical and maximum values for likelihood of triggering and destructive size. The handles automatically snap to the grid points of the chart.
 {{Note|The size and location of the blobber of an avalanche problem represent the typical expected values (center point) and the expected variability (min-max) in the terrain. The size of the blobber is not intended to represent the confidence of the forecasters.|NoteWithImage}}
-{{Note|If multiple handles are collapsed in a single point (e.g., minimum and typical value for destructive size on same grid point), you need to move the handle for the min or max value off before you can can access the handle for the typical values again.|NoteWithImage}}
+{{Note|If multiple handles are collapsed in a single point (e.g., minimum and typical value for destructive size on same grid point), you need to move the handle for the min or max value off before you can can access the handle for the typical values again. Or click on the {{ButtonGrey|Reset Chart;}} button to start again.|NoteWithImage}}
 * '''Comment'''<br/> Add any additional comments that help describe the character of the avalanche problem.

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Requirements|UserLevel=Submission moderator and higher|Connectivity=Online and partial offline}}
+{{Requirements|UserLevel=Submission moderator and higher|Connectivity=Online and offline}}
-This document describes the functionality of the 'hazard assessment' workflow module and how to properly configure if for a workflow.
+This document describes the functionality of the 'hazard assessment' workflow module and how to properly configure it for a workflow.
 '''Required permissions:'''
@@ Line 9: / Line 9: @@
 '''Required connectivity:'''
-* You need to be online to create a new  or edit an existing [[Definitions#WorkflowTemplate|workflow template]].
+* You need to be online to create a new or edit an existing [[Definitions#WorkflowTemplate|workflow template]].
-* You need to be online to initiate a [[Definitions#WorkflowInstance|workflow instance]] for the fields to be properly prefilled from the last workflow instance with the same location(s). Once the workflow instance has been loaded, you can complete the workflow on an offline mode.
+* If you are online when you initiate a [[Definitions#WorkflowInstance|workflow instance]] the fields will be prefilled from the last workflow instance with the same location(s). Once the workflow instance has been loaded, you can complete the workflow in an offline mode.
-* You can initiate a [[Definitions#WorkflowInstance|workflow instance]] when you are offline, but none of the fields will be prefilled and you will start with an completely blank copy.
+* You can initiate a [[Definitions#WorkflowInstance|workflow instance]] when you are offline, and the fields will be filled with the latest cached information on the computer. This will be up to date unless workflows have been submitted using other computers since you were last online on the computer you are currently using.
-* You need to be online to submit your observations and assessments at the end of your workflow.
+* If you submit whilst offline the workflow will be uploaded to the InfoEx server the next time you are online. WARNING: If the internet connection is lost whilst this is being done, the workflow will not be submitted and you will lose the data.
 ==Functionality==

@@ Line 22: / Line 22: @@
 The data entry fields of this workflow module are automatically pre-populated with the last Avalanche Problems and Hazard Ratings that were submitted for the location(s) associated with the workflow.
-{{Note|If you have multiple workflows for a location (e.g., AM and PM meetings), the information is pre-populated from the last time you submitted any workflow for the location. For example, in a regular rotation, the snowpack step in the PM meeting is pre-populated with information from the AM meeting and the next AM meeting is pre-populated with information from the PM meeting of the previous day.}}
+{{Note|If you have multiple workflows for a location (e.g., AM and PM meetings), the information is pre-populated from the last time you submitted any workflow for the location. For example, in a regular rotation, the hazard assessment step in the PM meeting is pre-populated with information from the AM meeting and the next AM meeting is pre-populated with information from the PM meeting of the previous day.}}
 Any workflow template with a hazard assessment module step will automatically have a [[Workflow summary]] step added at the end of the workflow. This summary allows users to review their observations and assessments before they are submitted.

@@ Line 126: / Line 126: @@
 ==<span style="color: #CC0000;">Information shared within the InfoEx</span>==
 All of the information entered in this workflow module is shared within the InfoEx in the following manner:
-* The characterisations of the existing avalanche problems is presented in the 'Avalanche Problems' table of the InfoEx report.
+* The characterizations of the existing avalanche problems are presented in the 'Avalanche Problems' and 'Avalanche Hazard' tables of reports.
-* The overall stability and hazard assessments are presented in the 'Avalanche Hazard' table of the InfoEx report.
+* The hazard assessments are presented in the 'Avalanche Hazard' table of reports.
-* The assessments are presented in the InfoEx under the location(s) that were associated with the workflow.
+* The assessments are presented for the location(s) that were associated with the workflow.
-* For a given day, the InfoEx report only shows the last assessments submitted for a workflow location. For example, if you include the snowpack module both in your AM and PM workflow, the InfoEx report will only show one of these assessments. Depending on the time of the day, it will be either the AM or PM assessments.
+* For a given day, reports only show the latest assessments submitted for a workflow location. For example, if you include the hazard assessment module both in your AM and PM workflows, reports will only show one of these assessments. Depending on the time of the day, it will be either the AM or PM assessments.
 ==Other workflow modules==

@@ Line 89: / Line 89: @@
 ===Step 2: Avalanche hazard (Fig. 3)===
-[[File:HzdAssessmentModuleStep2.png|300px|thumb|right|Fig. 3: Hazard assessment workflow module step 2: Avalanche hazard]] After the identified and characterized the current avalanche problems, the second step of the hazard assessment process allows you to discuss and rate the overall hazard. Depending on your [[#Settings|settings]], you will be presented with one general or three elevation-specific hazard charts (Fig. 3).
+[[File:HzdAssessmentModuleStep2.png|300px|thumb|right|Fig. 3: Hazard assessment workflow module step 2: Avalanche hazard]] Having identified and characterized the current avalanche problems, the second step of the hazard assessment process allows you to discuss and rate the overall hazard. Depending on your [[#Settings|settings]], you will be presented with one general or three elevation-specific hazard charts (Fig. 3).
 {|class="TblSteps"

← Older revision		Revision as of 23:32, 20 March 2017
Line 68:		Line 68:


−	* '''~~Spatial~~ Distribution''' (mandatory)<br/>Determine the density and distribution of the instability within the defined location.<br/>See [[Spatial distribution definition table]] for more information on spatial distribution.	+	* '''Distribution''' (mandatory)<br/>Determine the density and distribution of the instability within the defined location.<br/>See [[Spatial distribution definition table]] for more information on spatial distribution.

	* '''Sensitivity to Trigger''' (mandatory)<br/>Determine the Sensitivity to Triggers based on what kind of triggering will initiate avalanches of any size within the defined location.<br/>See [[Sensitivity to triggers definition table]] for more information on sensitivity to triggers.		* '''Sensitivity to Trigger''' (mandatory)<br/>Determine the Sensitivity to Triggers based on what kind of triggering will initiate avalanches of any size within the defined location.<br/>See [[Sensitivity to triggers definition table]] for more information on sensitivity to triggers.