This files explain what is present in the files : 

- elevator_vulnerability.csv
- elevator_complementary.csv

################################################################################
## elevator_vulnerability.csv			     				                  ##
################################################################################

This file contains elementary components coming from the "note ascenseur". 
Contrary to the input data in the note, values in this database are already 
converted to Euros of 2019, following the method described in the "note 
ascenseur". The file contains the following variables:

- component_elementary: corresponds partially to the variable 'hmin' of the 
    database in the 'note ascenseur'. The categories in this variable are used 
    to aggregate values in 'v_min' and 'v_max' with the function 
    'prepare_elevator_data()'. These categories are added to the list of 
    elementary components in floodam.building.
- component: corresponds to the variable 'component' of the database in the 
    'note ascenseur'. Not used for anything. Kept to be able to trace elements 
    in the 'note ascenseur' if needed
- subcomponent: corresponds to the variable 'subcomponent' of the database in 
    the 'note ascenseur'. Not used for anything. Kept to be able to trace 
    elements in the 'note ascenseur' if needed
- hydraulic: corresponds to the variable 'hydraulic' of the database in the 
    'note ascenseur'. Identifies the components and subcomponents belonging to 
    hydraulic elevators. Used to calculate the values of elementary components 
    of hydraulic elevators
- traction: corresponds to the variable 'traction' of the database in the 
    'note ascenseur'. Identifies the components and subcomponents belonging to 
    traction elevators. Used to calculate the values of elementary components 
    of traction elevators
- action: corresponds to the variable 'action' of the database in the 
    'note ascenseur'.
- v_min: corresponds to the value in Euros of 2019 of the values in the variable
     'cost.min' of the database in the 'note ascenseur', converted according to 
     the methodology proposed in the 'note ascenseur'.
- v_max: corresponds to the value in Euros of 2019 of the values in the variable
     'cost.max' of the database in the 'note ascenseur', converted according to 
     the methodology proposed in the 'note ascenseur'.
- v_unit: indicates the units of 'v_min' and 'v_max'
- v_support: indicates the magnitude of reference for 'v_min' and 'v_max'
- component_elementary_label_fr: french translation of categories in the 
    'component_elementary' variable
- comment: Includes the comments in the variable 'comment' of the database in 
    the 'note ascenseur', as well as other relevant information.

################################################################################
## elevator_complementary.csv                                       ##
################################################################################

This file contains hypotheses for all the rest of variables necessary for the 
'component_elementary', 'component_elementary_action' and 
'category_vulnerability' databases for which we do no have information.
This database is presented in a much aggregated form since it is meant to be 
merged with the aggregated form of the 'elevator_vulnerability' database that is
calculated in the function 'prepare_elevator_data()'. The file contains the 
following variables:

- component_elementary
- component_elementary_label_fr
- category_activity_01
- category_activity_02
- category_dwelling_01
- category_dwelling_02
- version
- expert
- h_min
- h_max
- d_min
- d_max
- humidity
- p_action
- dilapidation
- h_action
- i_action
- t_min
- t_max
- value
- action: The value for the action is the concatenation of actions in 
    elevator_vulnerability.csv for each category in elementary component.
- category_vulnerability
- category_label_fr
- comment

################################################################################
## warning in update                                                          ##
################################################################################

- Update of prices should not be a problem
- If further information can be gathered on elementary components and actions 
 and probabilities can be set for each of them. It is recommended to do not 
 update these databases, but to include the components, actions and 
 vulnerability functions manually in the corresponding databases. The components
 included this way should be removed from these databases.  