Difference between revisions of "Undocumented Custom Task"

From OSUPDOCS
Jump to navigation Jump to search
Line 1: Line 1:
If a [[MPM Input Files#Custom Tasks|custom task]] is available but is unknown to [[NairnFEAMPM]] or [[NairnFEAMPMViz]], you can still use such tasks.
If a [[MPM Input Files#Custom Tasks|custom task]] is available but is unknown to [[NairnFEAMPM]] or [[NairnFEAMPMViz]], you can still use such tasks.
In scripted files, an unknown task name <tt>NewTask</tt> custom task is scheduled using
In scripted files, an unknown custom task name <tt>NewTask</tt> is scheduled using the commands


  CustomTask NewTask
  CustomTask NewTask

Revision as of 11:42, 2 June 2015

If a custom task is available but is unknown to NairnFEAMPM or NairnFEAMPMViz, you can still use such tasks. In scripted files, an unknown custom task name NewTask is scheduled using the commands

CustomTask NewTask
Parameter Param1,(value1)
    . . .

where you provide name of the task and its parameters as required by the task. The name and parameters are all case sensitive (in contrast to known task that may be tolerant of different cases. In XML files, this tasks is scheduled using a Schedule element, which must be within the single <CustomTasks> block:

<Schedule name='newTask'>
   <Parameter name='Param1'>(value2)</Parameter>
        . . .
</Schedule>

The use of unknown custom tasks allows you to provided for user-written custom tasks. For more details on writing custom tasks, see the help on developing a custom task.