Skip to content

Incident angle model parameters - #2543

Open
EshitaJoshi wants to merge 16 commits into
mainfrom
add-new-model-params
Open

EshitaJoshi wants to merge 16 commits into
mainfrom
add-new-model-params

Conversation

@EshitaJoshi

@EshitaJoshi EshitaJoshi commented Sep 18, 2026 •

Copy link
Copy Markdown
Collaborator

Update and cleanup simtools-derive-incident-angles, and add derivation and export of lightguide_efficiency_vs_incidence_angle.

Closes #1976

@EshitaJoshi
EshitaJoshi requested a lite review from Copilot September 18, 2026 11:13

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The current export path can write empty model-parameter tables for non-finite data, and the documentation has an RST directive block that needs to be fenced properly to avoid Sphinx rendering/build issues.

Get a fresh assessment by requesting another Copilot review.

Review details
  • Files reviewed: 9/9 changed files
  • Comments generated: 3
  • Review effort level: Lite

Comment thread src/simtools/ray_tracing/incident_angles.py Outdated
Comment thread docs/source/user-guide/applications/simtools-derive-incident-angle.md Outdated
Comment thread src/simtools/ray_tracing/incident_angles.py Outdated
@EshitaJoshi
EshitaJoshi marked this pull request as ready for review September 18, 2026 11:39

@GernotMaier GernotMaier left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See below, probably me not understanding what is going on.

"calculate_primary_secondary_angles",
dest="calculate_primary_secondary_angles",
help="Compute angles of incidence on primary and secondary mirrors",
help="Compute angles of incidence on primary and secondary mirrors (enabled by default)",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this true by default, even for single-mirror telescopes? I am trying to understand what the impact is. Does it e.g., impact the reading of columns using _default_column_indices?

out=np.zeros_like(detected_counts, dtype=float),
where=bin_areas > 0,
)
max_efficiency = np.max(efficiency)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do struggle quite a bit with this part. Is this really light guide efficiency? Where does "photons transmitted for the light guide / photons incident on light-guide entrance" is applied? Is it possibly that this is only the angle distribution of photons incident on the light-guide entrance?

@ctao-sonarqube

Copy link
Copy Markdown

@EshitaJoshi

Copy link
Copy Markdown
Collaborator Author

@GernotMaier thanks for the review - can you take another look at this please?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Photon incident angles as input to camera efficiency.

3 participants