From Beocat
(Updating for code snippets) |
|||
Line 14: | Line 14: | ||
# 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> | ||
# If set_up_beocat.sh doesn’t work, what you need to do is create a ‘virtual environment’ for running python. You can look at [[https://support.beocat.ksu.edu/BeocatDocs/index.php/Installed_software#Python|this help page]] to see a different guide for doing so, but you can also look at the commands in '''set_up_beocat.sh''' to see an example of setting up the virtual environment. | # If set_up_beocat.sh doesn’t work, what you need to do is create a ‘virtual environment’ for running python. You can look at [[https://support.beocat.ksu.edu/BeocatDocs/index.php/Installed_software#Python|this help page]] to see a different guide for doing so, but you can also look at the commands in '''set_up_beocat.sh''' to see an example of setting up the virtual environment. | ||
=== Running a parameter sweep on Beocat === | |||
There are two ways to schedule the parameter sweep: directly or through the manager application. | |||
==== Option 1: run directly ==== | |||
# Log into Beocat and navigate to your '''proj''' folder | |||
# 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 | |||
# Otherwise, enter <code>no</code> and then the number of jobs you do want to run | |||
# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can. | |||
# '''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 | |||
==== 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 by itself: <code>./manager.sh</code> | |||
# Enter s when prompted by the program | |||
# 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 | |||
# Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can. | |||
# 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.''' | |||
# Follow the [[ParameterSweepDocumentation#Run the next batch of jobs|Run the next batch of jobs]] section below | |||
=== Run the next batch of jobs/Resubmit failed jobs === |
Revision as of 14:34, 27 April 2020
Parameter Sweep Documentation
Setting up Beocat to run a parameter sweep
- First, you need to copy the project with all of its files into Beocat.
- This can be done several ways, but make sure that you have them in the same folder, which needs to be named proj.
- 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
python ~/proj/Main_P.py
- 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)
- 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
./set_up_beocat.sh
- If set_up_beocat.sh doesn’t work, what you need to do is create a ‘virtual environment’ for running python. You can look at [help page] to see a different guide for doing so, but you can also look at the commands in set_up_beocat.sh to see an example of setting up the virtual environment.
Running a parameter sweep on Beocat
There are two ways to schedule the parameter sweep: directly or through the manager application.
Option 1: run directly
- Log into Beocat and navigate to your proj folder
- Run the following command to run the parameter sweep script by itself:
./sched_run.sh
- 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 - Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can.
- 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 Run the next batch of jobs section below
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 by itself:
./manager.sh
- Enter s when prompted by the program
- 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
- Wait for the program to finish, it will create all the input files and schedule as many jobs at once as it can.
- 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.
- Follow the Run the next batch of jobs section below