Managing Job - Revision history

Altadyna at 00:55, 21 May 2015

2015-05-21T00:55:48Z

Altadyna: /* Submitting a job */

2015-05-21T00:34:08Z

‎Submitting a job

Altadyna at 00:32, 21 May 2015

2015-05-21T00:32:41Z

Altadyna at 23:30, 20 May 2015

2015-05-20T23:30:29Z

Altadyna at 23:29, 20 May 2015

2015-05-20T23:29:25Z

Altadyna at 23:28, 20 May 2015

2015-05-20T23:28:06Z

Altadyna at 21:25, 20 May 2015

2015-05-20T21:25:43Z

Altadyna at 21:11, 20 May 2015

2015-05-20T21:11:06Z

Altadyna: /* Monitoring force history */

2015-05-20T19:09:06Z

‎Monitoring force history

Altadyna: Job Monitor

2015-05-20T18:59:23Z

Job Monitor

← Older revision		Revision as of 00:55, 21 May 2015
Line 68:		Line 68:
	=Restarting a job=		=Restarting a job=
	Parameters related to restart are defined in the project setup. User just need to resubmit the job after setting restart parameters in project setup. It's an good idea to pipe screen output into a different file.		Parameters related to restart are defined in the project setup. User just need to resubmit the job after setting restart parameters in project setup. It's an good idea to pipe screen output into a different file.
		+
		+	[[Category:Jobs]]

@@ Line 4: / Line 4: @@
 After a project has been setup, its simulation can be submitted from the viewer. Click on the "Job Monitor" button to open "Job Monitor" dialog.
-[[File:Job_Monitor_0.png|caption]]
+[[File:Job_Monitor_0.png|caption|600px]]
 ==Specifying solver options==

@@ Line 3: / Line 3: @@
 =Submitting a job=
 After a project has been setup, its simulation can be submitted from the viewer. Click on the "Job Monitor" button to open "Job Monitor" dialog.
 ==Specifying solver options==

@@ Line 61: / Line 61: @@
 User can right click in the graph area and select "Set axis range" in the popup menu. The range of each axis can be specified. Default range is automatically computed to cover the min and max values.
-----
+=Killing a job=
-−
-=Kill a running job=
 If a simulation is submitted from the viewer, click on the "Kill Job" button. On any platform users may have to kill the solver process manually.
-=Restart a job=
+=Restarting a job=
 Parameters related to restart are defined in the project setup. User just need to resubmit the job after setting restart parameters in project setup. It's an good idea to pipe screen output into a different file.

@@ Line 52: / Line 52: @@
 ==Monitoring force history==
 [[File:Job_monitor.png|thumb|200px]]
 The graph will automatically update when data is available. The horizontal axis is "Time", the physical time simulation has reached. On the right side is a list of variables available for plot. "Time", "Force:X", "Force:Y" and "Torque:Z" are always in the force history file. Other components are available if they were requested and/or the simulation is a 3D analysis.
 User can right click in the graph area and select "Set axis range" in the popup menu. The range of each axis can be specified. Default range is automatically computed to cover the min and max values.
 =Kill a running job=

@@ Line 14: / Line 14: @@
 :-release_all_lics
 ::releases all the solver licenses held up by this client computer. This option is useful when previous job was terminated abnormally without releasing the licenses. Note that client compute cannot ask the license server to release solver licenses held up by other computers. License server's administrator can perform such a task.
 Options related to simulation
@@ Line 20: / Line 26: @@
 :-no_shared_mem
 ::effective for linux only. Shared memory will be turned off. More memory consumption is expected. This option is useful when some linux OS or hardware causes simulation with shared memory to crash.
 ==From command line==
 =Monitoring job status=
 ==Screen output==
 ==Monitoring force history==
-After the job is running, from the "Job Monitor" dialog, click on "Show graph" and open the file "project_force.csv"
+Force history often is a good indication for convergence. When the job is running, from the "Job Monitor" dialog, click on "Show graph" and open the file "project_force.csv".
 [[File:Job_monitor.png|thumb|200px]]
-The horizontal axis is "Time", the physical time simulation has reached. On the right side is a list of variables available for plot. "Time", "Force:X", "Force:Y" and "Torque:Z" are always in the force history file. Other components are available if they were requested and/or the simulation is a 3D analysis.
+The graph will automatically update when data is available. The horizontal axis is "Time", the physical time simulation has reached. On the right side is a list of variables available for plot. "Time", "Force:X", "Force:Y" and "Torque:Z" are always in the force history file. Other components are available if they were requested and/or the simulation is a 3D analysis.
-User can right click in the graph area and select "Set Range" in the popup menu. The range of each axis can be specified. Default range is automatically computed to cover the min and max values.
+User can right click in the graph area and select "Set axis range" in the popup menu. The range of each axis can be specified. Default range is automatically computed to cover the min and max values.
 =Kill a running job=
 =Restart a job=

@@ Line 8: / Line 8: @@
 Options related to solver licenses (note that solver license is different from viewer license)
- -query_lic_server: query license information, such as license expiration date and how many licenses are available
+:-query_lic_server
- -list_lic_usage: shows the licenses been used by all running simulations
+::query license information, such as license expiration date and how many licenses are available
- -release_all_lics: releases all the solver licenses held up by this client computer. This option is useful when previous job was terminated abnormally without releasing the licenses. Note that client compute cannot ask the license server to release solver licenses held up by other computers. License server's administrator can perform such a task.
+:-list_lic_usage
 Options related to simulation
- -exact_resolution: grid cell size will equal to the user defined value exactly. When this option is given discretization may be less robust. This option is useful for some validation cases.
+:-exact_resolution
- -no_shared_mem: effective for linux only. Shared memory will be turned off. More memory consumption is expected. This option is useful when some linux OS or hardware causes simulation with shared memory to crash.
+::grid cell size will equal to the user defined value exactly. When this option is given discretization may be less robust. This option is useful for some validation cases.