"postprocess" block¶
Postprocessing is configured in the JSON block "postprocess". Each named subobject such as "nodeu" or "volume" is one postprocessor definition.
json
{
"postprocess": {
"nodeu": {
"type": "nodalvalue",
"dof": "phi",
"parameters": {
"nodeid": 51
}
},
"sidegraduy": {
"type": "sideintegralvectormate",
"side": ["right"],
"parameters": {
"vectormate": "gradu",
"component": 1
}
},
"volume": {
"type": "volume",
"domain": ["alldomain"]
}
}
}
Options inside each named postprocess block¶
"type": required string. Supported values are listed below."dof": optional string. If present, it must be one of the names from the"dofs"block."domain": optional array of bulk domain names. If omitted, AsFem uses["alldomain"]."side": optional array of boundary names. If omitted, the side list stays empty."parameters": optional JSON object. The parser stores it and passes it to the selected postprocessor.
For side-based postprocessors, provide "side" explicitly even though ReadPostprocessBlock.cpp only validates it when present.
The current parser does not validate every key inside "parameters" here. The expected parameter names depend on the chosen postprocessor implementation. Upstream examples use keys such as "nodeid", "scalarmate", "vectormate", "rank2mate", "rank4mate", "component", "i-index", and "j-index".
Supported nodal postprocessors¶
text
nodalvalue
nodalscalarmate
nodalvectormate
nodalrank2mate
nodalrank4mate
Supported side postprocessors¶
text
area
sideaveragevalue
sideaveragescalarmate
sideaveragevectormate
sideaveragerank2mate
sideaveragerank4mate
sideintegralvalue
sideintegralscalarmate
sideintegralvectormate
sideintegralrank2mate
sideintegralrank4mate
user1sideintegral
Supported volume postprocessors¶
text
volume
volumeaveragevalue
volumeaveragescalarmate
volumeaveragevectormate
volumeaveragerank2mate
volumeaveragerank4mate
volumeintegralvalue
volumeintegralscalarmate
volumeintegralvectormate
volumeintegralrank2mate
volumeintegralrank4mate
user1volumeintegral