Skip to content

May or may not be of concern: some functions will only work if input data is ordered in a particular way #7

@CesileyKing

Description

@CesileyKing
  1. ‘generate_focal_plane_distribution’ (MMTModules.py, lines 1081-1104) assumes that detector data is ordered in the following frequency/polarization angle combinations: freq1/polX, freq1/polY, freq2/polX, freq2/polY. When I was playing with MMT, I modified this to only increment index i by 1 and read in each detector’s info one at a time, instead of 4 at a time.

  2. ‘calculate_beam_matrix’ (MMTModules.py, lines 700-710) assumes that detectors located at an even index in the dictionary have polarization angles of 0 or pi/4, and detectors located at an odd index in the dictionary are pi/2 or -pi/4. When I was playing with MMT, I modified this to check the detector IDs to determine polarization angle (but this was particular to how I was labeling detectors, so one would probably want however S4 plans to standardly label detectors).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions