Data Challenges

The Main Objective of the Data Challenges:

Prepare the full simulation and data analysis chain for UHECR/UHEnu within GRAND.

Specific Objectives of the data challenge:

• Tune & validate the ROOT data format, simulation to ROOT conversion
• Add ROOT input/output to the electronic chain
• Identify what is missing in GRANDlib
• Document the simulation and data analysis chain and the interfaces

As the code you will produce during the data challenge may be included in the grandlib, it is highly recommanded that the general and grand specific code writing standard of grandlib are followed.

Rules of the game:

• You may pick any Data Challenge you like (all of them is posible)
• You may work alone or in teams
• Each team produces in principle an independent code, but communication among teams and code sharing is encouraged
• Progress will be discussed during soft meetings and through direct exchanges (for example, on GitHub)
• Tentative deadline for DC1 is early September, and the next GRAND meeting for DC2 (Nijmegen, late October / early November or early January).
• After the DCs are completed, the various codes will be evaluated and we will work towards the unification of the production of a standard / official GRANDlib code
• Parameters for code evaluation will be:
  • Validity of the results produced
    • Eg. for DC1: can the initial Efield be indeed retrieved by antenna response deconvolution?
    • Eg. for DC2: how well the true parameters of the showers are reproduced?
  • Codes speed and memory usage
  • Modularity, easiness of use and possibility for evolution
  • Compliance with GRANDlib coding standards

Data Challenge 1

Produce ADC traces from ROOT files with Efield.

Inputs:

• an antenna response file
• an electronics response module
• Efield traces at the antenna feed point in the ROOT format

Output: Two ROOT files, created using GRANDlib ROOT interfaces, containing clean and noisy ADC traces

Prerequisites:

• Use the following antenna response files (description of use needed): EW SN Z
• Use the following electronics response and noise model; script for direct ZHAireS output (needs to be made to read ROOT files)
• All parts (antenna response, noise model, etc.) need to be plugable (inputs to the routine, or a config file?)
• Use the GRANDlib ROOT TTrees interface (documented here, l: grand, p: uhenuuhecr)

Pre-Data Challenge:

Validate full production of simulated traces in the ROOT format.

• Use the ZHAireSInputGenerator.py to generate input
• Use ZHAireS to generate traces from the input
• Use ZHAireSRawToGRANDROOT.py to convert traces to the ROOT format (the one in dev_io_root branch is not yet updated)
• Same should be repeated for CoREAS when the CoREAS to ROOT script is ready

Deadline

Some time in early September 2022 (to be refined later depending on progress).

Discussion

• For specific bugs/issues, please use this repository's Issues function.
• For more general discussion, please use Github Discussions
• For ROOT format and GRANDlib interfaces to it ask Lech Piotrowski
• For ZHAireS ask Matias Tueros

A remark: Not all tools and interfaces are ready and Data Challenges are a way to prompt their creation, validation and testing. Thus a close cooperation between the participants and the author of parts of the functionality (for example, Lech for ROOT interfaces) is a must.

Data Challenge 2, focused on EAS reconstruction will follow after the Data Challenge 1 is concluded.