From 7638d12363a84c3faaa8305192e0a5ed23c86410 Mon Sep 17 00:00:00 2001
From: Miroslav Kratochvil <miroslav.kratochvil@uni.lu>
Date: Wed, 14 Feb 2024 09:37:19 +0100
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)
---
external/exchange-channels/atlas-hpc/atlas-hpc.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/external/exchange-channels/atlas-hpc/atlas-hpc.md b/external/exchange-channels/atlas-hpc/atlas-hpc.md
index b1bad486..126aa9e6 100644
--- a/external/exchange-channels/atlas-hpc/atlas-hpc.md
+++ b/external/exchange-channels/atlas-hpc/atlas-hpc.md
@@ -37,6 +37,6 @@ Instead of transferring data between Atlas and UL HPC Clusters through the lapto
## 3. Via Large File Transfer (LFT)
An alternative solution is to use LFT for transferring data between Atlas and UL HPC Clusters. This method can reliably transfer large data volumes (typically several terabytes). However, LFT can only be used if the data is already on LFT (e.g., received from external collaborators). In this case, you can make a copy of the data and directly download it to the UL HPC Clusters for computational analysis. Note that a **master copy of the data must still be manually uploaded to Atlas** for internal archival.
-Please visit the dedicated [How-to Card on LFT]({{'/?exchange-channels:lft' | relative_url }}) to see further information.
+Please refer to the [dedicated How-to Card on LFT]({{'/?exchange-channels:lft' | relative_url }}) for detailed information.
> NOTE: LFT is only recommended for the use case mentioned above, where raw data were received via LFT. In other use cases, we recommend opting for method 1 or 2.
--
GitLab