[ET Trac] [Einstein Toolkit] #465: Hydro_InitExcision test cases take a long time

[Einstein Toolkit]

#465: Hydro_InitExcision test cases take a long time
------------------------------------+---------------------------------------
  Reporter:  eschnett               |       Owner:     
      Type:  defect                 |      Status:  new
  Priority:  major                  |   Milestone:     
 Component:  EinsteinToolkit thorn  |     Version:     
Resolution:                         |    Keywords:     
------------------------------------+---------------------------------------

Comment (by rhaas):

 Sure. The reason we need the shock to pass into the excised region is to
 trigger some if statements inside of GRHydro so that we actually cover the
 code we want to test? The lines of code to check for are in the modified
 PPM scheme (trying to make sure not to remove the interesting code pieces
 from the test)? I'll throw in a couple of write(*,*) to check that we
 cover the same branches (or more) of the if statements before and after
 the change. Would that be sufficient? Would it be possible to star the
 shock so that it already overlaps the excised region (also: most of the
 slowness was due to user error on my part, mainly running with 2-processes
 4-threads-each on a quad core machine. Not sure about unoptimized
 builds.)?

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/465#comment:3>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit