Note: `git show <step_number>` is only useful if the previous step involved creating or modifying a file.
Note: `git show <step_number>` is only useful if the previous step involved creating or modifying a file.
### Example: how to jump to a specific section
### How to jump to a specific section
**Example**: You already know how to deploy IOCs and EPICS modules. You'd really like to skip to section 6 to learn more about asyn troubleshooting.
Do the following:
* Follow the [quickstart instructions](README.md#quickstart).
* Complete [step 2.1](2-IOC-deployment.md#21-clone-xxx) to clone xxx.
* Complete [step 2.2](2-IOC-deployment.md#22-confirm-the-directories-exist) to cd into the IOC's directory
* Complete [step 2.3](2-IOC-deployment.md#23-choose-a-new-ioc-prefix) override the default prefix
* Complete [step 4.1](4-Deploy-motorVMC.md#41-clone-motorvmc) to clone motorVMC
* Complete [step 4.2](4-Deploy-motorVMC.md#42-confirm-directories-exist) to cd into the motorVMC directory
* Run `git checkout 6.1` to update motorVMC for step 6.1.
* Run `make` to build motorVMC. The build should succeed.
* Run `cd ${IOC_DIR}/xxx` to go back to the IOC's directory.
* Run `git checkout 6.1` to update the IOC for step 6.1.
* Run `make` to build the IOC. The build should succeed.
* Complete [step 5.10.2](5-Add-virtual-motors.md#5102-start-serverypy-in-a-different-terminal-window) to start the virtual motor controller
* Proceed to [step 6.1](6-asyn-troubleshooting.md#61-start-the-ioc)
Note: You won't have a motor screen open because you skipped [step 3.4](3-Add-simulated-motors.md#34-launch-motor-screen) and there will be autosave errors when the IOC first runs saying **.sav** and **.savB** files are not found.
