> For the complete documentation index, see [llms.txt](https://friederikebock.gitbook.io/epiclfhcaltb-ana/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://friederikebock.gitbook.io/epiclfhcaltb-ana/data-analysis/simple-event-display.md).

# Simple Event display

## How it works

The main program to run a basic event diplay is the `./Display`. It produces a 3D plot showing the energy depositions in the 2024 test beam geometry, with the sizes and colors corresponding to the bins' contents. It can be run be run either over a particular event in the given run, or a range. It can only be run on calibrated data, otherwise all bins will be filled with `0`.

Sometimes, if run over more than 100 events, the colors are not assigned - to be debugged, the problem doesn't appear when run over a signle event.

Following options are implemented:

* common with the rest of the macros:
  * \`-d\` : switch to debug info with debug level 0 to n
  * \`-F\` : set plot extention expliticly, default is pdf
  * \`-i\` : input file in root format,
  * \`-P\` : plots directory path,
  * \`-r\` : name of run list file,
  * \`-y\` : setting year externally,
* specific for the event display:
  * \`-e\` : setting event number to plot, default 0,
  * \`-N\` : setting number of events to plot, default 1,
  * \`-M\` : plot only muon triggered events (in the given range)

Example of how to run it:

```
./Display -d 1 -i $INPUT_FILE -r $RUN_LIST -P $PLOT_DIR -e 5 [-N 10 -M]
```

<figure><img src="/files/pgoxUld2st4uR69zShnC" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/dtrqUevGyRyUOvYd7rnm" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/fY50wSu7ofC2v2dREULG" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/4VVaLX6fwbXBZ3UzpMt0" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/qiMP6BQuObgks8ITVKn9" alt=""><figcaption></figcaption></figure>

Alternative views with projections in `X,Y` and `Z` are also provided:

<div><figure><img src="/files/PEyhRPwIIxCjPH0OOn5x" alt=""><figcaption></figcaption></figure> <figure><img src="/files/qd9wDdi5K4U9B1qtrxib" alt=""><figcaption></figcaption></figure> <figure><img src="/files/oV4H0Jy7CgZXBXRyWZDp" alt=""><figcaption></figcaption></figure></div>

## CAEN data

### August 2024 data

The primary script implemented for the event display is `runEventDisplay_2024.sh`:

```bash
bash runEventDisplay_2024.sh $USERNAME $BEAM_TYPE $EVENT_NUMBER $HOW_MANY_EVENTS [muonTrig]
```

where: `$BEAM_TYPE` can be `muon`, `electron`, `hadron.`

## HGCROC data

### November 2025 data

The primary script implemented for the event display to run it on the 2025 data is `runEventDisplay_TB2025.sh` .

```shellscript
bash runEventDisplay_TB2025.sh $USERNAME [tot,adc,full,ped] $NEVT
```

The 2nd option defines which of the information of the HGCROC data should be filled:

* `tot` shows only the ToT values
* `adc` shows the GetIntegratedADC() value after waveform building (i.e. max-ADC so far)
* `full` shows the energy in mip equivalent coming from the calibrated output
* `ped` shows the pedestal subtracted ADC

The last argument defines for how many events you'll be creating the event displays.


---

# 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:

```
GET https://friederikebock.gitbook.io/epiclfhcaltb-ana/data-analysis/simple-event-display.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.