ancestry.py needs update

[cracraft]

There are a few corrections needed to the mapping of MIRI data models to JWST data models.
The MiriFringeFlatfieldModel should map to FringeModel, not FlatModel.
MiriMrsApertureCorrectionModel should map to MirMrsApcorrModel.
MiriImagingPhotometricModel should be MirImgPhotomModel, not MiriImgPhotomModel (extra i).
MiriMrsFluxconversionModel should be MirMrsPhotomModel, not MiriMrsPhotomModel (extra i).

[smbeard]

Misty, I have modified ancestry.py and committed the update to the MiriTE repository. Steven From: Misty Cracraft ***@***.***> Sent: 01 September 2021 21:52 To: JWST-MIRI/MiriTE ***@***.***> Cc: Subscribed ***@***.***> Subject: [JWST-MIRI/MiriTE] ancestry.py needs update (#34) There are a few corrections needed to the mapping of MIRI data models to JWST data models. The MiriFringeFlatfieldModel should map to FringeModel, not FlatModel. MiriMrsApertureCorrectionModel should map to MirMrsApcorrModel. MiriImagingPhotometricModel should be MirImgPhotomModel, not MiriImgPhotomModel (extra i). MiriMrsFluxconversionModel should be MirMrsPhotomModel, not MiriMrsPhotomModel (extra i). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#34>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEUGVL7WECAJVMNFEHGWTKDT72G7RANCNFSM5DHL544A>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.