From 343e539366e945fe6978ca107f412d3131d63ae5 Mon Sep 17 00:00:00 2001
From: Benjamin Pachev <benjaminpachev@gmail.com>
Date: Fri, 13 Aug 2021 13:39:40 -0600
Subject: [PATCH] Update CONTAINER-README.md

As currently presented in the README, the commands for testing Singularity containers use an input file that still has the GMT/GhostScript paths set. This means that people who try to run the commands in the README will get confusing errors. Changing the input file in the sample commands fixes that.
---
 CONTAINER-README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/CONTAINER-README.md b/CONTAINER-README.md
index e986a61..83b793c 100644
--- a/CONTAINER-README.md
+++ b/CONTAINER-README.md
@@ -66,19 +66,19 @@ command (for example):
 
 ##### MPI Example
 ```bash
-singularity exec <path to figuregen.sif> mpirun -np <num processes> figuregen -I ../Tests/BathyFilledCPT.inp
+singularity exec <path to figuregen.sif> mpirun -np <num processes> figuregen -I ../docker-test/BathyFilledCPT.inp
 ```
 
 ##### Serial Example
 
 ```bash
-singularity exec <path to figuregen-serial.sif> figuregen -I ../Tests/BathyFilledCPT.inp
+singularity exec <path to figuregen-serial.sif> figuregen -I ../docker-test/BathyFilledCPT.inp
 ```
 
 ##### TACC/HPC Example (e.g. on Stampede2. DO NOT RUN ON LOGIN NODE.)
 
 ```bash
-ibrun singularity exec <path to figuregen-tacc.sif> figuregen -I ../Tests/BathyFilledCPT.inp
+ibrun singularity exec <path to figuregen-tacc.sif> figuregen -I ../docker-test/BathyFilledCPT.inp
 ```
 
 **Note:** The TACC container gives some harmless errors that can be safely ignored.