In practice, nisarqa treats the CoordinateGrid dataclasses as frozen dataclasses. To ensure the robustness of the code, consider formally setting them to (frozen=True).
Can this be made frozen? Then there's no way that attributes can get out of sync (e.g., coordinate vectors vs the start/stop edges). This could be done in a separate PR.
Originally posted by @bhawkins in #161 (comment)
In practice,
nisarqatreats the CoordinateGrid dataclasses as frozen dataclasses. To ensure the robustness of the code, consider formally setting them to(frozen=True).Can this be made frozen? Then there's no way that attributes can get out of sync (e.g., coordinate vectors vs the start/stop edges). This could be done in a separate PR.
Originally posted by @bhawkins in #161 (comment)