12/16-12/20

Data Viewing

Mrto 1.0 1.5 2.0 2.5

Vwind 15 20 25

Vrto 1.0 1.5 2.0

NOTE: The three plots below are interactive.

Your browser does not support this feature! Please update.

Timeline

The inner grid must done in the normal queue, but I should be able to squeeze most of the outer grid runs into the development queue.

• W 12/18
  • Inner grid: runID 50-10-15-**-hri
  • Inner grid: runID 50-10-20-**-hri
  • Inner grid: post-process today's runs
• T 12/19
  • Outer grid: runID 50-10-15-**-hro
  • Outer grid: runID 50-10-20-**-hro
  • Outer grid: post-process today's runs
  • Inner grid: runID 50-10-25-**-hri
  • Inner grid: runID 50-15-15-**-hri
  • Inner grid: post-process today's runs
• F 12/20
  • Super grid: test grid
  • Outer grid: runID 50-10-25-**-hro
  • Outer grid: runID 50-15-15-**-hro
  • Outer grid: post-process today's runs
  • Inner grid: runID 50-15-20-**-hri
  • Inner grid: runID 50-15-25-**-hri
  • Inner grid: post-process today's runs
• S 12/21
  • Outer grid: runID 50-15-20-**-hro
  • Outer grid: runID 50-15-25-**-hro
  • Outer grid: post-process today's runs
  • Inner grid: runID 50-20-15-**-hri
  • Inner grid: runID 50-20-20-**-hri
  • Inner grid: post-process today's runs
• S 12/22
  • Outer grid: runID 50-20-15-**-hro
  • Outer grid: runID 50-20-20-**-hro
  • Outer grid: post-process today's runs
  • Inner grid: runID 50-20-25-**-hri
  • Inner grid: runID 50-25-15-**-hri
  • Inner grid: post-process today's runs
• M 12/23
  • Outer grid: runID 50-20-25-**-hro
  • Outer grid: runID 50-25-15-**-hro
  • Outer grid: post-process today's runs
  • Inner grid: runID 50-25-20-**-hri
  • Inner grid: runID 50-25-25-**-hri
  • Inner grid: post-process today's runs
• T 12/24
  • Outer grid: runID 50-25-20-**-hro
  • Outer grid: runID 50-25-25-**-hro
  • Outer grid: post-process today's runs
• W 12/25
  • Start SN runs

Pipeline

I have nearly everything scripted at this point so everything should be smoothe from here. I only need to start jobs, transfer (bulk) data, and start post-processing.

1. In the job script: select resolution (low/high), grid (inner/outer/super), parameter space
2. Manually change grid resolution and MAKE executable for appropriate grid
3. Start job. As each parameter set finishes it is moved to a directory with runID formatted as

   <mass> - <mass ratio> - <wind vel> - <wind/orbit ratio> - <lr/hr i/o/s>

   with decimals removed. e.g., the default in the interactive plot above 50-10-15-10-lri stands for

   mass: 5.0 [Msun] - mass ratio: 1.0 - wind vel: 15 [km/s] - wind ratio: 1.0 - resolution: low res - grid: inner

4. When job completes, manually move files to astro, then submit next job
5. run process.py script which will move through each new run directory and run post-processing. It will then save inner boundarys in a directory using same runID system.
6. once all inner boundaries are created, data is transferred back to Stampede and outer grid is run in bulk in a similar fashion.