Skip to content

Refactor the readout command-line switches? #119

@lucabaldini

Description

@lucabaldini

Since we are switching to a new model where all the calibrations are matrix based, we need to be more strict in terms of how we specify the readout. More specifically:

[lbaldini@pcpi0188 docs]$ hexsample simulate --help

    This is hexsample version 0.15.0+g82362e9.

    Copyright (C) 2023--2026, the hexsample team.

    hexsample comes with ABSOLUTELY NO WARRANTY.
    This is free software, and you are welcome to redistribute it under certain
    conditions. See the LICENSE file for details.

    Visit https://github.com/lucabaldini/hexsample for more information.

...

readout:
  Redout configuration

  --layout {ODD_R,EVEN_R,ODD_Q,EVEN_Q}
                        chip layout (default: HexagonalLayout.ODD_R)
  --num_cols NUM_COLS   number of colums in the readout chip (default: 304)
  --num_rows NUM_ROWS   number of rows in the readout chip (default: 352)
  --pitch PITCH         pitch of the readout chip in cm (default: 0.005)
  --enc ENC             equivalent noise charge in electrons (default: 30.0)
  --gain GAIN           conversion factor between electron equivalent and ADC
                        counts (default: 1.0)
  --map_gain_file MAP_GAIN_FILE
                        path to a file containing the gain map. If not
                        specified, the gain value of the --gain argument is
                        used for all the pixels. (default: None)
  --offset OFFSET       offset in ADC counts to be applied before the zero
                        suppression (default: 0)

...

That is: at this moment we are specifying the number of cols and rows, as well as the layout of the readouts separately. But from now on this has to match what we have in the calibration file.

I would like to propose that we identify the logical structure of the readout by a key (e.g., "xpol1" or "xpol3"). An alternative would be to take the information from the calibration files directly.

@starquino , @augustocattafesta what do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions