Server Side or Code Issue?

[tjelse]

Good afternoon,

I am just wondering if this is a server side issue, or if this originates from an issue with the FDS code. I have not encountered an issue like this before.

Thanks!

[marcosvanella]

If you run the case again can you reproduce the segfault? I've seen a similar error related to openmpi and ucx (a network lib) in an ARM computer (NVIDIA Grace-Grace nodes).

[tjelse]

I will run again and report back. Thanks for the help with this.

[mcgratta]

Run the case again. If it fails at the same place, submit the input file and we'll run it on our cluster. If it does not fail. it might have been something on your end.

[tjelse]

Okay great, will do. It takes a couple days, I will report back. Thanks for the help with this,

[tjelse]

Hi, it does fail at the same point. I've uploaded the input file, thank you for the help with this.
HRR_HGV_TEST.zip

[mcgratta]

I will run the case.

[mcgratta]

One thing to consider:

WARNING: Number of pressure ZONEs 268 is large. Consider reducing the number.

This is a recent addition to FDS. Your model has 268 cavities or void spaces. That is, regions that are completely sealed off from the rest of the domain. If these regions are small and/or have combustible linings, it can cause trouble. The case is running for me, and I'll see how far it gests, but I urge you to reconsider the geometry.

[mcgratta]

WARNING: Droplet heat transfer is not predicted when a droplet is on a SURF with a specified ADIABATIC, NET_HEAT_FLUX, or CONVECTIVE_HEAT_FLUX.

Something else to avoid -- do not use an ADIABATIC boundary. We use this for diagnostic purposes, but it can lead to problems. There is no such thing as an adiabatic boundary. It is an ideal, not reality.

[mcgratta]

The case is still running at 172 s.

[tjelse]

Hi Kevin, great thank you. I appreciate the insight, I'm going to work on fixing these issues for this case and future models. As shown in the screen shot my run reached the segfault error at around 230s.

[mcgratta]

The case has run 309 s and is still going. But it is very slow. I suggest that you clean up the geometry and try again with the latest nightly build. If you consistently see problems, open an issue rather than Discussion thread.

[tjelse]

Great, thank you for your help with this. I assume too it was an issue with our server, I will open an issue if I cannot resolve getting this problem. Thanks!