From 0121514a39163e820996ca6ef0e37b146f7f2871 Mon Sep 17 00:00:00 2001 From: rhaas Date: Thu, 28 Mar 2013 01:49:05 +0000 Subject: GRHydro_Init_Data: add routine to force boundary data to Bondi From: Roland Haas git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinInitialData/GRHydro_InitData/trunk@205 ac85fae7-cede-4708-beff-ae01c7fa1c26 --- schedule.ccl | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'schedule.ccl') diff --git a/schedule.ccl b/schedule.ccl index d5aa21a..b0a1dbb 100644 --- a/schedule.ccl +++ b/schedule.ccl @@ -257,6 +257,16 @@ SCHEDULE GRHydro_BondiM_Range IN HydroBase_Con2Prim BEFORE Con2Prim } "force analytic solution outside anulus" } +if(bondi_overwrite_boundary ) { +# this is a terrible HACK. We really should at least schedule ourselves in +# Boundaries and look at cctk_bbox and the symmetry flags +# by now Cactus is convenient CCTK_LOOP macros for this... +SCHEDULE GRHydro_BondiM_Boundary IN HydroBase_Boundaries BEFORE HydroBase_Select_Boundaries +{ + LANG: C +} "force analytic solution in boundaries" +} + if (CCTK_EQUALS(initial_Bvec, "poloidalmagfield") || CCTK_EQUALS(initial_Avec, "poloidalmagfield")) { # SCHEDULE GRHydro_PoloidalMagFieldM AT CCTK_INITIAL AFTER IN HydroBase_Initial AFTER rnsid_init AFTER TOV_Initial_Data after CCCC_StarMapper_InitialData -- cgit v1.2.3