You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I compute something with FrontISTR used dynamic explicit method, I found that there are some result keep 0.000000000000E+0 in all result files, They are the CONTACT_STATE and CONTACT_NFORCE etc. For CONTACT_STATE, I find a funcation named set_contact_state_vector( fstrSOLID%contacts(i), dt, fstrSOLID%CONT_RELVEL, fstrSOLID%CONT_STATE ) in fstr_scan_contact_state, but not in fstr_scan_contact_state_exp , when I added it, CONTACT_STATE changed. But for CONTACT_NFORCE , I do not know how to fix it. Does explicit method should not output these contact information, or just some bugs?
The text was updated successfully, but these errors were encountered:
The dynamic explicit function with contact state has not been tested well. sorry for inconvenience.
Would you try the dynamic implicit function, please?
Besides, would you share the input files (*.msh file and *.cnt file) with us?
When I compute something with FrontISTR used dynamic explicit method, I found that there are some result keep 0.000000000000E+0 in all result files, They are the CONTACT_STATE and CONTACT_NFORCE etc. For CONTACT_STATE, I find a funcation named set_contact_state_vector( fstrSOLID%contacts(i), dt, fstrSOLID%CONT_RELVEL, fstrSOLID%CONT_STATE ) in fstr_scan_contact_state, but not in fstr_scan_contact_state_exp , when I added it, CONTACT_STATE changed. But for CONTACT_NFORCE , I do not know how to fix it. Does explicit method should not output these contact information, or just some bugs?
The text was updated successfully, but these errors were encountered: