Achronix ACE Version 5.0 User Manual

Page 142

Advertising

Views

Chapter 3. Concepts

(configured in Preferences)

This link, when selected, will bring up the

Multiprocess View Preference

Page

, allowing the user to configure the

qsub

command-line options

which will be used when submitting jobs to the GridEngine.

When the Parallel Job Count is set to the minimum value of 1, all selected implementations will be executed
sequentially, one at a time. A value of 2 would cause all selected implementations to be queued, and
then the first two queued implementations would be allowed to execute at the same time. As soon as
an implementation completes its flow execution, the next queued implementation starts flow execution
and the

Multiprocess Summary Report

is updated with information gathered from the just-completed

implementation.

By default, ACE executes implementations in parallel by starting a background process on the host
workstation for each implementation. In this case, the effectiveness of parallel implementation execution
will naturally be limited by the resources of the host workstation.

Alternately, ACE may execute

the implementations in processes distributed among multiple hosts via an external GridEngine, which
will theoretically allow for greater parallel compute resources.

The GridEngine submissions are via

the GridEngine command-line executable ”

qsub

”, which may be configured via the

Multiprocess View

Preference Page

, reached by following the (configured in Preferences) hyperlink.

See

Configuring the Execution Queues

for more details regarding parallel implementation execution,

configuration, and GridEngine support.

Multiprocess Flow Management

This section allows the user to alter how far the flow will be executed for the multiprocess implementations.

Multiprocess Flow Management Controls

Name

Description

Stop Flow After

Allows the user to override standard flow behavior, and stop the flow early - the
flow step selected becomes the final flow step executed by all multiprocess
implementations. Useful when steps late in the flow are known to fail with
reported errors, but the user still wishes to run multiple implementations through
earlier parts of the flow.

Force Selected
Flow Step to be
Enabled

When optional flow steps are selected as the final flow step (in the Stop Flow After
drop-down list), this checkbox can ensure that the selected step is always enabled
in the multiprocess flows, regardless of the flow step’s current enabled state in the

Flow View