pnorbert

Exactly. This approach, however, put the task on the user to make sure the correct type is chosen. In adios 2.x, the C++ API lets the user to use the...

in adios 1.x, adios_byte simply means 8 bit. The user needs to make the mapping between memory type to the adios type. You would need to store a 16 bit...

Well, just that, unsigned char. On Thu, Sep 13, 2018, 3:35 PM Axel Huebl wrote: > @pnorbert alright, thanks. > > Another question: what's the recommended type in adios 1...

Did you configure with mpicc or gcc?

My setup on Rhea is: ``` export BUILD_WRITE=ON export BUILD_FORTRAN=ON export adios_timers=ON export INSTALL_PREFIX="$PWD/install" export CC=mpicc export CXX=mpiCC export FC=mpif90 export EXTRA_CFLAGS="" export CFLAGS="-g -fPIC ${EXTRA_CFLAGS}" ``` ``` /ccs/proj/e2e/pnorbert/ADIOS/ADIOS/build.rhea.gcc $...

Do you have HAVE_MPI on? $ grep HAVE_MPI config.h #define HAVE_MPI 1 Actually, I see the reason for the error when compiling with gcc (not mpicc) and so should always...

I did not mean you to define it. This should have been automatic, when using the mpi compiler.

Sorry I dropped the ball on this. Can you give me an example code? I can't recreate this valgrind error with a simple C example writing variables and attributes. On...

That's not it. My example works fine with 80MB variable. I can see the valgrind error in the SerialIOTests. How can I figure which actual test is causing this error?...

Never mind, I found them. The error is related to long double attributes, not to buffer size. On Wed, Aug 8, 2018 at 5:41 PM, Norbert Podhorszki < [email protected]> wrote:...