From 9b7eedd2f75f5e13ff739d213f6d9b13b37f8651 Mon Sep 17 00:00:00 2001
From: Natalie Breidenbach <natalie.breidenbach@tu-dresden.de>
Date: Tue, 28 Nov 2023 14:32:27 +0100
Subject: [PATCH] Update tensorboard.md

---
 doc.zih.tu-dresden.de/docs/software/tensorboard.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc.zih.tu-dresden.de/docs/software/tensorboard.md b/doc.zih.tu-dresden.de/docs/software/tensorboard.md
index a397498ed..a2ce59608 100644
--- a/doc.zih.tu-dresden.de/docs/software/tensorboard.md
+++ b/doc.zih.tu-dresden.de/docs/software/tensorboard.md
@@ -61,9 +61,9 @@ Then, create a workspace for the event data, that should be visualized in Tensor
 already have an event data directory, you can skip that step.
 
 ```console
-marie@compute$ ws_allocate -F scratch tensorboard_logdata 1
+marie@compute$ ws_allocate -F /data/horse tensorboard_logdata 1
 Info: creating workspace.
-/scratch/ws/1/marie-tensorboard_logdata
+/data/horse/ws/1/marie-tensorboard_logdata
 [...]
 ```
 
@@ -72,7 +72,7 @@ accessible for TensorBoard. Please find further information on the official [Ten
 Then, you can start TensorBoard and pass the directory of the event data:
 
 ```console
-marie@compute$ tensorboard --logdir /scratch/ws/1/marie-tensorboard_logdata --bind_all
+marie@compute$ tensorboard --logdir /data/horse/ws/1/marie-tensorboard_logdata --bind_all
 [...]
 TensorBoard 2.3.0 at http://taurusi8034.taurus.hrsk.tu-dresden.de:6006/
 [...]
-- 
GitLab