validParams check on FlowConvection Kernel #112
-
Hello everyone Since I updated the MOOSE suite a couple days ago, I've noticed a warning displayed on my terminal each time I run something due to my custom FlowConvection kernel:
So I tried my hand at fixing the problem, hopefully just by following the instructions. I attached the a txt file with both the .C and .h code, and I made what I deemed to be the necessary edits and left comments by them. If anyone has a few spare minutes and can quickly check my work, I would greatly appreciate it! Edit: I tried to compile as is and I got the following errors:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Just looking at the error output, it appears as though it's not interpreting your comments correctly. I would remove them and try to build again. This warning is just saying that the old (circa two years ago and before) method of declaring valid object parameters is being removed from the framework....which is actually happening very soon (see idaholab/moose#19440). If you would like to make a pull request fixing this object up, we would welcome it! To make looking at code changes easier, I would highly recommend that you create a git branch and commit your code changes. This lets us look at a summary of your changes and make direct suggestions in the code. Look for some tips on how to work in git that I made for Zapdos here starting with the heading "Work in a GitHub Fork": https://shannon-lab.github.io/zapdos/development/contributing.html |
Beta Was this translation helpful? Give feedback.
Just looking at the error output, it appears as though it's not interpreting your comments correctly. I would remove them and try to build again.
This warning is just saying that the old (circa two years ago and before) method of declaring valid object parameters is being removed from the framework....which is actually happening very soon (see idaholab/moose#19440). If you would like to make a pull request fixing this object up, we would welcome it!
To make looking at code changes easier, I would highly recommend that you create a git branch and commit your code changes. This lets us look at a summary of your changes and make direct suggestions in the code. Look for some tips on how to wo…