Docs @ 8a24386

MFC Action · MFC Action · commit ce9df20a8b91 · 2025-05-25T00:25:59.000Z
diff --git a/documentation/md_running.html b/documentation/md_running.html
@@ -189,8 +189,8 @@ <h3><a class="anchor" id="autotoc_md111"></a>
 <h3><a class="anchor" id="autotoc_md112"></a>
 AMD GPUs</h3>
 <ul>
-<li>Rocprof (ROC): <code>./mfc.sh run ... -t simulation --roc --hip-trace [rocprof flags]</code> allows one to visualize MFC's system-wide performance with <a href="https://ui.perfetto.dev/">Perfetto UI</a>. When used, <code>--roc</code> will run the simulation and generate files in the case directory for all targets. <code>results.json</code> can then be imported in <a href="https://ui.perfetto.dev/">Perfetto's UI</a>. Learn more about AMD Rocprof <a href="https://rocm.docs.amd.com/projects/rocprofiler/en/docs-5.5.1/rocprof.html">here</a> It is best to run case files with few timesteps to keep the report file sizes manageable.</li>
-<li>Omniperf (OMNI): <code>./mfc.sh run ... -t simulation --omni [omniperf flags]</code> allows one to conduct kernel-level profiling with <a href="https://rocm.docs.amd.com/projects/omniperf/en/latest/index.html">AMD's Omniperf</a>. When used, <code>--omni</code> will output profiling information for all subroutines, including rooflines, cache usage, register usage, and more, after the simulation is run. Adding this argument will moderately slow down the simulation and run the MFC executable several times. For this reason, it should only be used with case files with few timesteps.</li>
+<li>Rocprof Systems (RSYS): <code>./mfc.sh run ... -t simulation --rsys --hip-trace [rocprof flags]</code> allows one to visualize MFC's system-wide performance with <a href="https://ui.perfetto.dev/">Perfetto UI</a>. When used, <code>--roc</code> will run the simulation and generate files in the case directory for all targets. <code>results.json</code> can then be imported in <a href="https://ui.perfetto.dev/">Perfetto's UI</a>. Learn more about AMD Rocprof <a href="https://rocm.docs.amd.com/projects/rocprofiler/en/docs-5.5.1/rocprof.html">here</a> It is best to run case files with few timesteps to keep the report file sizes manageable.</li>
+<li>Rocprof Compute (RCU): <code>./mfc.sh run ... -t simulation --rcu -n &lt;name&gt; [rocprof-compute flags]</code> allows one to conduct kernel-level profiling with <a href="https://rocm.docs.amd.com/projects/rocprofiler-compute/en/latest/what-is-rocprof-compute.html">ROCm Compute Profiler</a>. When used, <code>--rcu</code> will output profiling information for all subroutines, including rooflines, cache usage, register usage, and more, after the simulation is run. Adding this argument will moderately slow down the simulation and run the MFC executable several times. For this reason, it should only be used with case files with few timesteps.</li>
 </ul>
 <p><a class="anchor" id="restarting-cases"></a> </p>
 <h2><a class="anchor" id="autotoc_md113"></a>
