-
Notifications
You must be signed in to change notification settings - Fork 97
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
$EPSILON in the bc-file can replace the automatically calculated search length #107
Conversation
…e initialized with -1, which means it is not active and activated via Keyword in the bc file.
…or the 2units2faults problem
…or the 2units2faults problem
I will debug based on 2units2faults_FCT, hm1_1Dbeam, tm1_3Dorigin.numdiff. |
… change the input files of the benchmarks
@wenqing : I think this can be merged now. We will need the same for source terms - Will be the next Pull Request |
…then this should be done during the construct grid procedure an not in inside the search function.
@@ -1378,7 +1378,12 @@ void CBoundaryConditionsGroup::Set(CRFProcess* pcs, int ShiftInNodeVector, const | |||
// debug_out.close(); | |||
//#endif | |||
std::vector<size_t> msh_nod_vec; | |||
double computed_search_length = m_msh->getSearchLength(); | |||
if (bc->epsilon != -1) |
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.
It is better to use epsilon from gli. We can take a look together once you are back.
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.
@norihiro-w : @Thomas-TK explained me the reason why to use this BC tolerance: to allow different processes have different regions of nodes for BCs. I think it looks good. Do you have any comment?
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.
no i have no further comments. i will merge this
Making use of $EPSILON in the bc-file for boundary conditions. Should be initialized with -1, which means it is not active and can be activated via the keyword in the bc file.