Submitting the Job
Resources
The submitted job will start running almost immediately.
CPU cycles and memory are dynamically shared with all other running jobs.
The resource allocation can be monitored
from the job status panel. This panel also allows one to
cancel a running job. In order to protect
anonymity, the first four letters
of the jobname are masked in the job status display. To kill a job, one would
need to know the full name.
The memory requirement is not very intensive for BPM.
Most realistic structures can be run without exceeding the memory
limits of the computer.
Manual Sync
This option really should not be necessary under normal circumstances
because the files are frequently synchronized automatically.
However, it may be useful in case of power failures or system shutdowns
where a program terminates
prematurely without synchronization.
This option will not be shown when the job is run on Node-1.
If the job did not run as expected:
- Check the "Program Output" for any clues. This is the
console output of the program.
- Check the "Input Datafile". Make sure there are no blank lines or
funny characters for each entry.
- Check the input profile to make sure it was properly uploaded.
- Plot the index profiles to make sure your polygon descriptions were
interpreted correctly.