Lebanon is a middle-income Middle Eastern country that has been hosting around 1.5 million Syrian Refugees, a figure representing one of the largest concentrations of refugees per capita in the world. The enormous influx of displaced refugees remains a daunting challenge for the national health services in a country whose own population is at 4 million, a problem that is exacerbated by the lack of national funds to allow respective municipalities to sufficiently balance its own services between host and refugee communities alike, prompting among the Lebanese population a sense of being disadvantaged by the presence of refugees

Our manuscript henceforth addresses the following question: can we analyse the spatiotemporal surge in demand recorded by primary health care centers through data provided by the Lebanese Ministry of Health in light of the peaks in events emanating from the Syrian war, and further model it in order to yield reasonably accurate predictions that can assist policy makers in their readiness to act on surges in demand within prescribed proximity to the locations in Syria where the peaks have taken place?

To this end, we embark on a process that analyses data from the Lebanese ministry of public health, representing primary health care demand, and augment it with data from the Syrian Violations Data Center, a leading repository for documenting casualties in the Syrian war. The objective of this study is to analyse the surge in demand on primary health care centers using data from MoPH in reference to the peaks in the Syrian war derived from the VDC, to produce both pointwise as well as probabilistic forecasting of the demand using a suite of statistical and machine learning models, to improve the recall values of surges in demand using utility based regression for capturing rare events – in our context, instances when the demand surges due to large scale events in Syria – and to reveal the rules and interactions between major input features that led these models to their prediction, using machine learning interpretability techniques.

• Faour.xlsx: is the original dataset of patient visits to Lebanese Health Centers
• VDC Datasets: Contains the three different datasets taken from Syrian Violations Data Center, one for each year (2014, 2015, 2016). vdc_grouped.csv is these three grouped together into one data frame
• Weather.csv is the weather data from the International Weather Station at Beirut International Airport. The weather data is scraped in a daily manner, for the Beirut Governorate, for the years 2014, 2015, 2016 from https://www.wunderground.com/history/monthly/lb/beirut/

All of the text entries in this dataset were in Arabic and so were translated using dictionaries that we developed in our capacity as native speakers. Dictionaries for translations could be found in here: translations.py

• Pre-processing and Data Cleaning: data_set.py, data_subset.py
• Visualizations: data_visualize.py
• Weather data scraping: generate_weather_data.py
• VDC Data Handling: generate_vdc_data.py
  • Adaptive binning for generating civilians rank
  • distances from Lebanese health centers to places of death in Syria in times of large scale events
  • distribution of civilians rank by year
• VDC Plots: vdc_plots contains all plots related to VDC explorations
• Generating inital 12 data subsets: generate_Faour_data_subsets.py This script is responsible for subsetting the original input data Faour.xlsx into 12 data subsets, each representing one of the three governorates on interest (Akkar, Beqaa, Tripoli) and one of the services in the health centers (General Medicine, Gynecology, Pediatrics, and Pharmacy). the Focus was on Syrian Nationalities. The datasubsets could be found here: Faour datsubsets. The datasubsets follow the following naming structure: [service name]_[Syria]_[Governorate name]
• Generating the final 12 datasubsets: Here, we take the initial 12 datasubsets (the buller above) and we:
  • apply weekly down-sampling (in Faour.xlsx) demand was in a daily basis. For a more general view, we aggregated demand to make it weekly
  • we added vdc data next to each week
  • we added weather data next to each week
  • we added distance from the large scale events in Syria next to each week Script: generate_multivariate_datasubsets.py, which generates the data subsets and saves them here: multivariate data subsets

• Collated Datasets: generate_collated_separated_input_datasets.py: collates the 12 data subsets together whilst adding one hot encoding to the service name and Governorate. The resulting collated data sets are found in:
  • input/all_with_date: including the date column
  • input/all_without_date without including the date column
• Separated Datasets: contains the separated datasets which we have used for collation. These are found in the following directory: input/separated
• Disclaimer: in each of tehe directories above, we set 9 column variations, removing certain columns and seeing which variation achieves teh best results. Therefore, there exists the [minus_colmn name] in the directories above

• Time Series: Code/timeseries.py: Generates:
  • time series plots: ACF, PACF, auto-correlation, persistence model, line plot, histogram, density plot.
  • white noise detection: L-jung box test
  • stationarity checking: Augmented Dickey-Fuller Test
  • adds lags, trend, and seasonality to the time series. - Time series plots: temporal_structure_plots - EDA: eda.py: Genrates all plots related to exploratory data analysis. - EDA Plots: eda_plots

We have done a suite of Machine learning models with cross validation. We have used 10-folds-10-reperats for cross validation.

• Cross Validation: cross_validation.py: the code that handles cross validation with hyper parameter tuning (Grid Search), produces the learning curves, applies scaling to the data.
• Hyper parameters: model_hyperparams_grid.py contains dictionaries of hyper parameters to be search by Grid Search in cross_validation.py)
• container.py contains paths and scaling options to each dataset
• Python Run Files for Column Variations: shallow collated run files is a directory containing all run files for applying cross validation on the 9 column variation we have. The cross_validation.py code is generaic and can be applied to any dataset as indicated below.
• Disclaimer In order to use the run files, put them as main children of the Code directory

We have an imbbalanced regression, were rare events, which are mainly high demand values, are poorly present in the data and they do add confusion to the machine learning models and degrade performance. We have used Branco's approach in the paper SMOGN: a Pre-processing Approach for Imbalanced Regression and forked their repository. We have used their R codes and called some appropriate helper functions from our python code using python's rpy2 module

• DIBSRegress.R Code that contains SMOGN algorithm
• smogn.R contains helper functions in R
• cross_validation_smogn.py contains the code that applies "SMOGN" inside cross validation
• extract_rare.py helper code for getting indices of rare values in testing data, extracting relevance function, and plotting rare values before and after oversampling
• utility_based_error_metrics code that computes utility-based-error-metrics Like F₁, precision, and recall

We have done probabilistic forecasts in both Ubr and non-Ubr mode

• Ubr

  • code CodeUbr\cross_validation_smogn_prob.py code for runnig cross validation with SMOGN and probabilistic models
  • code CodeUbr\models_hyperparams_prob.py hyper parameters for probabilistic models
  • models CodeUbr\probabilistic_uncertainty contains the codes for the probabilistic models
  • run files CodeUbr\probabilistic_run_files run files for running probabilistic models on all experiments (9 column variations)

• Non Ubr

  • code Code\cross_validation_smogn_prob.py code for runnig cross validation with probabilistic models
  • code Code\models_hyperparams_prob.py hyper parameters for probabilistic models
  • models Code\probabilistic_uncertainty contains the codes for the probabilistic models
  • run files Code\probabilistic_run_files run files for running probabilistic models on all experiments (9 column variations)

The experimental design was implemented in both Python and R language. Both code and data are in a format suitable for Python and R environment.

In order to replicate the experiments in CodeUbr you will need a working installation of R. Check [https://www.r-project.org/] if you need to download and install it.

You must have R 3.6.x

In your R installation you also need to install the following additional R packages:

• DMwR
• performanceEstimation
• UBL
• uba: https://www.dcc.fc.up.pt/~rpribeiro/uba/
• operators
• class
• fields
• ROCR
• Hmisc
• R tools version 35. https://cran.r-project.org/bin/windows/Rtools/

All the above packages, with the exception of uba package, can be installed from CRAN Repository directly as any "normal" R package. Essentially you need to issue the following commands within R:

install.packages(c("DMwR", "performanceEstimation", "UBL", "operators", "class", "fields", "ROCR"))
install.packages("Hmisc")

Before you install the uba package, you need to have the latest version of R tools. Check https://cran.r-project.org/bin/windows/Rtools/

Additionally, you will need to install uba package from a tar.gz file that you can download from http://www.dcc.fc.up.pt/~rpribeiro/uba/.

For installing this package issue the following command within R:

install.packages("uba_0.7.7.tar.gz",repos=NULL,dependencies=T)

Other than R, in order to run the remaining experiments in CodeUbr as well as the experiments in Code you need the following python modules

• rpy2 version 2.9.5
• pandas version 0.24.0
• keras
• tensorflow
• sklearn
• xgboost
• scipy
• matplotlib
• numpy