anchor.diff:      use global_mod, only: ip, dp, minimum_allowed_depth, default_nonlinear_timestepping_method
       use domain_mod, only: domain_type
       use multidomain_mod, only: multidomain_type, setup_multidomain, test_multidomain_mod
  -    use boundary_mod, only: boundary_stage_transmissive_normal_momentum, flather_boundary, &
  -        boundary_stage_transmissive_momentum, boundary_stage_radiation_momentum
  +    use boundary_mod, only: flather_boundary, boundary_stage_radiation_momentum
       use local_routines
       use timer_mod
       use logging_mod, only: log_output_unit
  
positive.code:         real(dp):: t0 = 0.0_dp
      end type
  
      !
      ! Parameter controlling the northern boundary treatment
      ! Depending on the solver, it is nontrivial to get a good boundary forcing for this problem, that is sufficiently radiative
      ! without overly distorting the tsunami.
      character(len=charlen) :: boundary_type = 'boundary_stage_radiation_momentum'
  
      ! This will hold the information -- is seen by other parts of the module
  
negative.code:     call md%set_point_gauges_from_csv("point_gauges.csv", skip_header=1_ip)
     
      do j = 1, size(md%domains) 
          select case(boundary_type)
          case('flather_with_vh_from_continuity')
              md%domains(j)%boundary_subroutine => flather_boundary
          case('boundary_stage_radiation_momentum')
              md%domains(j)%boundary_subroutine => boundary_stage_radiation_momentum
  