Changes related to "flameSpeed" and "dfChemistryModel" #529
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You should now be able to add reviewers for your PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The past flameSpeed is only used when the time step is 0.001s.
Now, we give two choice.
If you choose flameSpeed, the time step will be set as the same as it in controlDict.
If you choose flameSpeed1, you can input a float number as the time step.
In the current version, when solving Yeqn with DNN methods, all the points will be chosen as the problem size, and we then solve all points whose temperature are above frozenTemperature.
This process makes Chemistry time ratio over 60%.
If we read frozenTemperature before we decide problem size, Chemistry time ratio will be 10%.