Skip to content

chef_guide.md

Latest commit

 

History

History
43 lines (30 loc) · 1.84 KB

chef_guide.md

File metadata and controls

43 lines (30 loc) · 1.84 KB

Chefs' Guide for Timeline Production

The timeline code is provided on ifarm via

module load timeline

Please report any issues to the software maintainers, such as warnings or error messages.

🟢 Step 1: The workflow

Use the qtl model as part of your usual cooking workflow; see the Chefs' documentation wiki.

Output files will appear in your chosen output directory, within hist/detectors/.

🟢 Step 2: Make the timelines

run-detectors-timelines.sh -d $dataset -i $out_dir/hist/detectors --run-slurm

where $out_dir is your output directory from Step 1 and $dataset is a unique name for this cook, e.g., rga_v1.23.

Notice the --run-slurm option which will set up a slurm script for each detector timeline. To submit the jobs, run the printed sbatch command or run with the --submit-slurm option to automatically submit. Once all jobs have finished successfully, rerun using the --after-slurm option instead to complete the organization of the output.

Output will appear in ./outfiles/$dataset/.

🟢 Step 3: Deploy the timelines

deploy-timelines.sh -d $dataset -t $target_dir -D

where $target_dir is a subdirectory of /group/clas/www/clas12mon/html/hipo, for example,

-t rgb/pass0/$dataset   # deploys to /group/clas/www/clas12mon/html/hipo/rgb/pass0/$dataset/
  • remove the -D argument if everything looks okay (-D only prints what the script will do, i.e., a "dry run")
  • a URL will be printed upon success, and a link will appear in clas12mon in your run group's area momentarily

For more details, such as producing physics QA timelines, see other guides in the table of contents or reach out to the software maintainers.
⚡