remove usage instructions from building instructions

Author: tomeichlersmith

src/developing/custom-production-image.md

@@ -1,13 +1,9 @@
-# Using a Custom Production Image
+# Building a Custom Production Image
 
 Using a container has many advantages and one of them is the ability to develop code on one machine (e.g. your personal laptop), 
 but the deploy the _exact same code_ to run on several other computers (e.g. SLAC batch computing).
-This page details a process you can follow to generate your own production image that has your developments of ldmx-sw inside of it and has two big parts.
-
-1. Building a custom production image with your developments
-2. Running any production image (with specific focus on using `singularity`).
-
-## 1. Building a Custom Production Image
+This page details a process you can follow to generate your own production image that has your developments of ldmx-sw inside of it.
+Refer to the [Batch Computing](../using/batch.md) for how to use these production images.
 
 Building a docker image is complicated, but hopefully you can get one of the two methods listed below to work for your specific case.
 The common denominator in these methods is that you *need* to have a DockerHub repository that you have administrator access to.
@@ -61,34 +57,3 @@ _Note: If you haven't yet, you may need to `docker login` on your computer for t
 ```
 docker push docker-user-name/docker-repo-name:some-tag
 ```
-
-## 2. Running the Production Image on the Batch Computer
-0. Decide where you want to save the production image: `export LDMX_PRODUCTION_IMG=$(pwd -P)/ldmx_my_production_image_some_tag.sif`
-1. Pull the docker container down from Docker Hub and build it into a `.sif` image file. _Note: This step requires your Docker Hub repository to be public._
-```
-singularity build ${LDMX_PRODUCTION_IMG} docker://docker-user-name/docker-repo-name:some-tag
-```
-2. Now you can run a configuration script with your developments in the container using
-```
-singularity run --no-home ${LDMX_PRODUCTION_IMG} . config.py
-```
-This is the command you want to be giving to `bsub` or some other submission program.
-The only files it needs access to are the configuration script that you want to run and the `.sif` image file;
-both of which are only used at the start-up of the container.
-
-_Note: On SLAC computers, the default singularity cache directory is $HOME, but SLAC users are not given very much space in $HOME. It may help your singularity build and run commands if you change the cache directory 'SINGULARITY_CACHEDIR' to somewhere with more space._
-
-## 3. Submission Script
-It is best practice to write a "submission script" that handles the running of this command _and_ any pre- or post- run actions.
-A lot of different submission scripts have been written in `bash` and `python`, but they all have a similar structure:
-1. Setup the batch environment (e.g. Find singularity image file and turn off email notifications)
-2. Configure or write a job script which does all the pre- and post- run actions as well as the `singularity run` command.
-   - Go to a scratch or temporary directory to work
-   - Pre-Run Actions: copying over input file, inserting parameters into configuration script, etc...
-   - Run `singularity run` command
-   - Post-Run Actions: copying output files to output directory cleaning up scractch directory
-3. Submit the job script using the submission program (e.g. `bsub` or `condor`) however many times
-
-The `batch` directory in the [LDMX-Software/ldmx-sw-scripts](https://github.com/LDMX-Software/ldmx-sw-scripts)
-repository offers some examples of these submission scripts, although they tend to be a little old
-and will need to be updated.