From 9c4220114fd58741027d258f47dc809edc875abd Mon Sep 17 00:00:00 2001
From: Jan Siwiec <jan.siwiec@vsb.cz>
Date: Mon, 23 Sep 2024 11:11:54 +0200
Subject: [PATCH] Update intel-vtune-amplifier.md

---
 docs.it4i/software/debuggers/intel-vtune-amplifier.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs.it4i/software/debuggers/intel-vtune-amplifier.md b/docs.it4i/software/debuggers/intel-vtune-amplifier.md
index 9675e77d3..b5bf1c36c 100644
--- a/docs.it4i/software/debuggers/intel-vtune-amplifier.md
+++ b/docs.it4i/software/debuggers/intel-vtune-amplifier.md
@@ -27,7 +27,7 @@ $ ml av VTune
 To profile an application with VTune Amplifier, special kernel modules need to be loaded. The modules are not loaded on the login nodes, thus direct profiling on login nodes is not possible. By default, the kernel modules are not loaded on compute nodes either. In order to have the modules loaded, you need to specify the `vtune=version` PBS resource at job submit. The version is the same as for the environment module. For example, for VTune/2016_update1, use:
 
 ```console
-$ qsub -q qexp -A OPEN-0-0 -I -l select=1,vtune=2020_update3
+$ salloc -p qexp -A PROJECT_ID --nodes=1 --gres=vtune:2020_update3
 ```
 
 After that, you can verify the modules `sep*`, `pax`, and `vtsspp` are present in the kernel:
-- 
GitLab