YaqiWang
commented
5 years ago Another thing I noticed is that when we have lots of subapps, the screen output is pretty messy. Things will get even worse if we have multiple levels of subapps. We should think of a way to trim down outputs of subapps so that we can stay focused on important messages from subapps. I suggest on MultiApp level we have a verbose parameter to control the screen outputs from subapp. But this requires MooseApp to support lesser outputs. One suggestion is to just output postprocessor values line-by-line for each time step with number of nonlinear/linear iterations taken.
permcody
Rationale
This issue was raised by @gleicher27 who practice multiphysics coupling calculations a lot. We can use this issue for making the output for these kinds of calculation prettier.
Description
So far, we possibly can create a vector postprocessor to report time steps a sub-application takes during sub-cycling. Residual norms of subapps before and after they are solved are the important information about the Picard convergence, thus we might want to highlighting them in some way. There will possibly more we can think of.
Impact
Improved user experience.