ParameterSweepDocumentation - Revision history

Gwillford: /* Running a parameter sweep on Beocat */

2020-05-14T19:58:45Z

Running a parameter sweep on Beocat

← Older revision		Revision as of 14:58, 14 May 2020
Line 19:		Line 19:
	# Otherwise, enter <code>no</code> and then the number of jobs you do want to run. Please note that this will just run the first jobs up to that number (ie if you enter 100 it will run the first 100 jobs).		# Otherwise, enter <code>no</code> and then the number of jobs you do want to run. Please note that this will just run the first jobs up to that number (ie if you enter 100 it will run the first 100 jobs).
	# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can. Please note if you interrupt the program, you will need to rerun it in order to schedule the jobs, as it only schedules them at the end of the program.		# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can. Please note if you interrupt the program, you will need to rerun it in order to schedule the jobs, as it only schedules them at the end of the program.
			# The first batch should be scheduled now that the program is done.
	# '''Note: Do not delete the file remaining_jobs.csv unless you want to stop your current parameter sweep! It is used for keeping track of which chunks we have already submitted.'''		# '''Note: Do not delete the file remaining_jobs.csv unless you want to stop your current parameter sweep! It is used for keeping track of which chunks we have already submitted.'''
	# Follow the [[ParameterSweepDocumentation#Run the next batch of jobs\|Run the next batch of jobs]] section below		# Follow the [[ParameterSweepDocumentation#Run the next batch of jobs\|Run the next batch of jobs]] section below
Line 29:		Line 30:
	# Otherwise, enter <code>no</code> and then the number of jobs you do want to run. (ie if you enter 100 it will run the first 100 jobs).		# Otherwise, enter <code>no</code> and then the number of jobs you do want to run. (ie if you enter 100 it will run the first 100 jobs).
	# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can. Please note if you interrupt the program, you will need to rerun it in order to schedule the jobs, as it only schedules them at the end of the program.		# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can. Please note if you interrupt the program, you will need to rerun it in order to schedule the jobs, as it only schedules them at the end of the program.
			# The first batch should be scheduled now that the program is done.
	# Complete any other operations you want to do and then exit the program.		# Complete any other operations you want to do and then exit the program.
	# '''Note: Do not delete the file remaining_jobs.csv unless you want to stop your current parameter sweep! It is used for keeping track of which chunks we have already submitted.'''		# '''Note: Do not delete the file remaining_jobs.csv unless you want to stop your current parameter sweep! It is used for keeping track of which chunks we have already submitted.'''

Gwillford at 20:45, 6 May 2020

2020-05-06T20:45:21Z

← Older revision		Revision as of 15:45, 6 May 2020
Line 129:		Line 129:
	# Enter <code>d</code> when prompted by the program		# Enter <code>d</code> when prompted by the program
	# When prompted, enter yes for whichever groups of files you'd like to delete		# When prompted, enter yes for whichever groups of files you'd like to delete

			== FAQs ==
			==== My jobs keep failing with a '''TIMEOUT''' error. What do I do? ====
			You need to lengthen the time specified in '''run.sh'''.
			Currently, the job is limited to thirty minutes, as specified by the line:<br>
			'''<code>#SBATCH --time=30:00</code>'''<br>
			If I wanted to extend it to an hour, I would change it to<br>
			'''<code>#SBATCH --time=1:00:00</code>'''<br>
			It is good to try to keep this number as low as you can while still having the code finish in time, as it is easier for Beocat to schedule.<br>
			More information can also be found under the '''<code>--time</code>''' section here: https://slurm.schedmd.com/sbatch.html

	== Link to the project ==		== Link to the project ==
	https://github.com/gwillford1/CIS-598-Project-Repository		https://github.com/gwillford1/CIS-598-Project-Repository

Gwillford at 18:13, 6 May 2020

2020-05-06T18:13:08Z

← Older revision		Revision as of 13:13, 6 May 2020
Line 79:		Line 79:
	# Add the parameter as an input parameter for the <code>__init__</code> function, by adding it in a line like the others to the big list of parameters shown partially above. For example, I'd add something like <code>fr_mod=7000</code>		# Add the parameter as an input parameter for the <code>__init__</code> function, by adding it in a line like the others to the big list of parameters shown partially above. For example, I'd add something like <code>fr_mod=7000</code>
	# Next, add the parameter as a class member in the function by adding a statement such as <code>self.param_name = param_name</code> in the function (like the other members already there, one is shown below) [[File:Class mem.png]]		# Next, add the parameter as a class member in the function by adding a statement such as <code>self.param_name = param_name</code> in the function (like the other members already there, one is shown below) [[File:Class mem.png]]
			# NOTE: If there is already a line with '''<code>self.param_name = ...</code>''' at the bottom of the function (under the header '''<code>Set all remaining inputs to defaults/input parameters</code>'''), you should remove that now, as you are adding a new one instead.
	# For example, <code>self.fr_mod = fr_mod</code>. '''Note, it is crucial to remember the <code>self</code> prefix on that! If you forget it, the parameter won’t be written to the input file.'''		# For example, <code>self.fr_mod = fr_mod</code>. '''Note, it is crucial to remember the <code>self</code> prefix on that! If you forget it, the parameter won’t be written to the input file.'''
	# The program should automatically be able to include the new parameter in the input file now.		# The program should automatically be able to include the new parameter in the input file now.

Gwillford at 18:52, 4 May 2020

2020-05-04T18:52:34Z

Gwillford at 20:35, 28 April 2020

2020-04-28T20:35:19Z

← Older revision		Revision as of 15:35, 28 April 2020
Line 1:		Line 1:

	== Setting up Beocat to run a parameter sweep ==		== Setting up Beocat to run a parameter sweep ==
	# First, you need to copy the project with all of its files into Beocat.		# First, you need to copy the project with all of its files into Beocat.
Line 128:		Line 127:
	# Enter <code>d</code> when prompted by the program		# Enter <code>d</code> when prompted by the program
	# When prompted, enter yes for whichever groups of files you'd like to delete		# When prompted, enter yes for whichever groups of files you'd like to delete

			== Link to the project ==
			https://github.com/gwillford1/CIS-598-Project-Repository

Gwillford: finished up initial upload of documentation

2020-04-28T20:27:50Z

finished up initial upload of documentation

← Older revision		Revision as of 15:27, 28 April 2020
Line 87:		Line 87:
	# Go to the '''<code>Define parameter sweep ranges</code>''' section of '''<code>Parameter_Sweep_P.py</code>''', the beginning of which is shown below [[File:Def ranges.png]]		# Go to the '''<code>Define parameter sweep ranges</code>''' section of '''<code>Parameter_Sweep_P.py</code>''', the beginning of which is shown below [[File:Def ranges.png]]
	# Add the range of the parameter you want in the file in the same style as the previous ranges, calling it '''<code><parameter_name>_RANGE</code>'''. For example, if I want to add the parameter Bearing to range from 5 to 10 with intervals of 1, I would add the following line: '''<code>BEARING_RANGE = [5, 6, 7, 8, 9, 10]</code>'''		# Add the range of the parameter you want in the file in the same style as the previous ranges, calling it '''<code><parameter_name>_RANGE</code>'''. For example, if I want to add the parameter Bearing to range from 5 to 10 with intervals of 1, I would add the following line: '''<code>BEARING_RANGE = [5, 6, 7, 8, 9, 10]</code>'''
	# Update the function '''<code>generate_files</code>''' to use this new range as well by adding a for loop for it. For example, I’d update what is already there (shown below)~~:[[File:For loops.png]]~~		# Update the function '''<code>generate_files</code>''' to use this new range as well by adding a for loop for it. For example, I’d update what is already there (shown below) to include a new for loop for my new range too on the innermost level, such as '''<code>for bearing in BEARING_RANGE:</code>'''[[File:For loops.png]]
	# to include a new for loop for my new range too on the innermost level, such as '''<code>for bearing in BEARING_RANGE:</code>'''
	# Pass the new variable into the '''<code>input_data.InputData</code>''' call shown below. For example, I’d add the following to the parameters that are already there: '''<code>bearing=bearing,</code>''' if bearing was a new parameter I added above. [[File:Create input data.png]]		# Pass the new variable into the '''<code>input_data.InputData</code>''' call shown below. For example, I’d add the following to the parameters that are already there: '''<code>bearing=bearing,</code>''' if bearing was a new parameter I added above. [[File:Create input data.png]]
	# Add to the num_jobs calculation to include the new range (shown below). You should multiply what is already there by the len of your new range (by doing something like '''<code>len(BEARING_RANGE)</code>''').[[File:Num jobs calc.png]]		# Add to the num_jobs calculation to include the new range (shown below). You should multiply what is already there by the len of your new range (by doing something like '''<code>len(BEARING_RANGE)</code>''').[[File:Num jobs calc.png]]

Gwillford at 20:26, 28 April 2020

2020-04-28T20:26:26Z

← Older revision		Revision as of 15:26, 28 April 2020
Line 85:		Line 85:

	=== Step 2: Add the range of the parameter to Parameter_Sweep_P.py ===		=== Step 2: Add the range of the parameter to Parameter_Sweep_P.py ===
			# Go to the '''<code>Define parameter sweep ranges</code>''' section of '''<code>Parameter_Sweep_P.py</code>''', the beginning of which is shown below [[File:Def ranges.png]]
			# Add the range of the parameter you want in the file in the same style as the previous ranges, calling it '''<code><parameter_name>_RANGE</code>'''. For example, if I want to add the parameter Bearing to range from 5 to 10 with intervals of 1, I would add the following line: '''<code>BEARING_RANGE = [5, 6, 7, 8, 9, 10]</code>'''
			# Update the function '''<code>generate_files</code>''' to use this new range as well by adding a for loop for it. For example, I’d update what is already there (shown below):[[File:For loops.png]]
			# to include a new for loop for my new range too on the innermost level, such as '''<code>for bearing in BEARING_RANGE:</code>'''
			# Pass the new variable into the '''<code>input_data.InputData</code>''' call shown below. For example, I’d add the following to the parameters that are already there: '''<code>bearing=bearing,</code>''' if bearing was a new parameter I added above. [[File:Create input data.png]]
			# Add to the num_jobs calculation to include the new range (shown below). You should multiply what is already there by the len of your new range (by doing something like '''<code>len(BEARING_RANGE)</code>''').[[File:Num jobs calc.png]]

			=== Step 3: Update Input_P.py to read this new parameter and the code to use it ===
			# Add to the other calls to read this new parameter from the input.
			# Add a line to '''<code>write_params</code>''' like the others to write this new parameter to the results file as well.

	== Using the output sorting program ==		== Using the output sorting program ==

Gwillford at 20:10, 28 April 2020

2020-04-28T20:10:13Z

← Older revision		Revision as of 15:10, 28 April 2020
Line 5:		Line 5:
	# If you want to name it differently, you need to update run.sh to have the path to the new folder on line 15, where it has the command <code>python ~/proj/Main_P.py</code>		# If you want to name it differently, you need to update run.sh to have the path to the new folder on line 15, where it has the command <code>python ~/proj/Main_P.py</code>
	# The project folders should be structured correctly if you kept them as given, but make sure that the project is structured as follows: '''proj''' folder containing: all '''python''' and '''.sh''' files, a '''references''' folder containing '''ASTMA1096.txt''', '''wireproperties.txt''', and a '''geo_points''' folder containing all geometric point files		# The project folders should be structured correctly if you kept them as given, but make sure that the project is structured as follows: '''proj''' folder containing: all '''python''' and '''.sh''' files, a '''references''' folder containing '''ASTMA1096.txt''', '''wireproperties.txt''', and a '''geo_points''' folder containing all geometric point files
	# Make all '''.sh''' files in your '''proj''' folder executable, using the command '''chmod +x *.sh''' in your '''proj''' folder. This should make '''.sh''' files appear in green now, as shown below (note that not all files are shown) [[File:Cropped executable sh file.png~~\|frameless~~]]		# Make all '''.sh''' files in your '''proj''' folder executable, using the command '''chmod +x *.sh''' in your '''proj''' folder. This should make '''.sh''' files appear in green now, as shown below (note that not all files are shown) [[File:Cropped executable sh file.png]]
	# Set up Beocat to run the Python files.		# Set up Beocat to run the Python files.
	# You can run the '''set_up_beocat.sh''' file to do this automatically. Run it by going to the folder that the file is in and entering the command <code>./set_up_beocat.sh</code>		# You can run the '''set_up_beocat.sh''' file to do this automatically. Run it by going to the folder that the file is in and entering the command <code>./set_up_beocat.sh</code>
Line 68:		Line 68:
	# Run the parameter sweep, the updated range will be used to generate files.		# Run the parameter sweep, the updated range will be used to generate files.

			== Adding new parameters to the parameter sweep ==
			Adding parameters to the sweep is a fairly involved process, but it should be simple if you make sure to complete the steps below.
			Please do also note that adding any parameters dramatically increases the number of combinations of inputs that are created, so you should think about reducing the ranges of other parameters when adding your own to avoid needing to do a ridiculous number of different combinations (at the time of writing this, there are already over 300,000 combinations, which is a very large number of simulations to run, even for Beocat.

			=== Step 1: Add the parameter as a member of the <code>InputData</code> class in <code>Input_Data_P.py</code> ===
			Before you do this, if you don’t know what Python classes are, I’d strongly recommend reading the Python documentation for classes (can be found at https://docs.python.org/2/tutorial/classes.html).

			==== If the parameter is not already being passed in to the <code>__init__</code> function, part of which is shown below, do the following steps: ====
			[[File:Init.png]]
			# Add the parameter as an input parameter for the <code>__init__</code> function, by adding it in a line like the others to the big list of parameters shown partially above. For example, I'd add something like <code>fr_mod=7000</code>
			# Next, add the parameter as a class member in the function by adding a statement such as <code>self.param_name = param_name</code> in the function (like the other members already there, one is shown below) [[File:Class mem.png]]
			# For example, <code>self.fr_mod = fr_mod</code>. '''Note, it is crucial to remember the <code>self</code> prefix on that! If you forget it, the parameter won’t be written to the input file.'''
			# The program should automatically be able to include the new parameter in the input file now.
			==== If the parameter ''is'' already being passed into the function, do the following steps if necessary ====
			# If you need to change a parameter to use a new formula, for example, find the line that is self.param = param and update it to use the new equation. For example, Ec and Eci use an equation like below: [[File:Equation.png]]

			=== Step 2: Add the range of the parameter to Parameter_Sweep_P.py ===

	== Using the output sorting program ==		== Using the output sorting program ==

Gwillford at 19:55, 28 April 2020

2020-04-28T19:55:24Z

← Older revision		Revision as of 14:55, 28 April 2020
Line 67:		Line 67:
	# Copy the file to Beocat (if you edited it locally).		# Copy the file to Beocat (if you edited it locally).
	# Run the parameter sweep, the updated range will be used to generate files.		# Run the parameter sweep, the updated range will be used to generate files.



			== Using the output sorting program ==
			This program allows you to search for results that match your entered parameter values and save them to a new '''.csv''' file that you specify.

			==== Option 1: run directly ====
			# Log into Beocat and navigate to your '''proj''' folder
			# Run the following command to run the script to search for results directly: <code>./sort_output.sh</code>
			# When prompted, enter the parameters you are searching as <code>name1=value1 name2=value2 name3=value3 etc</code>, separated by spaces.
			# For example, to search for WA wire type, fps of 213, and fc of 6000 I’d enter the following: <code>W_type=WA fps=213 fc=6000</code>
			# Enter the name of the file you’d like results saved to when prompted.
			# Repeat if you’d like to do other searches, otherwise end the program.

			==== Option 2: run through the manager application ====
			# Log into Beocat and navigate to your '''proj''' folder
			# Run the following command to run the manager program: <code>./manage_jobs.sh</code>
			# Enter <code>o</code> when prompted by the program
			# When prompted, enter the parameters you are searching as <code>name1=value1 name2=value2 name3=value3 etc</code>, separated by spaces.
			# For example, to search for WA wire type, fps of 213, and fc of 6000 I’d enter the following: <code>W_type=WA fps=213 fc=6000</code>
			# Enter the name of the file you’d like results saved to when prompted.
			# Repeat if you’d like to do other searches, otherwise end the program.

			== Deleting all input or output files ==
			Due to the very large number of input and output files this generates, there is also a simple program to delete the remaining files.

			==== Option 1: run directly ====
			# Log into Beocat and navigate to your '''proj''' folder
			# Run the following command to run the script to delete the files directly: <code>./delete_files.sh</code>
			# When prompted, enter yes for whichever groups of files you'd like to delete

			==== Option 2: run through the manager application ====
			# Log into Beocat and navigate to your '''proj''' folder
			# Run the following command to run the manager program: <code>./manage_jobs.sh</code>
			# Enter <code>d</code> when prompted by the program
			# When prompted, enter yes for whichever groups of files you'd like to delete

Gwillford at 21:58, 27 April 2020

2020-04-27T21:58:54Z

← Older revision		Revision as of 16:58, 27 April 2020
Line 63:		Line 63:
	== Changing the range of a parameter in the sweep ==		== Changing the range of a parameter in the sweep ==
	If you need to change the range of a parameter in the sweep, the process should be simple.		If you need to change the range of a parameter in the sweep, the process should be simple.
	# Go to the <code>Define parameter sweep ranges</code> section of <code>Parameter_Sweep_P.py</code>, some of which is shown below.		# Go to the <code>Define parameter sweep ranges</code> section of <code>Parameter_Sweep_P.py</code>, some of which is shown below. [[File:Param sweep ranges.png\|824×238px\|]]
	[[File:Param sweep ranges.png\|824×238px\|]]

	# Edit the range of the parameter you want in the file and save it. For example, if I want FC to range from 5500 to 7500 instead of 6000 to 10000, I would change it to be <code>FC_RANGE = [5500, 6000, 65000, 7000, 7500]</code>		# Edit the range of the parameter you want in the file and save it. For example, if I want FC to range from 5500 to 7500 instead of 6000 to 10000, I would change it to be <code>FC_RANGE = [5500, 6000, 65000, 7000, 7500]</code>
	# Copy the file to Beocat (if you edited it locally).		# Copy the file to Beocat (if you edited it locally).
	# Run the parameter sweep, the updated range will be used to generate files.		# Run the parameter sweep, the updated range will be used to generate files.

← Older revision		Revision as of 13:52, 4 May 2020
Line 4:		Line 4:
	# If you want to name it differently, you need to update run.sh to have the path to the new folder on line 15, where it has the command <code>python ~/proj/Main_P.py</code>		# If you want to name it differently, you need to update run.sh to have the path to the new folder on line 15, where it has the command <code>python ~/proj/Main_P.py</code>
	# The project folders should be structured correctly if you kept them as given, but make sure that the project is structured as follows: '''proj''' folder containing: all '''python''' and '''.sh''' files, a '''references''' folder containing '''ASTMA1096.txt''', '''wireproperties.txt''', and a '''geo_points''' folder containing all geometric point files		# The project folders should be structured correctly if you kept them as given, but make sure that the project is structured as follows: '''proj''' folder containing: all '''python''' and '''.sh''' files, a '''references''' folder containing '''ASTMA1096.txt''', '''wireproperties.txt''', and a '''geo_points''' folder containing all geometric point files
			# Navigate into your '''proj''' folder using the command <code>cd proj</code>. Additionally, if you are unfamiliar with using Linux, I would recommend reading this page on Linux basics: https://support.beocat.ksu.edu/BeocatDocs/index.php?title=LinuxBasics
	# Make all '''.sh''' files in your '''proj''' folder executable, using the command '''chmod +x *.sh''' in your '''proj''' folder. This should make '''.sh''' files appear in green now, as shown below (note that not all files are shown) [[File:Cropped executable sh file.png]]		# Make all '''.sh''' files in your '''proj''' folder executable, using the command '''chmod +x *.sh''' in your '''proj''' folder. This should make '''.sh''' files appear in green now, as shown below (note that not all files are shown) [[File:Cropped executable sh file.png]]
	# Set up Beocat to run the Python files.		# Set up Beocat to run the Python files.
Line 16:		Line 17:
	# Run the following command to run the parameter sweep script by itself: <code>./sched_run.sh</code>		# Run the following command to run the parameter sweep script by itself: <code>./sched_run.sh</code>
	# If you’d like to run a whole parameter sweep: enter <code>yes</code> when prompted		# If you’d like to run a whole parameter sweep: enter <code>yes</code> when prompted
	# Otherwise, enter <code>no</code> and then the number of jobs you do want to run		# Otherwise, enter <code>no</code> and then the number of jobs you do want to run. Please note that this will just run the first jobs up to that number (ie if you enter 100 it will run the first 100 jobs).
	# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can.		# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can. Please note if you interrupt the program, you will need to rerun it in order to schedule the jobs, as it only schedules them at the end of the program.
	# '''Note: Do not delete the file remaining_jobs.csv unless you want to stop your current parameter sweep! It is used for keeping track of which chunks we have already submitted.'''		# '''Note: Do not delete the file remaining_jobs.csv unless you want to stop your current parameter sweep! It is used for keeping track of which chunks we have already submitted.'''
	# Follow the [[ParameterSweepDocumentation#Run the next batch of jobs\|Run the next batch of jobs]] section below		# Follow the [[ParameterSweepDocumentation#Run the next batch of jobs\|Run the next batch of jobs]] section below
Line 26:		Line 27:
	# Enter s when prompted by the program		# Enter s when prompted by the program
	# If you’d like to run a whole parameter sweep: enter yes when prompted		# If you’d like to run a whole parameter sweep: enter yes when prompted
	# Otherwise, enter no and then the number of jobs you do want to run		# Otherwise, enter <code>no</code> and then the number of jobs you do want to run. (ie if you enter 100 it will run the first 100 jobs).
	# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can.		# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can. Please note if you interrupt the program, you will need to rerun it in order to schedule the jobs, as it only schedules them at the end of the program.
	# Complete any other operations you want to do and then exit the program.		# Complete any other operations you want to do and then exit the program.
	# '''Note: Do not delete the file remaining_jobs.csv unless you want to stop your current parameter sweep! It is used for keeping track of which chunks we have already submitted.'''		# '''Note: Do not delete the file remaining_jobs.csv unless you want to stop your current parameter sweep! It is used for keeping track of which chunks we have already submitted.'''
Line 61:		Line 62:

	== Changing the range of a parameter in the sweep ==		== Changing the range of a parameter in the sweep ==
	If you need to change the range of a parameter in the sweep, the process should be simple.		If you need to change the range of a parameter in the sweep, the process should be simple. Please do also note that increasing the range of a parameter dramatically increases the number of combinations of inputs that are created, so you should think about reducing the ranges of other parameters when adding your own to avoid needing to do a ridiculous number of different combinations (at the time of writing this, there are already over 300,000 combinations, which is a very large number of simulations to run, even for Beocat.
	# Go to the <code>Define parameter sweep ranges</code> section of <code>Parameter_Sweep_P.py</code>, some of which is shown below. [[File:Param sweep ranges.png\|824×238px\|]]		# Go to the <code>Define parameter sweep ranges</code> section of <code>Parameter_Sweep_P.py</code>, some of which is shown below. [[File:Param sweep ranges.png\|824×238px\|]]
	# Edit the range of the parameter you want in the file and save it. For example, if I want FC to range from 5500 to 7500 instead of 6000 to 10000, I would change it to be <code>FC_RANGE = [5500, 6000, 65000, 7000, 7500]</code>		# Edit the range of the parameter you want in the file and save it. For example, if I want FC to range from 5500 to 7500 instead of 6000 to 10000, I would change it to be <code>FC_RANGE = [5500, 6000, 65000, 7000, 7500]</code>
	# Copy the file to Beocat (if you edited it locally).		# Copy the file to Beocat (if you edited it locally). Please note that if you changed the file name, you will need to update the '''<code>import Parameter_Sweep_P</code>''' statement in '''Manager_P.py'''
	# Run the parameter sweep, the updated range will be used to generate files.		# Run the parameter sweep, the updated range will be used to generate files.

Line 100:		Line 101:
	# Log into Beocat and navigate to your '''proj''' folder		# Log into Beocat and navigate to your '''proj''' folder
	# Run the following command to run the script to search for results directly: <code>./sort_output.sh</code>		# Run the following command to run the script to search for results directly: <code>./sort_output.sh</code>
	# When prompted, enter the parameters you are searching as <code>name1=value1 name2=value2 name3=value3 etc</code>, separated by spaces.		# When prompted, enter the parameters you are searching as <code>name1=value1 name2=value2 name3=value3 etc</code>, separated by spaces. There is not a limit on the number of parameters you use to search. Please do note, however, that the only parameters you will be able to search are those that are written in the first line of the results file.
	# For example, to search for WA wire type, fps of 213, and fc of 6000 I’d enter the following: <code>W_type=WA fps=213 fc=6000</code>		# For example, to search for WA wire type, fps of 213, and fc of 6000 I’d enter the following: <code>W_type=WA fps=213 fc=6000</code>
	# Enter the name of the file you’d like results saved to when prompted.		# Enter the name of the file you’d like results saved to when prompted.
Line 109:		Line 110:
	# Run the following command to run the manager program: <code>./manage_jobs.sh</code>		# Run the following command to run the manager program: <code>./manage_jobs.sh</code>
	# Enter <code>o</code> when prompted by the program		# Enter <code>o</code> when prompted by the program
	# When prompted, enter the parameters you are searching as <code>name1=value1 name2=value2 name3=value3 etc</code>, separated by spaces.		# When prompted, enter the parameters you are searching as <code>name1=value1 name2=value2 name3=value3 etc</code>, separated by spaces. There is not a limit on the number of parameters you use to search. Please do note, however, that the only parameters you will be able to search are those that are written in the first line of the results file.
	# For example, to search for WA wire type, fps of 213, and fc of 6000 I’d enter the following: <code>W_type=WA fps=213 fc=6000</code>		# For example, to search for WA wire type, fps of 213, and fc of 6000 I’d enter the following: <code>W_type=WA fps=213 fc=6000</code>
	# Enter the name of the file you’d like results saved to when prompted.		# Enter the name of the file you’d like results saved to when prompted.