MueLu: forcing MueLu to keep data for export to files
Created by: mayrmt
@trilinos/muelu
Current Behavior
The sublist export data
in the simple XML interface forces MueLu to keep data for printing. However, when looking at the content of a single MueLu::Level
, I'm confused by multiple instances of data that has been kept.
Motivation and Context
The easy XML input allows to fill the parameter list
<ParameterList name="export data">
<Parameter name="A" type="string" value="{0,1}"/>
<Parameter name="R" type="string" value="{0,1}"/>
<Parameter name="P" type="string" value="{0,1}"/>
<Parameter name="Nullspace" type="string" value="{0,1,2}"/>
<Parameter name="Coordinates" type="string" value="{0,1,2}"/>
</ParameterList>
which forces MueLu to keep certain data and to print this data to files. When selecting "A" and "Nullspace" in export data
, a level contains this data:
LevelID = 0
data name gen. factory addr. req keep type data req'd by
-------------------- ------------------ ----- ----- --------------- -------------- --------------------
A 0x266dda0 0 Keep unknown not available
Nullspace 0x266ec20 0 Keep unknown not available
A NoFactory 0 User Matrix available
Nullspace NoFactory 0 User Vector available
PostSmoother NoFactory 0 Final SmootherBase available
PreSmoother NoFactory 0 Final SmootherBase available
A
and Nullspace
occur twice, however with different generating factories. The ones generated by NoFactory
are marked as available
while the ones generated by 0x266dda0
and 0x266ec20
are not available
.
Why is that? Which instance of the Nullspace
can be accessed after SetupHierarchy()
has been called?
My motivation to look at this is that I want to force MueLu to keep the aggregates around since I need them after the setup of the hierarchy (#2262 (closed)). I'm looking at the Nullspace
only to understand the concept of keeping stuff.
Related Issues
- Blocks #2262 (closed)
- Related to #2260 (closed)