Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the detector polarization type to infer psi_pol in Pxx #808

Open
wants to merge 2 commits into
base: toast3
Choose a base branch
from

Conversation

keskitalo
Copy link
Member

Two quick fixes to support ground-based conviqt simulations.

@keskitalo keskitalo requested a review from tskisner February 20, 2025 01:07
Copy link
Member

@tskisner tskisner left a comment

Choose a reason for hiding this comment

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

Fine for now, although it could be fragile...

pol = props["pol"]
else:
pol = None
if pol == "A" or det.endswith(("a", "A", "t", "T")):
Copy link
Member

Choose a reason for hiding this comment

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

So this means that if the detector table happens to have a column named pol (with any value) and the detector name ends in A, it will trigger this branch. Is that fragile?

For simulated data from SO, this probably is fine since the det names end in "A" or "B" and there is a "pol" column with a matching value of "A" or "B".

For real SO data, the detectors have names like "Mv5_f150_Br06c04A", but we index the detectors by readout name (which doesn't end in "A", "B", "T", etc). So this is probably safe for that case.

In the future, if we find that we are running this operator frequently, we could create a trait that specifies the detector table column to use for psi_pol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants