| 29 | | * <code>simtest.basic</code> specifies the setup (see <code>ippTasks/simtest.basic.config</code>). |
| 30 | | * <code>dbname</code> is your database name: it must have already been set up (e.g., using <code>dbadmin</code>), though it needn't have been created (using <code>pxadmin</code>) since the <code>simtest</code> will do that, depending on the <code>init</code> value you give it. |
| 31 | | * <code>computer</code> is the name of a processing node: you must be able to <code>ssh</code> to this node without it prompting for a password. |
| 32 | | * The <code>init</code> value (in the example here, <code>2</code>) specifies what needs to be done. |
| | 29 | * {{{simtest.basic}}} specifies the setup (see {{{ippTasks/simtest.basic.config}}}). |
| | 30 | *{{{dbname}}} is your database name: it must have already been set up (e.g., using {{{dbadmin}}}), though it needn't have been created (using {{{pxadmin}}}) since the {{{simtest}}} will do that, depending on the {{{init}}} value you give it. |
| | 31 | * {{{computer}}} is the name of a processing node: you must be able to {{{ssh}}} to this node without it prompting for a password. |
| | 32 | * The {{{init}}} value (in the example here, {{{2}}}) specifies what needs to be done. |
| 34 | | After this, the database will be (re)created, simulated images will be generated, and the usual processing should automatically take place all the way through to the diff stage. As usual, you can track how things go using the <code>status</code> command in pantasks, or using the IPP Monitor (if you've got it set up). |
| | 34 | After this, the database will be (re)created, simulated images will be generated, and the usual processing should automatically take place all the way through to the diff stage. As usual, you can track how things go using the {{{status}}} command in pantasks, or using the IPP Monitor (if you've got it set up). |