Details
-
Type:
Story
-
Status: In Progress
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: sphgeom
-
Labels:
-
Story Points:10
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
Our sphgeom provides a nice generic interface for spherical pixelizations, with implementations for HTM, Q3C, and a custom modification of Q3C. By delegating the work to the public HEALPix C++ library, we could easily add HEALPix to the mix, and write downstream mask manipulation code without assuming a particular pixelization. It'd also give us an easy way to compare the performance of different pixelizations.
The HEALPix C++ library is packaged by conda-forge as healpix_cxx, and at least right now it installs without any trouble into our environment. When this ticket is nearing completion we can RFC getting that into our standard installs. We should then either make HEALPix an optional dependency of sphgeom or (probably better) put a new subclass of sphgeom::Pixelization in a new package that depends on both HEALPix and sphgeom; we want to make sure the current sphgeom functionality continues to be available without additional dependencies.
It looks like the tricky part of implementing that new Pixelization will be determining whether the pixel method can just return a sphgeom::ConvexPolygon with the four vertices of the pixel (i.e. under what conditions do the non-geodesic HEALPix boundaries extend beyond the geodesic boundaries of a ConvexPolygon with the same vertices instead lying completely within them?). I've only taken a quick glance, but it looks like the HEALPix library includes routines for directly implementing all of Pixelization's other virtual methods.
Attachments
Issue Links
- is blocked by
-
DM-33162 Fix conda feedstocks for healpix_cxx
- Done
Activity
Labels | geometry-refactor |
Risk Score | 0 |
Description |
Our {{sphgeom}} provides a nice generic interface for spherical pixelizations, with implementations for HTM, Q3C, and a custom modification of Q3C. By delegating the work to the public HEALPix C++ library, we could easily add HEALPix to the mix, and write downstream mask manipulation code without assuming a particular pixelization. It'd also give us an easy way to compare the performance of different pixelizations.
The stack already includes {{healpy}} as a dependency, which builds against the HEALPix C++ library internally. Since {{healpy}} can also build against an external HEALPix library, we should create a new third-party LSST package for that and have {{healpy}} depend on it. We should then either make HEALPix an optional dependency of sphgeom or (probably better) put a new subclass of {{sphgeom::Pixelization}} in a new package that depends on both HEALPix and sphgeom; we want to make sure the current sphgeom functionality continues to be available without additional dependencies. It looks like the tricky part of implementing that new {{Pixelization}} will be determining whether the {{pixel}} method can just return a {{sphgeom::ConvexPolygon}} with the four vertices of the pixel (i.e. under what conditions do the non-geodesic HEALPix boundaries extend beyond the geodesic boundaries of a {{ConvexPolygon}} with the same vertices instead lying completely within them). I've only taken a quick glance, but it looks like the {{HEALPix}} library includes routines for directly implementing all of {{Pixelization}}'s other virtual methods. |
Our {{sphgeom}} provides a nice generic interface for spherical pixelizations, with implementations for HTM, Q3C, and a custom modification of Q3C. By delegating the work to the public HEALPix C++ library, we could easily add HEALPix to the mix, and write downstream mask manipulation code without assuming a particular pixelization. It'd also give us an easy way to compare the performance of different pixelizations.
The HEALPix C++ library is packaged by conda-forge as {{healpix_cxx}}, and at least right now it installs without any trouble into our environment. When this ticket is nearing completion we can RFC getting that into our standard installs. We should then either make HEALPix an optional dependency of sphgeom or (probably better) put a new subclass of {{sphgeom::Pixelization}} in a new package that depends on both HEALPix and sphgeom; we want to make sure the current sphgeom functionality continues to be available without additional dependencies. It looks like the tricky part of implementing that new {{Pixelization}} will be determining whether the {{pixel}} method can just return a {{sphgeom::ConvexPolygon}} with the four vertices of the pixel (i.e. under what conditions do the non-geodesic HEALPix boundaries extend beyond the geodesic boundaries of a {{ConvexPolygon}} with the same vertices instead lying completely within them?). I've only taken a quick glance, but it looks like the {{HEALPix}} library includes routines for directly implementing all of {{Pixelization}}'s other virtual methods. |
Assignee | Jim Bosch [ jbosch ] |
Status | To Do [ 10001 ] | In Progress [ 3 ] |
Summary | Add sphgom.Pixelization for HEALPix | Add sphgeom.Pixelization for HEALPix |
Assignee | Jim Bosch [ jbosch ] | Matthias Wittgen [ wittgen ] |
Epic Link |
|
PREOPS-477 [ 476909 ] |
Epic Link | PREOPS-477 [ 476909 ] | PREOPS-650 [ 714056 ] |
Urgent? | off |
Epic Link | PREOPS-650 [ 714056 ] | PREOPS-995 [ 1078856 ] |
Assignee | Matthias Wittgen [ wittgen ] |
Epic Link | PREOPS-995 [ 1078856 ] | PREOPS-1161 [ 1475339 ] |
Epic Link | PREOPS-1161 [ 1475339 ] | PREOPS-1183 [ 1509238 ] |
Epic Link | PREOPS-1183 [ 1509238 ] | PREOPS-1494 [ 2225526 ] |
Epic Link | PREOPS-1494 [ 2225526 ] | PREOPS-1496 [ 2232716 ] |
Epic Link | PREOPS-1496 [ 2232716 ] | PREOPS-1497 [ 2232737 ] |
Epic Link | PREOPS-1497 [ 2232737 ] | PREOPS-1498 [ 2232747 ] |
Epic Link | PREOPS-1498 [ 2232747 ] | PREOPS-4524 [ 5413054 ] |