jwst package version for MIRISim data about eureka HOT 8 CLOSED

I suggest emailing Pierre-Olivier Lagage to find out what versions of MIRISim and jwst they plan on using.

from eureka.

Sure, I think now is probably a good time to migrate to jwst v1.3.3. I can make new MIRI simulations with the newer MIRISIM pipeline for in-house testing as well to make sure we're prepared for MIRI data

from eureka.

Hey @taylorbell57, that's great news! I'd hold off on NIRSpec briefly as I just got the new injected dataset from David so I think it would be worthwhile to test things with that on my end for a bit. NIRSpec did reduce with the 1.3.3 version I used to develop Stage 1, so I'm not expecting too many differences.

from eureka.

I've just spotted that the latest jwst version is 1.4.0, as of a few days ago. But it seems that MIRISim is still at 2.4.1, so I'm not sure about compatibility.

With the data challenge in March (as you mention), I'm wondering if we are in a position right now to decide what version of jwst we want to make the code (particularly Stage 1) compatible with?

from eureka.

Okay, I'll do that now.

from eureka.

Okay, so the situation is that most of the people involved with MIRISim are also on the commissioning team and whilst they are aware of the new jwst package, they don't have any specific plans / roadmap to update anything as of yet. It is currently compatible with version 1.3.3.

Given that we are getting new MIRI simulated data, should we make sure everything runs on 1.3.3?

from eureka.

FYI, the current version of MIRISIM uses jwst v1.3.2 - not sure how that differs from v1.3.3 and whether it would be compatible with that minor version change

from eureka.

Alright, I just checked the old MIRISIM simulations and some new ones I made myself (using the same MIRISIM version as the ERS challenge will use) with jwst v1.3.3 and photutils>=1.1.0,<1.2 and had no issues running S2->S5. I can check NIRCam and NIRSpec now if @AarynnCarter or others have not already done so

from eureka.