> For the complete documentation index, see [llms.txt](https://jonas.gitbook.io/seismo_rain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jonas.gitbook.io/seismo_rain/rainfall-data/picking-the-right-rainfall-event-for-our-analysis.md).

# Picking the right rainfall event for our analysis

## Climate around the seismic network

The peak rainfall in Enid, the nearest major city located 50 km away from the 2A seismic network (detailed in "[Picking the right seismic stations](/seismo_rain/seismic-data/picking-the-right-seismic-stations.md)"), occurs during the boreal spring season (April-June). This presents a favourable opportunity for us to utilize the rainfall data in our analysis.

<figure><img src="/files/9bXfaTTBJsOp44WIvwR0" alt="" width="447"><figcaption><p>The Climate of Enid, Oklahoma, USA (<a href="https://en.climate-data.org/north-america/united-states-of-america/oklahoma/enid-17116/">Climate Data, n.d</a>.)</p></figcaption></figure>

## Finding possible dates for analysis

We examined the daily rainfall data throughout the operational period of the 2A seismic network, spanning from April 11, 2016, to May 13, 2016. In line with the findings of [Bakker et al., 2022](https://doi.org/10.1016/j.jhydrol.2022.127812), which established the lowest detection limit of the geophone for rainfall intensity at 17 mm/day (equivalent to 0.7 inches/day), we aim to identify the date right above this threshold to ensure the validity of our results.

Hence, these are the three days that we are interested in: 11 April, 17 April, and 20 April 2016, which we could further investigate by looking at the archived radar data from [NOAA](https://www.ncei.noaa.gov/maps/radar/).

<figure><img src="/files/8zH7UKnupgASqAiFsifz" alt="" width="563"><figcaption><p>Daily Precipitaion during 1 Apr 2016 - 31 May 2016 at Enid, OK, USA (<a href="https://www.ncei.noaa.gov/access/past-weather/enid">NCEI, n.d.</a>)</p></figcaption></figure>

## Browsing the rainfall event with archived radar data

Once you are on the webpage of the NCEI NOAA Radar Data, select the dates of interest mentioned above and play around with the time by updating the map to pick a suitable rainfall event.

<figure><img src="/files/02as3QroqPX89DslU2zJ" alt="" width="375"><figcaption><p>Selecting the dates of interest to identify the relevant rainfall event (<a href="https://www.ncei.noaa.gov/maps/radar/">NECI, n.d</a>.)</p></figcaption></figure>

In this study, I selected a rainfall event occurring from April 19, 2016, at 22:00 UTC to April 20, 2016, at 02:00 UTC, characterized by an apparent West to East trailing rainband and resulting in widespread rainfall at the site of the seismic network.

<figure><img src="/files/vhH904QtnByVJ6vzHf54" alt=""><figcaption><p>Screenshots of radar maps around the seismic network (outlined in red) at 30-minute intervals from April 19, 2016, 21:30 UTC to April 20, 2016, 02:00 UTC (<a href="https://www.ncei.noaa.gov/maps/radar/">NECI, n.d</a>.)</p></figcaption></figure>

You could also pick a different rainfall event, and change the date when extracting the seismic data when amending the [Python code](/seismo_rain/seismic-data/extracting-seismic-data.md#extract-the-waveforms-from-all-four-seismic-stations).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jonas.gitbook.io/seismo_rain/rainfall-data/picking-the-right-rainfall-event-for-our-analysis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.