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 can be very intensive for two-dimensional structures.
It increases approximately as x^2*y where x is the number of
points
along the x-axis and y is the number of points along the y-axis.
To conserve memory, one should carefully design the grid such that there are
as few x points as possible.
Before
submitting a job, estimate the memory requirement to make sure it can run
on this 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 "Console Output" for any clues.
- Make sure there are no blank lines or funny characters in the input boxes.
- Plot the index profiles to make sure your polygon descriptions were
interpreted correctly.