Thanks to visit codestin.com
Credit goes to github.com

Skip to content

weird behavior when running grizli on GR150R #259

@pierluigi-rinaldi

Description

@pierluigi-rinaldi

Hello,

I am testing grizli on a very small dataset and noticed a weird behavior. As a test, I am using NGDEEP data.
In this particular case, F150W is the filter I am considering.

When considering grism C data, everything works fine on my laptop. I can model everything without any problem.
However, when considering grism R data, my notebook (but also via command line) gives me back segmentation fault. Even when I set cpu_count = 2 (so I limit its access to the memory, in principle). Everything seems working out fine when using it on my cluster (with more RAM ad CPUs).

The error I get from my notebook is the one below:

The Kernel crashed while executing code in the current cell or a previous cell.
Please review the code in the cell(s) to identify a possible cause of the failure.
Click here for more info.
View Jupyter log for further details.

Does anyone know why it happens?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions