> For the complete documentation index, see [llms.txt](https://docs.humdata.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humdata.org/about/hdx-signals/datasets/armed-conflict.md). # Armed conflict Signals are sent when monthly conflict levels reach levels not seen in the past one to three years. ## Source We monitor [Armed Conflict Location & Event Data Project (ACLED)](https://acleddata.com) data. ACLED data contains dates, actors, locations, fatalities, and types of all reported political violence and protest events in more than [200 locations in real time](https://acleddata.com/download/4404/). You can access aggregated ACLED data directly on [HDX](https://data.humdata.org/organization/acled?) and get full, disaggregated data through the [ACLED data and tools](https://acleddata.com/data/). ## Signals detection We transform ACLED event datasets into a time series of armed conflict and fatalities, and calculate monthly fatalities as the rolling sum of fatalities across the past 30 days. Signals are generated whenever monthly fatalities reaches levels not seen in the past one or three years. Signals are not generated if monthly fatalities are below the minimum threshold of 100. ## Mapping ACLED occasionally reports conflicts at sea, which would require more detailed maps to visualize, including neighboring countries and bodies of water. To keep the visualizations clear and simple, points lying outside the base administrative boundary map are removed during the mapping process. #### Examples Below are historical examples that show how signals are generated with ACLED data. [Myanmar](https://us14.campaign-archive.com/?e=0c9936e61d\&u=ea3f905d50ea939780139789d\&id=3b6173e87a): in February 2021, monthly fatalities reached 169, higher than any time in the past year. [South Sudan](https://us14.campaign-archive.com/?e=0c9936e61d\&u=ea3f905d50ea939780139789d\&id=171a61325b): in June 2022, monthly fatalities reached 527, a level not seen since early 2019. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.humdata.org/about/hdx-signals/datasets/armed-conflict.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.