...
which will generate the following scripts, located in a new directory called logs_test_ozstar_chips :
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ ls logs_test_ozstar_chips run_clean_test_8dec_test_ozstar_chips.sh ##Cleans up intermediate data products run_grid_1093641624_test_8dec_test_ozstar_chips.sh ##Grids the first observation run_grid_1093641864_test_8dec_test_ozstar_chips.sh ##Grids the second observation run_grid_1093642232_test_8dec_test_ozstar_chips.sh ##Grids the third observation run_lssa_test_8dec_test_ozstar_chips_xx.sh ##Makes the XX power spectra run_lssa_test_8dec_test_ozstar_chips_yy.sh ##Makes the YY power spectra |
if there are any errors in the input arguments, you should get some form of error message telling you what to do next. If this command runs find. To actually launch your jobs, remove the --no_run command. I usually put this all in a bash script, so you'd do something like:
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ more run_CHIPS.sh
source /fred/oz048/jline/software/chips/module_load_chips.sh
run_CHIPS.py \
--cluster=ozstar \
--obs_list=/fred/oz048/jline/test_CHIPS_scripts/obs_list.txt \
--uvfits_dir=test_8dec \
--output_tag=test_ozstar_chips \
--output_dir=/fred/oz048/jline/test_CHIPS_scripts/CHIPS_outputs/ \
--band=high --obs_range=0,3
$ source run_CHIPS.sh
Command run: sbatch --parsable run_grid_1093641624_test_8dec_test_ozstar_chips.sh
Job ID: 27145363
Command run: sbatch --parsable --dependency=afterok:27145363 run_grid_1093641864_test_8dec_test_ozstar_chips.sh
Job ID: 27145364
Command run: sbatch --parsable --dependency=afterok:27145363:27145364 run_grid_1093642232_test_8dec_test_ozstar_chips.sh
Job ID: 27145365
Command run: sbatch --parsable --dependency=afterok:27145363:27145364:27145365 run_lssa_test_8dec_test_ozstar_chips_xx.sh
Job ID: 27145366
Command run: sbatch --parsable --dependency=afterok:27145363:27145364:27145365 run_lssa_test_8dec_test_ozstar_chips_yy.sh
Job ID: 27145367
Command run: sbatch --parsable --dependency=afterok:27145366:27145366 run_clean_test_8dec_test_ozstar_chips.sh |
...
Debugging actual CHIPS runs: all the log outputs and error messages for this run will be output into logs_test_ozstar_chips , so if you jobs error, try checking the output logs and error messages located there. If everything runs fine, you can just delete that entire logs_test_ozstar_chips directory (saves on the number of files quota).
Plotting the outputs
See (page to be written soon) for a full overview of the plotting commands available. But a quick example of how to make a 2D cross-power spectra using outputs of the OzStar example is. Note the output tag for the files is a combination of the --output_tag and --uvfits_dir options that were fed to run_CHIPS.py :
| Code Block | ||||
|---|---|---|---|---|
| ||||
source /fred/oz048/jline/software/chips/module_load_chips.sh
plotchips_all.py \
--basedir=/fred/oz048/jline/test_CHIPS_scripts/CHIPS_outputs/ \
--polarisation='yy' \
--chips_tag=test_8dec_test_ozstar_chips \
--min_power=1e3 --max_power=1e15 |
this will produce a plot called chips2D_yy_test_8dec_test_ozstar_chips_crosspower.png which looks like this:
this is some random EoR1 data I found on OzStar so I have no idea of the quality or what peeling was done, but hey, it's a power spectrum!