storing geometry / eff. information into separate file

Open
  • Is something wrong?
#153 8 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@KrisThielemans is already working on this.

Since Sep 13, 2026.

Assessment

This issue has not been assessed yet.

Description

Since most modern scanners are "stable" and detector effs. are usually only "re-estimated" every few weeks / months,
storing those in a separate file would decrease storage requirements, especially if not all symmetries are being used
to encode the ModulePairEfficiencies.

Dominant language
Python
Stars
15
Forks
18
Avg merge
1d 11h
Merged PRs (30d)
12

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ETSInitiative/PETSIRD

All issues in ETSInitiative/PETSIRD

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.