🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

Hydrodynamic Lubrication Model

User: "Corlbert"
Altair Community Member

Hello,

I wanted to know why my simulation crashes when I add the above model. I use default parameters but when I submit the simulation its crashes. However, the simulations runs without the model.

Find more posts tagged with

Sort by:
1 - 4 of 41
    User: "jerrinjobs"
    Altair Employee

    Hi Corlbert

    Since this is not generally reproducible, I would advise you to recheck your installation, and see if it has completed well.

    Also, if you are not already using it, I would advise to update on the latest version also.

    Hope this helps.

    Thanks,
    Jerrin Job

    User: "Corlbert"
    Altair Community Member
    OP

    Hello Jerrin,

    Here is the error I got when I try submitting my simulation with the model

    Numeric mode unsupported in the posix collation implementation

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8431, resource id: 11035320, major code: 40 (TranslateCoords), minor code: 0

    /storage/group/ozo5101/default/sw/EDEM2024/altair/scripts/edem: line 21: 1924351 Segmentation fault (core dumped) "${SCRIPT_DIR}/edem-bin" $@

    And this is what my school IT has to say when I sent this error to them:

    That error can occur if the process attempts to use more memory than requested, but it is difficult to determine that for a running job. There are no obvious reasons why that should be occurring on our end.

    I would recommend reaching out to the software developer and seeing if they can provide insight into why this is happening.

    Best regards,

    Ayuk

    User: "Corlbert"
    Altair Community Member
    OP

    Hello Jerrin,

    I am using 2024 version which I think is new.

    User: "jerrinjobs"
    Altair Employee
    Updated by jerrinjobs

    Hi Corlbert

    I can confirm that this is a bug in the code with Linux. If you can try it in Windows, please go ahead, and you should not see this error.

    This is fixed in the 2025.1 release. Please look out for the release, and update the software on Linux when you are able, and you should not see this error after that.

    Hope this helps.

    Thanks,
    Jerrin Job