Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

where to check for config file of linux?

satri

Hello

I keep getting this message when i run simulation on HPC after 10 hours i dont know why.

one possible resolution i am thinking of trying is specifying the screen resolution when i connect through vcl to hpc.

Can you please tell me where can i find /.altair config file in the installation directory. i tried looking for it

here -

/DEM/altair/EDEM2025/altair/

but i could not find it

The error is given bellow.

WARNING : Argument Conflict : grid option is not applicable to GPU CUDAsolvers. Option will be ignored.qt.qpa.xcb: could not connect to display 10.1.16.111:11.0qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" eventhough it was found.This application failed to start because no Qt platform plugin could beinitialized. Reinstalling the application may fix this problem.Available platform plugins are: minimal, xcb.DEM/altair/EDEM2025/altair/EDEM/bin/edem:line 21: 527487 Aborted (core dumped)"${SCRIPT_DIR}/edem-bin" $@

Just to let you know simulation works fine. it used to run for more than 10hr. but sometimes it staops at 10hours and i get this message.

If i reinitiate it after an hour the simulation runs fine. so i am confused how to even resolve this. I can't have an unreliable case file running that stops suddenly like this.

Find more posts tagged with

EDEM

v2025.0

Accepted answers

All comments

Stephen Cole

hi,

Are you running with the gui/display visible? It maybe worth running command line especially on a remote machine:

https://help.altair.com/edem/topics/edem_simulator/using_the_edem_command_line_t.htm

The error suggests there is no display to connect to, if it was working for a time then stops there maybe some power saving or display time-out on the machine which is causing an issue?

Regards

Stephen

satri

I am using the MobA EX terminal on a Windows machine.

One thing I noticed is that once Moba Ex logs out by auto timeout or I close it and relog back in, this error came up. It does not matter if I use -X, or -Y while logging in or not, in both cases I would get this error. and also. This might be causing the issue -D 0+1+2+3 and tried to get 0+1+2+3 using the CUDA_VISIBLE_DEVICES worked on a Mac machine (even if you log out of the machine and log back in) but have not tried it yet on Mobaex yet because LSF might be assigning a different sequence of gpu maybe 3,2,1,0.