-
Notifications
You must be signed in to change notification settings - Fork 239
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
Balance for HT process #2132
Balance for HT process #2132
Changes from 1 commit
81d275e
d8b55d5
744ddd4
38413ee
7546ae2
f608621
2689f06
1d9aa9a
0be9c2b
75fa95f
fdeafde
3f11cb8
dd8c5ca
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -91,7 +91,7 @@ class HTFEM : public HTLocalAssemblerInterface | |
/// Computes the flux in the point \c pnt_local_coords that is given in | ||
/// local coordinates using the values from \c local_x. | ||
// TODO add time dependency | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yep, that would be nice (for the sake of completeness). Could you please add it now? |
||
std::vector<double> getFlux( | ||
Eigen::Vector3d getFlux( | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For the HT process the problem is that there are potentially two different interesting fluxes: There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Or one could pass the variable_id to getFlux? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You are right, there are potentially two different interesting fluxes. Maybe other processes have also interesting quantities fluxes. For this reason we would need rather general names. I opened an issue for discussion and for the time being I would keep the implementation of this PR. Is this okay for you? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK. |
||
MathLib::Point3d const& pnt_local_coords, | ||
std::vector<double> const& local_x) const override | ||
{ | ||
|
@@ -149,10 +149,9 @@ class HTFEM : public HTLocalAssemblerInterface | |
auto const b = this->_material_properties.specific_body_force; | ||
q += K_over_mu * rho_w * b; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not getting the intentions of the comment. What is 'downwards'? Maybe it's copied from some other context... |
||
} | ||
std::vector<double> flux; | ||
flux.resize(3); | ||
Eigen::Map<GlobalDimVectorType>(flux.data(), flux.size()) = q; | ||
|
||
Eigen::Vector3d flux; | ||
flux.head<GlobalDim>() = q; | ||
return flux; | ||
} | ||
|
||
|
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.
Isn't the flux 2D in two dimentsions?