![]() ![]() The jobs we will submit to the queue are basically placeholder jobs that are asleep until the job starts running. In particular, FireWorks is completely unaware that you are running through a queue! This method is just like typing rlaunch into a Terminal window like in the core tutorials, except that now we are submitting a queue script that does the typing for us (it’s very low-tech!). In this method, the queue file runs rlaunch instead of running your desired program. Thus, many of the useful management and monitoring features of FireWorks will not be available to you.Ī more powerful way to execute jobs through a queue is presented in this tutorial. FireWorks will not know when the actual payload starts running, or is finished, or if the job finishes successfully. However, FireWorks then considers your “job” to only be queue submission, and will consider the job completed after the queue submission is complete. The simplest way to execute jobs through a queue would be to write a templated queue file and then submit it as a two-task Firework, as in the Firetask tutorial. Instead, you’ll submit Rockets through an existing queueing system that allocates computer resources. If your FireWorker is a large, shared resource (such as a computing cluster or supercomputing center), you probably won’t be able to launch Rockets directly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |