[User100000]

Hello!

I'm a new OpenFOAM and Ubuntu user and recently downloaded OpenFOAM v7 to use with the default ParaView version (5.6) and Ubuntu 18.04 LTS on Windows 10. I was working through the stress analysis tutorial and made it through generating the mesh. Unfortunately, when I tried to view the mesh using the paraFoam command, I received the following error message:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-chandraa18'

failed to get the current screen resources

I/O : uncollated

The mesh did not show up in ParaView although the overall shape itself did.

After searching around this forum, I came across an older post where a user had a similar issue but with OpenFoam v6 and the error message

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-neil'
failed to get the current screen resources
Xlib: *extension "MIT-SHM" missing on display "localhost:0.0".

I tried uninstalling v7 and installing v5, which uses ParaView 5.4 instead, but when I tried running paraFoam in v5, I got the error message

I/O : uncollated

Nothing showed up in ParaView for this version.

I would very much appreciate it if anyone knows how to resolve this issue and is willing to share a solution. Thank you!

[User100000]

Update: I tried a plethora of fixes (see below), and somewhere along the way, ParaView decided to start displaying the output of the solvers!

1) Overriding the uncollated file format

There is a very helpful section of the user manual (https://cfd.direct/openfoam/user-guide/v7-running-applications-parallel/#x12-870003.4.2) that describes how to add an "OptimisationSwitches" section to the controlDict file and set the fileHandler piece to either collated or uncollated. (I'm not sure why my system defaulted to an uncollated file format, but setting fileHandler fixed that issue.)

2) Saving the output files to VTK format using foamToVTK, downloading ParaView 5.4 on my Windows system, and opening the VTK files there

Since ParaView 5.4 refused to load on my Ubuntu system, I tried opening the output files in Windows. They did show up there, but I couldn't edit the "Properties" tab with the VTK file format, so I tried installing v7 again since that version of ParaView (5.6) loaded on Ubuntu.

3) Uninstalling v5 and reinstalling v7 with ParaView 5.6 installed on both the Ubuntu subsystem and Windows

After doing this, ParaView 5.6 on Ubuntu loaded results from the pitzDaily and cylinder tutorials with the "I/O: uncollated" message. The "QStandardPaths" error still showed up but didn't seem to affect anything.

I hope that this helps anyone who might have had similar issues!

[ali moeni]

Hi
I faced the same problem (I/O : uncollated)
I took Your advice and used the foamToVTK to save files as VTK format and right after that, again I used paraFoam to check out if its still there.
(I/O : uncollated) was still there but didn't affect anything and paraview worked perfectly and showed all the results.

[fluid-user]

Hi
I faced the same problem (I/O : uncollated)

Created temporary 'cavityGrade.OpenFOAM'
I/O : uncollated


It affect anything and paraview worked perfectly and showed all the results.But, the terminal couldn't use. I need open a new terminal.

[lxufeishi]

Originally Posted by fluid-user

Hi
I faced the same problem (I/O : uncollated)

Created temporary 'cavityGrade.OpenFOAM'
I/O : uncollated


It affect anything and paraview worked perfectly and showed all the results.But, the terminal couldn't use. I need open a new terminal.

I use OF9 with paraview5.6.0 in WLS2 of Win10 and "paraFoam" works perfectly as well. I think the problem has nothing to do with the message "I/O : uncollated". We can ignore it.
By the way, to get rid of opening a new terminal, just run the command in the backgound, like

paraFoam &

then you can type CTRL+C to skip into a new command line and the paraview window is remaining.

Cheers,

[fluid-user]

Originally Posted by lxufeishi

I use OF9 with paraview5.6.0 in WLS2 of Win10 and "paraFoam" works perfectly as well. I think the problem has nothing to do with the message "I/O : uncollated". We can ignore it.
By the way, to get rid of opening a new terminal, just run the command in the backgound, like

paraFoam &

then you can type CTRL+C to skip into a new command line and the paraview window is remaining.

Cheers,

Thank you very much. I solved the problem with your method.