-
Notifications
You must be signed in to change notification settings - Fork 60
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.
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
Adding a custom parsed function #1143
Conversation
a94e69f
to
0903ca2
Compare
87d32f8
to
e9a5bff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1-2 comments that's all. Cool work man
48a35de
to
c4534a7
Compare
c4534a7
to
c2df53b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Excited about the reactive physics module in Lethe coming soon. I have only a few remarks regarding documentation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only few suggestion for comments :)
Co-authored-by: hepap <[email protected]>
Description of the problem In the idea of adding a reactive physics, a way to parse functions based on any variables needed to be added. For example, when a species A reacts at a rate of -dA/dt = k*A, the source term for A depends on A itself. Parsed functions in deal.II didn't allow to parse functions unless they depended only on x,y,z,t. Description of the solution A new custom class based on the deal.II implementation of parsed functions (using muParser) is added to Lethe. This class has the template parameter n_component. It requires that classes are instantiated with n_component expressions as well. Physics that will use this class will have the responsibility of interfacing between their variables of interest and the class ParsedFunctionCustom itself. When a different number of variables/expressions will be needed by a solver, this solver will have the responsibility of introducing dummy variables or expressions. This solution might change if required. How Has This Been Tested? [core/custom_parsed_functions] Unit test of value and gradient functions. Documentation Not at the moment, except for doxygen. Future changes A reactive auxiliary physics will be implemented using this class. Co-authored-by: Bruno Blais <[email protected]> Co-authored-by: hepap <[email protected]> Former-commit-id: 8b0aab5
Description of the problem In the idea of adding a reactive physics, a way to parse functions based on any variables needed to be added. For example, when a species A reacts at a rate of -dA/dt = k*A, the source term for A depends on A itself. Parsed functions in deal.II didn't allow to parse functions unless they depended only on x,y,z,t. Description of the solution A new custom class based on the deal.II implementation of parsed functions (using muParser) is added to Lethe. This class has the template parameter n_component. It requires that classes are instantiated with n_component expressions as well. Physics that will use this class will have the responsibility of interfacing between their variables of interest and the class ParsedFunctionCustom itself. When a different number of variables/expressions will be needed by a solver, this solver will have the responsibility of introducing dummy variables or expressions. This solution might change if required. How Has This Been Tested? [core/custom_parsed_functions] Unit test of value and gradient functions. Documentation Not at the moment, except for doxygen. Future changes A reactive auxiliary physics will be implemented using this class. Co-authored-by: Bruno Blais <[email protected]> Co-authored-by: hepap <[email protected]> Former-commit-id: 8b0aab5
Description of the problem
Description of the solution
n_component
. It requires that classes are instantiated withn_component
expressions as well.How Has This Been Tested?
Documentation
Future changes