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 trying to use the 'Wale' model, I received the following error: AttributeError: 'DirichletBC' object has no attribute 'user_sub_domain'.
Having changed 'user_sub_domain' to user_subdomain (compatible with dolfin 2018), this error is resolved.
Then the following error occurs:
"/home/ubuntu/anaconda3/envs/oasis/lib/python3.7/site-packages/oasis-2018.1-py3.7.egg/oasis/solvers/NSfracStep/LES/common.py", line 21, in derived_bcs
m = bc.markers() # Get facet indices of boundary
AttributeError: 'DirichletBC' object has no attribute 'markers'
Is there some other way to get facet indices of the boundary within the " derived_bcs" function in oasis.solvers.NSfracStep.LES.common, to make this function compatible with dolfin 2018.1?
With kind regards,
Joel
The text was updated successfully, but these errors were encountered:
Dear Sir,
When trying to use the 'Wale' model, I received the following error: AttributeError: 'DirichletBC' object has no attribute 'user_sub_domain'.
Having changed 'user_sub_domain' to user_subdomain (compatible with dolfin 2018), this error is resolved.
Then the following error occurs:
"/home/ubuntu/anaconda3/envs/oasis/lib/python3.7/site-packages/oasis-2018.1-py3.7.egg/oasis/solvers/NSfracStep/LES/common.py", line 21, in derived_bcs
m = bc.markers() # Get facet indices of boundary
AttributeError: 'DirichletBC' object has no attribute 'markers'
In the following link it is stated that in python version of dolfin 2018.1 the markers() attribute is indeed missing.
https://bitbucket.org/fenics-project/dolfin/issues/1042/python-interface-for-dirichletbcmarkers
Is there some other way to get facet indices of the boundary within the " derived_bcs" function in oasis.solvers.NSfracStep.LES.common, to make this function compatible with dolfin 2018.1?
With kind regards,
Joel
The text was updated successfully, but these errors were encountered: