Page History

...

• Retire aXe
• Retire aXeSIM
• Leverage the JWST infrastructure
  • just crds, gwcs and asdf?
• Enable common "Grismconf" infrastructure for:
  • pyLINEAR
  • grizli
  • EM2D, and Nor's other modules
  • JWST pipeline
  • (WFIRST)
• Ensure that users can do all the flavors of geometric transformations (and can understand them)
• Make sure calibration (files) are consistent with the approach to geometry
• Support the following HST modes:
  • WFC3/IR
  • ACS
  • WFC3/UVIS?
• Compatible with JWST pipeline outputs of WFSS modes (NIRISS and NIRCam)

Low-Hanging Fruit?

It would be good to start development work right away during the sprint, if at all possible. Even if we aren't completely certain of the end goals. This will start to get people familiar with the code bases and documentation, and make shake out some subtleties that are difficult to find without looking at the code. So what are some low-hanging fruit coding tasks?

• Refactor grizli | pyLINEAR | Nor's code to use JWST version of grismconf?
• Jupyter notebook illustrating how to do the equivalent aXedrizzle without using aXe?
  • Using reproject package (doesn't yet have drizzle algorithm though)
  • Using JWST pipeline version of drizzle

Use-Cases / Workflows

1D spectral extraction for perfectly registered & perfectly calibrated data

...