From 737c2cf456e5db9d9ac9ed4e33cdf719a0954303 Mon Sep 17 00:00:00 2001 From: Zachary Sweger Date: Tue, 10 Sep 2024 12:09:23 -0700 Subject: [PATCH] Propagation to website failed. Remove tex code --- _episodes/03-making_useful_figures.md | 39 +-------------------------- 1 file changed, 1 insertion(+), 38 deletions(-) diff --git a/_episodes/03-making_useful_figures.md b/_episodes/03-making_useful_figures.md index 4dce477..756f65f 100644 --- a/_episodes/03-making_useful_figures.md +++ b/_episodes/03-making_useful_figures.md @@ -56,44 +56,7 @@ Even a well-labeled figure will still be ambiguous as to what is being plotted. This document may be written in LaTeX, exported as a PDF, and then uploaded to [GitHub under your benchmark](https://github.com/eic/physics_benchmarks/blob/pr/u_channel_sweger/benchmarks/u_rho/BenchmarkPlotsExplained.pdf). The way most users will interact with your benchmark is at the level of the artifacts it produces. When others are looking through the plots produced by your benchmark, this description of your figures should be readily available as an artifact itself. To achieve this, you can use this template tex document: -```tex -%====================================================================% -% BENCH.TEX % -% Written by YOUR NAME % -%====================================================================% - %\documentclass[final,3p]{elsarticle} -\documentclass{bench} - - - -% A useful Journal macro -\def\Journal#1#2#3#4{{#1} {\bf #2}, #3 (#4)} - -\NewDocumentCommand{\codeword}{v}{% -\texttt{\textcolor{black}{#1}}% -} - -% Some other macros used in the sample text -\def\st{\scriptstyle} -\def\sst{\scriptscriptstyle} -\def\epp{\epsilon^{\prime}} -\def\vep{\varepsilon} -\def\vp{{\bf p}} -\def\be{\begin{equation}} -\def\ee{\end{equation}} -\def\bea{\begin{eqnarray}} -\def\eea{\end{eqnarray}} -\def\CPbar{\hbox{{\rm CP}\hskip-1.80em{/}}} - -\begin{document} -\title{YOUR BENCHMARK NAME Benchmark Figures} -\maketitle - -\codeword{benchmark_plot1.pdf}: -This figure shows... - -\end{document} -``` +