Update version number to 2.5.1

docs/Docker.md

@@ -9,7 +9,7 @@ than Docker, so you should read the guide for
 it on Windows, Mac, or Linux.
 
 There is a docker image on [Docker Hub](https://hub.docker.com/) named
-`wlandry/sdpb:2.4.0` containing binaries for `scalar_blocks`,
+`wlandry/sdpb:2.5.1` containing binaries for `scalar_blocks`,
 `pvm2sdp`, `sdp2input`, and `sdpb`.
 
 Suppose you have an input file `/my/project/input.xml`. To use this
@@ -27,7 +27,7 @@ place that docker will see it.
 
 `<image>` is the image name.
 
-        wlandry/sdpb:2.4.0
+        wlandry/sdpb:2.5.1
 
 `<command>` is the command that you would normally use to run the SDPB
 commands (see [Usage.md](Usage.md)).  The directory containing the
@@ -43,12 +43,12 @@ container.  To allow mpirun to run as root, we add the option
 can change that number to match your own machine.  Putting it all
 together on a single line
 
-    docker run -v /my/project/:/usr/local/share/sdpb wlandry/sdpb:2.4.0 mpirun --allow-run-as-root -n 4 pvm2sdp 1024 /usr/local/share/sdpb/input.xml /usr/local/share/sdpb/input
+    docker run -v /my/project/:/usr/local/share/sdpb wlandry/sdpb:2.5.1 mpirun --allow-run-as-root -n 4 pvm2sdp 1024 /usr/local/share/sdpb/input.xml /usr/local/share/sdpb/input
 
 Running this command will populate the directory `/my/project/input`.
 To search for primal-dual solutions
 
-    docker run -v /my/project/:/usr/local/share/sdpb wlandry/sdpb:2.4.0 mpirun --allow-run-as-root -n 4 sdpb --precision=1024 --procsPerNode=4 -s /usr/local/share/sdpb/input
+    docker run -v /my/project/:/usr/local/share/sdpb wlandry/sdpb:2.5.1 mpirun --allow-run-as-root -n 4 sdpb --precision=1024 --procsPerNode=4 -s /usr/local/share/sdpb/input
 
 The results will be in `/my/project/`.  Note that the files may be
 owned by root.

docs/SDPB-Manual.tex

@@ -38,7 +38,7 @@
 
 {\Large
 \begin{center}
-{\bf SDPB 2.4.0 \\\vspace{.1in}}
+{\bf SDPB 2.5.1 \\\vspace{.1in}}
 \end{center}
 }
 \begin{center}

docs/Singularity.md

@@ -23,27 +23,27 @@ and look for `singularity`.
 Once Singularity is installed, the next step is to download and
 convert the image
 
-    singularity pull docker://wlandry/sdpb:2.4.0
+    singularity pull docker://wlandry/sdpb:2.5.1
 
 Depending on your version of Singularity, this will create a file
-named `sdpb-2.4.0.simg` or `sdpb_2.4.0.sif`.
+named `sdpb-2.5.1.simg` or `sdpb_2.5.1.sif`.
 
 Singularity should automatically mount your home directory.  If your
-Singularity image is named `sdpb-2.4.0.simg`, you can invoke the SDPB
+Singularity image is named `sdpb-2.5.1.simg`, you can invoke the SDPB
 programs by prepending the command with
 
-    singularity exec sdpb-2.4.0.simg
+    singularity exec sdpb-2.5.1.simg
 
 So to convert the XML input file at `/home/user/input.xml`, run the command
 
-    singularity exec sdpb-2.4.0.simg mpirun -n 4 pvm2sdp 1024 /home/user/input.xml /home/user/input
+    singularity exec sdpb-2.5.1.simg mpirun -n 4 pvm2sdp 1024 /home/user/input.xml /home/user/input
 
 This uses 4 cores when running pvm2sdp.  You can change that number to
 match your own machine.
 
 To find a primal-dual solution, 
 
-    singularity exec sdpb-2.4.0.simg mpirun -n 4 sdpb --precision=1024 --procsPerNode=4 -s /home/user/input
+    singularity exec sdpb-2.5.1.simg mpirun -n 4 sdpb --precision=1024 --procsPerNode=4 -s /home/user/input
 
 In theory, Singularity can be used to run jobs across multiple nodes.
 We have not been able to make that work yet.  So for large, multi-node