Elegant users forum

The noac option is specific to nfs, not xfs. I just took the original files you posted and ran it on an office computer on an xfs mounted drive. The results were not corrupted for me. My launch command was: /usr/lib64/mpich-3.2/bin/mpirun -np 12 Pelegant test_gen.ele The xfs drive is mounted with th...

Uninstall the RPMs you previously installed and then install these:

SDDSToolKit-5.0-1.rhel.7.nolock.x86_64.rpm
elegant-2020.4.0-5.rhel.7.openmpi.nolock.x86_64.rpm

I am going to guess that your lustre system is not using the flock mount option:
I will create an RPM for you with file locking turned off.

Is there run.acc file in that directory? Initially there isn't. So if there is, perhaps it was left behind by a previous test and left locked for some reason. What happens if you delete run.acc and try again?

What type of file system are you writing to? ext3, ext4, NFS, lustre, gpfs or something else?

Does your office workstation have a local disk drive that you can write to? If you run "df" you will see all the mounted drives. Look for entries that start with /dev. On my computer I can write to the local disk drive in the /local directory. Filesystem 1K-blocks Used Available Use% Mounted on /dev...

On RHEL.7 the mpich package from Redhat is version 3.0. That is the one in /usr/lib64/mpich. If you are using MPICH2 then you will want to use the Build-AOP-RPMs script to build Pelegant using the MPICH2 libraries. As for NFS, it depends on how you are running this. If this is a cluster, then the cl...

If you run it the same way but with fewer particles, is the output file ok? if not, then I would suspect an issue with the filesystem. MPI programs writing to an NFS filesystem can cause problems with corrupted files if the NFS file system is not mounted with the "noac" mount option. If the smaller ...

I found a problem passing memory to the GPU in a procedure that the KQUAD was using. There is another new version released for RHEL.7

I ran your files with Pelegant and got the 5.2 GB output file. However I am able to run sddscheck, sddsquery and sddsplot without seeing an error message. Can you tell me what you see when you run: uname -a and rpm -qa | fgrep SDDSToolKit I want to verify that you are running on a 64bit version of l...