pnorbert

The Campaign Manager is on by default and records the ADIOS outputs (so far only the names) of an application. `adios-campaign/` is the directory that contains one or more sqlite3...

Fix will use .adios-campaign/ but it also deactivates recording by default and it can only be turned on in ~/.config/adios2/adios2.yaml.

Is there any update on this issue? In your build directory, what is the content of `thirdparty/EVPath/EVPath/config.h` This file contains `#define IPCONFIG_ENVVAR_PREFIX "ADIOS2_"`, and therefore it should be defined when...

I don't know how to solve this problem. I assume the one-build adios approach is not compatible with the two-build approach of hdf5, so you may need to keep two...

Hi Abishek, You need to tell adios what transport to use. It is not asking MPI what that is using. Unfortunately in the end of the log, it is not...

That doc was written before the UCX support was added. Since it found UCX, the RDMA transport is using that. For some reason the cmake config did not like the...

On Perlmutter I got: ``` -- Found LIBFABRIC: /opt/cray/libfabric/1.15.2.0/lib64/libfabric.so (Required is at least version "1.6") -- Checking for module 'cray-drc' -- No package 'cray-drc' found -- Could NOT find CrayDRC...

Indeed, I can't see it either. The libfabric option was taken out of the user options and now it does not appear in the list of features even when it...

@chuckatkins is using both (and travis) in the adios2 repository. So use whichever you think is better.

Our best examples are in a different repository right now that we use for tutorials. The heat2d code has both fortran and c++ versions. [https://github.com/pnorbert/adiosvm/tree/master/Tutorial/heat2d](https://github.com/pnorbert/adiosvm/tree/master/Tutorial/heat2d)