diff src/BoundaryConditions/boundary_condition.jl @ 1395:bdcdbd4ea9cd feature/boundary_conditions

Merge with default. Comment out broken tests for boundary_conditions at sat
author Vidar Stiernström <vidar.stiernstrom@it.uu.se>
date Wed, 26 Jul 2023 21:35:50 +0200
parents d26aef8a5987
children 35840a0681d1
line wrap: on
line diff
--- a/src/BoundaryConditions/boundary_condition.jl	Tue Feb 07 21:55:07 2023 +0100
+++ b/src/BoundaryConditions/boundary_condition.jl	Wed Jul 26 21:35:50 2023 +0200
@@ -70,8 +70,8 @@
 # TODO: Is the return type of discretize really a good interface
 # for the boundary data?
 # Moreover, instead of explicitly converting to a LazyArray here
-# should we defer this to evalOn (and extend evalOn for scalars as well)?
-# I.e. if evalOn returns a LazyArray, the boundary data is lazy. Otherwise
+# should we defer this to eval_on (and extend eval_on for scalars as well)?
+# I.e. if eval_on returns a LazyArray, the boundary data is lazy. Otherwise
 # it is preallocated.
 
 function discretize(bd::ConstantBoundaryData, boundary_grid)
@@ -83,11 +83,11 @@
 end
 
 function discretize(bd::SpaceDependentBoundaryData, boundary_grid)
-    return t -> evalOn(boundary_grid, bd.val)
+    return t -> eval_on(boundary_grid, bd.val)
 end
 
 function discretize(bd::SpaceTimeDependentBoundaryData, boundary_grid)
-    return t -> evalOn(boundary_grid, bd.val(t))
+    return t -> eval_on(boundary_grid, bd.val(t))
 end
 
 function discretize(::ZeroBoundaryData, boundary_grid)