|
OpenFPM at most basic level operations manage the **Memory**: getting some chunk of memory, destroy it, or resize it on any devices or with particular properties. The component inside OpenFPM designed to do such task is **devices (Memory)**. After that we have the capabilities to create memory we have to shape it, or give to them some meaning. More specifically we want to **Map** complex structures on memory, like a Grid, Vectors, Graph ... The component designed to do such task in OpenFPM is ** data **. While data implement complex structures on single machine, we would like to have distributed version of such complex structures. . After that we have complex structure, we would like to create distributed structures |
|
OpenFPM at most basic level operations manage the **Memory**: getting some chunk of memory, destroy it, or resize it on any devices or with particular properties. The component inside OpenFPM designed to do such task is **devices (Memory)**. After that we have the capabilities to create memory we have to shape it, or give to them some meaning. More specifically we want to **Map** complex structures on memory, like a Grid, Vectors, Graph ... The component designed to do such task in OpenFPM is ** data **. While ** data ** implement complex structures on single machine, we would like to have distributed version of such complex structures. The component designed to do such task in OpenFPM is ** pdata **. Here pdata does not directly depend on data, but there is an intra-modularity between them given by Vcluster. Why we need this ? There are several reasons, the first is modularization of the comunication libraries |