| 1 | /*
|
|---|
| 2 | * MPQCDataMap.hpp
|
|---|
| 3 | *
|
|---|
| 4 | * Created on: 28.07.2012
|
|---|
| 5 | * Author: heber
|
|---|
| 6 | */
|
|---|
| 7 |
|
|---|
| 8 | #ifndef MPQCDATAMAP_HPP_
|
|---|
| 9 | #define MPQCDATAMAP_HPP_
|
|---|
| 10 |
|
|---|
| 11 | // include config.h
|
|---|
| 12 | #ifdef HAVE_CONFIG_H
|
|---|
| 13 | #include <config.h>
|
|---|
| 14 | #endif
|
|---|
| 15 |
|
|---|
| 16 | #include <boost/fusion/container/map.hpp>
|
|---|
| 17 | #include <boost/mpl/list.hpp>
|
|---|
| 18 |
|
|---|
| 19 | #include "Jobs/MPQCDataFused.hpp"
|
|---|
| 20 |
|
|---|
| 21 | class Histogram;
|
|---|
| 22 | class IndexedVectors;
|
|---|
| 23 | class SamplingGrid;
|
|---|
| 24 |
|
|---|
| 25 | /// \note: We had to split up the map because boost::fusion only allows for
|
|---|
| 26 | /// up to 9 template types.
|
|---|
| 27 |
|
|---|
| 28 | /** This boost::fusion map defines key-value or rather key-type pairs with
|
|---|
| 29 | * which we associate all energy_t data members in MPQCData and their type.
|
|---|
| 30 | *
|
|---|
| 31 | * This lets us resolves any ambiguitites of types in MPQCData, e.g.
|
|---|
| 32 | * to know vector<double> is forces or energy_eigenvalues.
|
|---|
| 33 | *
|
|---|
| 34 | */
|
|---|
| 35 | typedef boost::fusion::map<
|
|---|
| 36 | boost::fusion::pair<MPQCDataFused::energy_total, double>
|
|---|
| 37 | , boost::fusion::pair<MPQCDataFused::energy_nuclear_repulsion, double>
|
|---|
| 38 | , boost::fusion::pair<MPQCDataFused::energy_electron_coulomb, double>
|
|---|
| 39 | , boost::fusion::pair<MPQCDataFused::energy_electron_exchange, double>
|
|---|
| 40 | , boost::fusion::pair<MPQCDataFused::energy_correlation, double>
|
|---|
| 41 | , boost::fusion::pair<MPQCDataFused::energy_overlap, double>
|
|---|
| 42 | , boost::fusion::pair<MPQCDataFused::energy_kinetic, double>
|
|---|
| 43 | , boost::fusion::pair<MPQCDataFused::energy_hcore, double>
|
|---|
| 44 | , boost::fusion::pair<MPQCDataFused::energy_eigenvalues, Histogram >
|
|---|
| 45 | > MPQCDataEnergyMap_t;
|
|---|
| 46 |
|
|---|
| 47 | typedef boost::mpl::list<
|
|---|
| 48 | MPQCDataFused::energy_total,
|
|---|
| 49 | MPQCDataFused::energy_nuclear_repulsion,
|
|---|
| 50 | MPQCDataFused::energy_electron_coulomb,
|
|---|
| 51 | MPQCDataFused::energy_electron_exchange,
|
|---|
| 52 | MPQCDataFused::energy_correlation,
|
|---|
| 53 | MPQCDataFused::energy_overlap,
|
|---|
| 54 | MPQCDataFused::energy_kinetic,
|
|---|
| 55 | MPQCDataFused::energy_hcore,
|
|---|
| 56 | MPQCDataFused::energy_eigenvalues
|
|---|
| 57 | > MPQCDataEnergyVector_t;
|
|---|
| 58 |
|
|---|
| 59 | /** This boost::fusion map defines key-value or rather key-type pairs with
|
|---|
| 60 | * which we associate all forces data members in MPQCData and their type.
|
|---|
| 61 | *
|
|---|
| 62 | * This lets us resolves any ambiguitites of types in MPQCData, e.g.
|
|---|
| 63 | * to know vector<double> is forces or energy_eigenvalues.
|
|---|
| 64 | *
|
|---|
| 65 | */
|
|---|
| 66 | typedef boost::fusion::map<
|
|---|
| 67 | boost::fusion::pair<MPQCDataFused::forces, IndexedVectors >
|
|---|
| 68 | > MPQCDataForceMap_t;
|
|---|
| 69 |
|
|---|
| 70 | typedef boost::mpl::list<
|
|---|
| 71 | MPQCDataFused::forces
|
|---|
| 72 | > MPQCDataForceVector_t;
|
|---|
| 73 |
|
|---|
| 74 | /** This boost::fusion map defines key-value or rather key-type pairs with
|
|---|
| 75 | * which we associate all sampled_grid data members in MPQCData and their type.
|
|---|
| 76 | *
|
|---|
| 77 | * This lets us resolves any ambiguitites of types in MPQCData, e.g.
|
|---|
| 78 | * to know vector<double> is forces or energy_eigenvalues.
|
|---|
| 79 | *
|
|---|
| 80 | */
|
|---|
| 81 | typedef boost::fusion::map<
|
|---|
| 82 | boost::fusion::pair<MPQCDataFused::sampled_grid, SamplingGrid >
|
|---|
| 83 | > MPQCDataGridMap_t;
|
|---|
| 84 |
|
|---|
| 85 | typedef boost::mpl::list<
|
|---|
| 86 | MPQCDataFused::sampled_grid
|
|---|
| 87 | > MPQCDataGridVector_t;
|
|---|
| 88 |
|
|---|
| 89 | /** This boost::fusion map defines key-value or rather key-type pairs with
|
|---|
| 90 | * which we associate all times_t data members in MPQCData and their type.
|
|---|
| 91 | *
|
|---|
| 92 | * This lets us resolves any ambiguitites of types in MPQCData, e.g.
|
|---|
| 93 | * to know vector<double> is forces or energy_eigenvalues.
|
|---|
| 94 | *
|
|---|
| 95 | */
|
|---|
| 96 | typedef boost::fusion::map<
|
|---|
| 97 | boost::fusion::pair<MPQCDataFused::times_walltime, double >
|
|---|
| 98 | , boost::fusion::pair<MPQCDataFused::times_cputime, double >
|
|---|
| 99 | , boost::fusion::pair<MPQCDataFused::times_flops, double >
|
|---|
| 100 | > MPQCDataTimeMap_t;
|
|---|
| 101 |
|
|---|
| 102 | typedef boost::mpl::list<
|
|---|
| 103 | MPQCDataFused::times_walltime,
|
|---|
| 104 | MPQCDataFused::times_cputime,
|
|---|
| 105 | MPQCDataFused::times_flops
|
|---|
| 106 | > MPQCDataTimeVector_t;
|
|---|
| 107 |
|
|---|
| 108 | #endif /* MPQCDATAMAP_HPP_ */
|
|---|
