3/1/2024 0 Comments Firetask instalBasic example ¶īelow is an example of how to use FireWorks at NERSC. This file should be located in the directory where you are issuing FireWorks commands. This information will go into a file named "my_launchpad.yaml". e.g., for MongoDB Atlas this is sometimes 'admin'.:Ĭonfiguration written to my_launchpad.yaml! Database used for authentication, if not connection db. Path to any client certificate to be used for Mongodb connection:Įnter authsource parameter. Password for MongoDB authentication: my_passwordĮnter ssl_ca_file parameter. Username for MongoDB authentication: my_db_adminĮnter password parameter. Database under which to store the fireworks collections: my_dbĮnter username parameter. Example: 'localhost' or 'mongodb+srv://': Įnter port parameter. (press Enter if you want to accept the defaults )Įnter host parameter. Please supply the following configuration values Note you'll want to use the address to your mongoDB database, your database name, your administrator database name, and the password you were provided. You can follow the steps in our example below. Make sure you have initialized your FireWorks environment, for example via conda activate fireworks. In this example, we are working from $HOME/fw_test. On a login node, navigate to the directory where you will issue your fireworks commands. You will need to specify the name of the database host and your own username and password - note that you need to have admin access to the database, so make sure you use the administrators username/password with which you were provided. Setting up the Launchpad can be done interactively using the command lpad init, similar to the example shown below. Setting up your LaunchPad for Perlmutter ¶ Mamba install -c conda-forge fireworks pytestįor more information about using conda environments at NERSC, check out this page. Create a new conda environment for FireWorksĬonda create -n fireworks python = 3.9 -y We recommend that anyone wanting to use FireWorks at NERSC install it in a conda environment. Could be run on a separate machine (FireWorker) or through a batch system (in this case, SLURM). Rocket: fetches a FireWork from the LaunchPad and runs it.FireTask: computing tasks to be performed.It contains all the tasks to be run, and whether they have run successfully etc. LaunchPad/FireServer: MongoDB that controls the workflow.Terminology ¶įireWorks uses a number of terms to describe the different parts of the workflow manager: If you need more help with FireWorks itself please open a separate ticket with NERSC consulting at. Please note that we don't provide database backups, so we encourage all FireWorks users who depend on the information stored in their MongoDB databases to manage their own periodic backups. Please use the database creation form to request your mongoDB database. To use FireWorks you must first request a mongoDB database. You can find more information in the official FireWorks documentation. We will cover using FireWorks via bash shell here. It can be used via bash scripting or via a Python API. It can handle complex job dependencies, restart jobs that have died, and track the workflow status on a friendly dashboard. Running jobs with different resource requirements can be trickyįireWorks uses a centralized server model where the server manages the workflows and workers run the jobs.Requires a mongoDB database which must be set up by NERSC staff.Friendly dashboard to display workflow status.Can run tasks on CPU or GPU (GPU example below).Well-suited to high throughput use-cases.Can handle tasks that contain MPI (example below).Works well at NERSC and can integrate with Slurm.FireWorks is a free, open-source code for defining, managing, and executing complex scientific workflows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |