Editing Tutorial (section)

===Additional SCons commands===
Here are some additional SCons commands that are useful to know.
====Viewing Plots====
If you're running an SConstruct and want to view the plots that it generates as it creates them, then you can use: '''scons view'''  to force SCons to show the plots interactively.  Doing so allows you to view your output at runtime and to stop the SConstruct as it's running if you don't like what you see.
====Viewing only one plot====
If you want to view the plot associated with only a single file you can tell SCons to view that plot by using the command: '''scons file.view'''  where file is the filename of the item that you want to view.  For example: scons spike.view would show the plot of the spike.rsf file.  The advantage to using this command is that SCons will only build the dependencies needed to view that specific plot, which can save you a lot of time in longer processing scripts.
====Building specific targets====
If you want to build a specific RSF file, or a few specific RSF files you can simply specify them on the command line when you execute SCons as follows: '''scons file.rsf file2.rsf file3.rsf ...''' .  The advantage to doing this, is that SCons will only build those files and their dependencies instead of running through the entire script.
====Cleaning up====
After we've executed our SConstruct and viewed the results of the processings flow, we might decide that we want to clean up our project and go work on something else.  Normally, one would have to delete all of the files and then move on, but SCons automates this process using the command: '''scons -c''' .  Simply execute it in the local directory and SCons will remove all of the built RSF files, and VPLOT files.  SCons will not remove files that it does not have rules for.
====Dry-runs====
Sometimes we want to test an SConstruct through the end of the script without waiting for it to run completely.  To do so, we can use '''scons -n'''  which tells SCons to simulate an actual execution. During a dry-run SCons will check all of the commands, and dependencies to ensure that they exist and are properly configured.  If not, then SCons will tell you which commands are misconfigured.  This command can save you hours of debugging!  Use it liberally.
====Parallel executions====
For long scripts we can use parallel execution to run multiple processing commands at the same time.  Parallel execution requires that the commands can function independently of one another (i.e. there are commands that do not depend on each other's output).  To use parallel execution use: '''pscons'''  which launches the maximum number of parallel jobs that your computer can handle at once.  Parallel execution can greatly speed up your processing flows if SCons can parallelize it.  In the worst case, SCons won't be able to parallelize your script and it will run at the same speed as if you just used '''scons'''.