Simplify access functions to the number of items
- Mar 14, 2022
-
-
Stéphane Del Pino authored
The constness check was made one the wrong one (typenames were inverted)
-
- Mar 11, 2022
-
-
Stéphane Del Pino authored
One does not use std::map anymore
-
- Mar 10, 2022
-
-
Stéphane Del Pino authored
All possible values are now filled using adequate types. For instance in 1d, since nodes, edges and faces designate the same entities, the following values are defined: nodes<->cells, edges<->cells and faces<->cells. Actually, in that case, the same memory (embedded Array) is used for all these data. In 2d, only faces and edges share the same data.
-
Stéphane Del Pino authored
-
Stéphane Del Pino authored
-
Stéphane Del Pino authored
-
Stéphane Del Pino authored
Also make some clean-up and update tests and add a bunch of missing qualifiers to functions
-
Stéphane Del Pino authored
-
- Mar 09, 2022
-
-
Stéphane Del Pino authored
-
- Mar 08, 2022
-
-
Stéphane Del Pino authored
Also change the semantic/implementation of sub-Array and sub-Table views. One does not use anymore Kokkos' subView which seems to be very expensive (2 to 3 times the cost for the Lagrangian acoustic solver if one uses subView for connectivity: lists of sub-items). It looks like the over cost is related to the memory management (here the reference counting). Sub-Array and sub-Table view are coarsely "embedded raw pointers" (which may not be safe as it is the case in Kokkos::StaticCrsGraph). However we tried to reduce the risk of having a view on a destroyed Array/Table by forbidding copy constructors. ConnectivityMatrix and ItemToItemMatrix still require refactoring. For instance it would be natural for ItemToItemMatrix to be replaced by the appropriate SubItemValuePerValue<ItemId>.
-
- Mar 04, 2022
-
-
Stéphane Del Pino authored
This was a marginal optimization that - is too specific (was used only once ...) - generate no measurable performance change
-
- Mar 02, 2022
-
-
Stéphane Del Pino authored
The new operator behaves exactly as the SubItemValuePerItem::itemArray(ItemId) and SubItemArrayPerItem::itemTable(ItemId) functions This convenient change is mainly made in the goal of simplifying item-to-item matrices used in connectivity
-
Stéphane Del Pino authored
-
- Mar 01, 2022
-
-
Stéphane Del Pino authored
Numbers of nodes, edges, faces and cells are now stored. This may reduce slightly the compilation time
-
Stéphane Del Pino authored
-