Winmostar Job Manager (Winmostar/JM) is job management software for multi-core Windows PC.
We can automatically schedule the execution of various solvers such as GAMESS, Gaussian etc. on PC ( local machine ) which works as an auxiliary program of Winmostar and has Winmostar installed.
6.34.1. Basic actions
In Winmostar, if you choose to execute a job (called local job) on the local machine, the JM window as shown below will be launched and registered in the first queue. :guilabel: Status of the queued job is first WAIT (queued for execution), in order of registration, Priority, sequential considering the number of executed cores RUN, and the job is started. The Status of the job that has finished processing switches to END.
JM is automatically started when executing a local job with Winmostar, but it does not end automatically, so if you want to exit it is the
x (close) button It ends from. When you exit JM, the following jobs in the: guilabel: WAIT state will not start.
If you want to start JM at an arbitrary timing such as stopping JM by mistake, click
on the Winmostar main unit.
MaxCores is the maximum number of cores that JM can use and defaults to the number of cores of the machine. While this value is large, many jobs are executed in parallel, but setting it more than the number of cores on the local machine does not improve efficiency.
If you start the Windows Task Manager and go to the Performance tab, the number of cores of your machine will be displayed in the Number of logical processors field.
Jobs are basically executed in the order of old jobs in the WAIT state, but you can adjust their order by changing Priority. Priority has a lower value job execution with higher priority.
The number of executed cores is set to the value set by the keyword of the solver to be used. For example, the value of %nproc= for G03W, and the value of NCPUS for GAMESS. G03W requires a parallel calculation version, and there is a limit of up to 4 cores.
JM has been adjusted not to start twice, and if you start Winmostar multiple times, the job will be registered for one JM.
JM can manage up to 200 jobs (queues) . If exceeded, old queues are deleted. Even if the running job is deleted from the queue, the job processing itself will continue.
For MOPAC, you can select whether to use JM in the Preferences of Winmostar itself. If you do not use JM, calculation results are automatically loaded into Winmostar's main window after MOPAC calculation, but if you use JM, the user must explicitly load the calculation result on Winmostar after the job is finished .
6.34.2. How to forcibly terminate/cancel a job
If you want to forcibly terminate the job in RUN state (running), press the
x (close) button in the job's prompt (DOS) window. On JM you can also finish by clicking on the line of the job in the guilabel: run state and changing the Status to END, but in some solvers such as MOPAC 2009 That operation does not work.
In JM, click on the row of the job in RUN state, the DOS window for that job will be displayed in the foreground.
If you want to cancel the job in the WAIT state, select the line of that job with JM and press or keyboard Delete key. If you do not want to execute it without deleting it from the queue, change Status from WAIT to END.