Skip to content

[Enhancement]: Fix small discrepancy between pop_pxar_kw function and JWST pipeline #278

@kammerje

Description

@kammerje

Instrument or Category

Analysis Tools

What is your suggestion?

The pop_pxar_kw function in analysistools currently uses pysiaf to populate the pixel area FITS header keyword in case it is missing (which is the case if some of the JWST pipeline steps are skipped). However, the values from pysiaf are slightly discrepant from the values that the JWST pipeline populates itself for the pixel area FITS header keyword. Ideally, the pop_pxar_kw should be implemented so that it uses the same source for the pixel area as the JWST pipeline.

Error traceback output

No response

What operating system are you using?

No response

What version of Python are you running?

No response

What Python packages do you have installed?

No response

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions