Conversation
|
|
Current |
|
Producing artifacts requires placing your output files to results directory. I think I haven't implemented this for diffractive_vm yet. Ideas are welcome. |
|
The config.yml file has been updated for the physics benchmarks |
Sorry for the naïve questions, but does this just mean I should rename the |
Updated config.yml to include simulate task
Yes. |
benchmarks/u_rho/config.yml
Outdated
| stage: collect | ||
| needs: ["u_channel_rho:simulate"] | ||
| script: | ||
| - cp benchmark_output/campaign_23.12.0_combined_60files_eicrecon.edm4eic.plots_figures/*.pdf figures/ |
There was a problem hiding this comment.
One issue here is that the contents of the "current" directory is not preserved, only what's in the $LOCAL_DATA_PATH space. I think it would be simpler to move this line to the line after you call snakemake, and let gitlab output results/ directory as an artifact.
|
Okay I edited the procedure to immediately create the results directory and copy to it. |
Testing removing analysis compilation from u-channel rho pipeline
Reimplemented compilation step
Updated compile step in snakefile
Edited compile rule
Updated file paths
Updated compile path
|
Should be a matter of including into the top-level Snakefile. I've pushed the changes, let's see if it works. |
|
Produces some pretty plots now: https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/jobs/2335547/artifacts/file/results/benchmark_rho_dNdu.pdf |
Demonstration of benchmark for CA Consortium Meeting, using simulation campaign
4 participants
Briefly, what does this PR introduce?
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No breaking changes.
Does this PR change default behavior?
This PR should create an automatic benchmark using u-channel rho production to benchmark the tracking performance of the B0 trackers