Skip to content

Instantly share code, notes, and snippets.

@ysimillides
Created August 14, 2017 09:03
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ysimillides/30fdbd71951c5e29e5f999635410b6de to your computer and use it in GitHub Desktop.
Save ysimillides/30fdbd71951c5e29e5f999635410b6de to your computer and use it in GitHub Desktop.
fenics.jl differences
#Throughout the project we have tried to keep the API and the usage the same as direct interfacing with FEniCS.
#Due to some design preferences and technical issues they're may be slight differences in various parts.
#Regarding the Solve Funtion in FEniCS ,depending on the functionality we call
lvsolve , nlvsolve, anlvsolve #depending on what kind of solve we desire.
lvsolve # is the linear variational solver
nlvsolve # is the non-linear variational solver
anlvsolve # corresponds to the adapative non-linear solver.
#For the DirichletBC, whereas in FEniCS we would define a function as
def u0_boundary(x, on_boundary):
return on_boundary
#and then call DirichletBC(*args,u0_boundary)
#in FEniCS.jl we call it as
DirichletBC(*args,"on_boundary")
#Furthermore, in some cases, where importing functions directly from fenics as
fenics.ExampleFunction(args), #we may need to append the input with args.pyobject as
fenics.ExampleFunction(args.pyobject)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment