From fd9725de582fb8f5e8c9b396793519e469e8d349 Mon Sep 17 00:00:00 2001
From: Kaan Cimir <kaan.cimir@uni.lu>
Date: Tue, 13 Feb 2024 14:27:25 +0100
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)

---
 external/exchange-channels/atlas-hpc/atlas-hpc.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/external/exchange-channels/atlas-hpc/atlas-hpc.md b/external/exchange-channels/atlas-hpc/atlas-hpc.md
index 3e3416e1..0c0b093e 100644
--- a/external/exchange-channels/atlas-hpc/atlas-hpc.md
+++ b/external/exchange-channels/atlas-hpc/atlas-hpc.md
@@ -11,6 +11,7 @@ redirect_from:
 
 # Data transfer between Atlas and UL HPC Clusters
 A recommended storage pattern is to have the master copy of data on Atlas (project folder) and to only store data on the UL HPC Clusters temporarily for the duration of computational analysis. All analysis performed on the UL HPC Clusters must therefore be regularly transferred to Atlas. This How-to Card describes the different methods to transfer data between Atlas and the UL HPC Clusters. The three recommended methods to transfer data are: 
+
 1. [Via laptop with ```scp``` or ```rsync```]()
 2. [Via dedicated Virtual Machine (VM)]()
 3. [Via Large File Transfer (LFT)]() 
-- 
GitLab