Description | Background | Epidemic Intelligence at ECDC | Monitoring social media trends | Objectives of episomer | Repository of episomer material and training | Hardware requirements | Installation | Installation steps | Prerequisites | Mandatory for running episomer | Mandatory for some of the functionalities in episomer | Only for R developers | External dependencies | Installing episomer from CRAN | Environment variables | Launching the episomer Shiny app | Setting up data collection and alert detection loop | How does it work? General architecture behind episomer | Collection of posts | Use of the Bluesky search API version | Bluesky authentication | Topics and post collection queries | Scheduled plans to collect posts | progress Double Progress of the current plan as a percentage. It is calculated as (current$plan_max_date - current$current_min_date)/(current$plan_max_date - current$plan_min_date). If the underlying API returns no posts the progress is set to 100%. This only applies for non error responses containing an empty list of posts. | Geolocating locations referenced in message content | Improving and evaluating geolocation performance | Stored geolocated post information | Most frequent elements found in and extracted from posts | Aggregation of data | Signal detection | Details of the algorithm underlying signal detection | Downweighting previous signals | Timing of signal detection | The alpha parameter: the false positive rate of the signal detection | Bonferroni correction | Using same weekdays as baseline | Sending email alerts | Folder structure | Fs folder > posts | Fs folder > country_counts, geolocated, tags, topwords, urls | The interactive user application (Shiny app) | Dashboard: The interactive user interface for visualisation | Filters | The timeline | Map | Most frequent words, tags and URLs found in or extracted from posts | The alerts page | Find alerts | Alerts annotations | The geotag page | The data protection page | The configuration page | The troubleshoot page | Create a snapshot file | Diagnostic | Downloading outputs from the interactive user interface (Shiny app) | Annex I: Downweighting the previous signals | Introduction | EARS as a Linear Model | Downweighting | Example of the downweighting approach using Ebola data | Annex II: Troubleshooting and tips | Management of episomer pipelines ('episomer database', 'Data collection & processing', 'Requirements & alerts') in Windows | Management of episomer pipelines ('episomer database', 'Data collection & processing', 'Requirements & alerts') in Linux and Mac | Running 'episomer database', 'Data collection and processing' and 'Requirements and alerts' pipelines | "Cannot execute task #####: the task is already running" | "Failed while processing alerts" | Change the user of the Bluesky authentication | Downloading GeoNames and/or languages | Languages to be added or deleted | "The specified size exceeds the maximum representable size. Error: Could not create the Java Virtual Machine" | The "Launch slots" in the configuration page show NAs instead of the time slots | Downloading PDF of the dashboard | "Error in: LaTeX failed to compile C:\Users\name~1\...\file######.tex." | "Error: pandoc document conversion failed with error 6" | Different totals in dashboard outputs | Receiving only real-time alerts | Not receiving email alerts | References

Introduction | Common post format | Pre-requisites | Creates API and plan files | Edit config.R | Adapt the shiny app