Migrating from CPPC 0.7.2 to CPPC 0.8.0
- Changes to the execution system:
- HDF5 v1.8 or newer is required. CPPC will not compile if using v1.6 or older.
- The configuration mechanism for HDF5 has changed. Now 'configure' expects to receive the path to the 'h5cc' executable. Check the
documentation page for details.
- The configuration mechanism for MPI has changed. Now 'configure' expects to receive the path to the 'mpicc' executable. Check the
documentation page for details.
- OpenSSL is now required in order to compile CPPC.
- Changes to configuration files:
- Plain configuration files are now the default. This means that, if not otherwise specified, the compiled library will expect the
'.cppc_config' file to be a plain text file following the format shown in 'Example/cppc_config.example' (and in 'Example/cppc_config.plain'
in previous CPPC versions). If you are currently using XML files and would prefer to continue doing so, please use the --with-xerces family
of options. Check the documentation page for details.
- There is a new configuration parameter which controls when to create full checkpoints (versus incremental checkpoints). Before trying to
run a CPPC execution it is necessary to add the CPPC/Controller/FullFrequency to the configuration file. Check the
documentation page for details. Note that this parameter complements CPPC/Controller/Frequency, and both are necessary for execution.
- The configuration parameter which controlled the number of stored checkpoints (CPPC/Controller/StoredCheckpoints) has been replaced by a new
one which controls the number of simultaneously stored recovery sets. Check the documentation page for details.
The new CPPC/Controller/StoredRecoverySets is required for execution. The old CPPC/Controller/StoredCheckpoints is no longer used and can be
safely removed from the configuration file.
- Multithreaded is now always enabled. The CPPC/Checkpointer/Multithreaded option in '.cppc_config' is no longer used and can be safely removed.
- The configuration parameter which controlled the compressor to use, CPPC/Compressor/Type, was not used since CPPC 0.5. It can now be safely removed
from the configuration file.
