RAM pipeline stage 3

[EvgeniaKouts]

Hello everyone!

I would like to ask how much RAM memory should I have to run the whole MIRI pipeline.
I have a device with 32GB RAM and the pipeline fails at stage 3.
Is there any way to make it run with this memory available?

Thanks!

[braingram]

Hi!

Would you share which pipeline you're running? Are you using strun or calling it from python? Is it possible to share the command/code?

Finally what version of jwst are you using?

[EvgeniaKouts]

Hi! I am using the MIRI-MRS pipeline and I am calling it from this jupyter notebook https://github.com/spacetelescope/jwst-pipeline-notebooks/blob/main/notebooks/MIRI/JWPipeNB-MIRI-MRS.ipynb. Up until stage 2 it works fine. Then in stage 3 it produces the _crf.fits files and then I get a dead kernel. I tried also to run it as a .py file and again it took up all of my RAM after the _crf.fits files and it was killed. I am using JWST Calibration Pipeline Version = 1.16.0 and CRDS Context = jwst_1295.pmap. Thank you! On Monday, November 4, 2024 at 10:36:44 PM GMT+2, Brett Graham ***@***.***> wrote: Hi! Would you share which pipeline you're running? Are you using strun or calling it from python? Is it possible to share the command/code? Finally what version of jwst are you using? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[braingram]

Thanks!

Are you running the example data for that notebook or a different dataset/association? If a different one is it public and would you share the details to be able to find it on mast?

[EvgeniaKouts]

I am running the demo data. Thanks! On Monday, November 4, 2024 at 10:51:05 PM GMT+2, Brett Graham ***@***.***> wrote: Thanks! Are you running the example data for that notebook or a different dataset/association? If a different one is it public and would you share the details to be able to find it on mast? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>