This repository runs the Alerta Dengue analytics pipeline using R within a Conda environment, orchestrated by Makim tasks.
It is designed to run against a PostgreSQL database (local container or
remote), generate per-state .RData artifacts, and produce SQL update scripts
for downstream systems.
- Linux
- Conda distribution (recommended: Miniforge/Mambaforge)
mamba(recommended) orconda- PostgreSQL database available (e.g., Docker container)
Create the environment from the repository conda spec:
mamba env create -f conda/base.yaml -n alertadengueanalise -y
conda activate alertadengueanalisemakim deps.install --env alertadengueanaliseOptional smoke test:
makim deps.check --env alertadengueanaliseCreate a .env file at the repo root with your Postgres connection settings.
Supported variables:
DB_HOSTDB_PORTDB_NAMEDB_USERDB_PASSWORDDB_SSLMODE(optional)
Example:
ALERTA_DATA_RELATORIO=${ALERTA_DATA_RELATORIO}
ALERTA_OUT_DIR=${ALERTA_OUT_DIR}
ALERTA_DB_HOST=${ALERTA_DB_HOST}
ALERTA_DB_PORT=${ALERTA_DB_PORT}
ALERTA_DB_NAME=${ALERTA_DB_NAME}
ALERTA_DB_USER=${ALERTA_DB_USER}
ALERTA_DB_PASSWORD=${ALERTA_DB_PASSWORD}
ALERTA_DO_SCP=${ALERTA_DO_SCP}
ALERTA_SCP_ENDPOINT=${ALERTA_SCP_ENDPOINT}
ALERTA_SCP_PATH=${ALERTA_SCP_PATH}Check connectivity:
makim db.check --env alertadengueanaliseRun the pipeline for week YYYYWW (example: 202601):
makim pipeline.run-br --env alertadengueanalise --week 202601- Pipeline behavior and steps:
docs/WORKFLOW.md - Outputs and where to find them:
docs/OUTPUTS.md
-
If you see missing R packages during execution, run:
makim deps.install --env alertadengueanalise
-
If the pipeline runs long with little console output, check:
- CPU usage:
ps -o pid,etime,pcpu,pmem,cmd -p <PID> - New files created under
main/alertas/<YYYYWW>/ - Log file under
logs/(if enabled by your pipeline wrapper)
- CPU usage: