Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Print postprocessor values in PicardSolve if the postprocessor is used for controlling convergence #16940

Closed
YaqiWang opened this issue Feb 10, 2021 · 0 comments · Fixed by #16941
Closed

Print postprocessor values in PicardSolve if the postprocessor is used for controlling convergence #16940

YaqiWang opened this issue Feb 10, 2021 · 0 comments · Fixed by #16941
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.

Comments

@YaqiWang
Copy link
Contributor

YaqiWang commented Feb 10, 2021 •
edited

Reason

A postprocessor can be used to control Picard convergence PicardSolve but it may choose to not show on screen. Adding a colored screen print-out like the residual norms for showing the Picard convergence will make the screen output more user friendly.

Design

Using the tool Console::outputNorm to output the postprocessor history when a postprocessor is used by PicardSolve.

Impact

Make using postprocessor control the Picard convergence more user friendly. No impact on others because it is an output enhancement.
@YaqiWang YaqiWang added P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software. labels Feb 10, 2021
YaqiWang added a commit to YaqiWang/moose that referenced this issue Feb 10, 2021
@YaqiWang
show postprocessor history when the postprocessor is used for Picard …
78aa234 
…convergence check idaholab#16940
@YaqiWang YaqiWang mentioned this issue Feb 10, 2021
Merged
YaqiWang added a commit to YaqiWang/moose that referenced this issue Feb 11, 2021
@YaqiWang
show postprocessor history when the postprocessor is used for Picard …
6aaa9df 
…convergence check idaholab#16940
YaqiWang added a commit to YaqiWang/moose that referenced this issue Feb 11, 2021
@YaqiWang
show postprocessor history when the postprocessor is used for Picard …
74a407f 
…convergence check idaholab#16940
loganharbour pushed a commit to loganharbour/moose that referenced this issue Feb 15, 2021
@YaqiWang @loganharbour
show postprocessor history when the postprocessor is used for Picard …
c652c3d 
…convergence check idaholab#16940
jain651 pushed a commit to jain651/moose that referenced this issue Apr 19, 2021
@YaqiWang
show postprocessor history when the postprocessor is used for Picard …
7a13e9d 
…convergence check idaholab#16940
aeslaughter pushed a commit to aeslaughter/moose that referenced this issue Jun 2, 2021
@YaqiWang @aeslaughter
show postprocessor history when the postprocessor is used for Picard …
cebf5b7 
…convergence check idaholab#16940
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.
Projects
None yet
Milestone
No milestone
2 participants
@YaqiWang @loganharbour