Parallel Groups are server-side node containers that work similar to Groups, but without ordering constraints for the contained nodes. This means that on parallel architectures the elements of a Parallel Group can be executed concurrently.
Create and return a Group.
| target |
A target for this Group. If target is not a Group or Synth, it will be converted as follows: If it is a Server, it will be converted to the default_group of that server. If it is nil, to the default_group of the default Server. | ||||||||||
| addAction |
one of the following Symbols:
Note: A Synth is not a valid target for \addToHead and \addToTail. |
The following convenience methods correspond to the add actions above:
Create and return a Group and add it immediately after aNode.
Create and return a Group and add it immediately before aNode.
Create and return a Group. If aGroup is a Group add it at the head of that group. If it is a Server, add it at the head of the default_group of that server. If it is nil, add it at the head of the default_group of the default Server.
Create and return a Group. If aGroup is a Group add it at the tail of that group. If it is a Server, add it at the tail of the default_group of that server. If it is nil, add it at the tail of the default_group of the default Server.
Create and return a Group and use it to replace nodeToReplace, taking its place in its server's node order.
Like with Groups, it is possible to create a a ParGroup object without immediately creating a parallel group in the server.
Create and return a ParGroup object without creating a group node on the server. (This method is inherited from Node and is documented here only for convenience.)
| server |
An optional instance of Server. If nil this will default to the default Server. |
| nodeID |
An optional node ID number. If not supplied one will be generated by the Server's NodeIDAllocator. Normally you should not need to supply an ID. |
For a detailed discussion please refer to Group: *basicNew.