Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

icetdatareplicationgroup(3) [debian man page]

icetDataReplicationGroup(3)					  IceT Reference				       icetDataReplicationGroup(3)

NAME

       icetDataReplicationGroup -- define data replication.

Synopsis
       #include <IceT.h>

       void icetDataReplicationGroup(	IceTInt 	  size,
					const IceTInt *   processes  );

Description
       IceT  has the ability to take advantage of geometric data that is replicated among processes. If a group of processes share the same geome-
       try data, then IceT will split the region of the display that the data projects onto among the processes, thereby reducing the total amount
       of image composition work that needs to be done.

       Each  group  can be declared by calling icetDataReplicationGroup and defining the group of processes that share the geometry with the local
       process. size indicates how many processes belong to the group, and processes is an array of ids of processes that  belong  to  the  group.
       Each process that belongs to a particular group must call icetDataReplicationGroup with the exact same list of processes in the same order.

       You can alternately use icetDataReplicationGroupColor to select data replication groups.

       By default, each process belongs to a group of size one containing just the local processes (i.e. there is no data replication).

Errors
       ICET_INVALID_VALUE
	       processes does not contain the local process rank.

Warnings
       None.

Bugs
       IceT assumes that icetDataReplicationGroup is called with the exact same parameters on all processes belonging to a given group.  Likewise,
       IceT also assumes that all processes have called icetBoundingVertices or icetBoundingBox with the exact same parameters	on  all  processes
       belonging  to  a  given	group. These requirements are not strictly enforced, but failing to do so may cause some of the geometry to not be
       rendered.

Copyright
       Copyright (C)2003 Sandia Corporation

       Under the terms of Contract DE-AC04-94AL85000 with Sandia Corporation, the U.S. Government retains certain rights in this software.

       This source code is released under the New BSD License.

See Also
       icetDataReplicationGroupColor(3), icetBoundingVertices(3), icetBoundingBox(3)

IceT Reference							September 20, 2010				       icetDataReplicationGroup(3)

Check Out this Related Man Page

icetCreateContext(3)						  IceT Reference					      icetCreateContext(3)

NAME

       icetCreateContext -- creates a new context.

Synopsis
       #include <IceT.h>

       IceTContext icetCreateContext(	IceTCommunicator   comm  );

Description
       The  icetCreateContext  function creates a new .igcontext!IceT IceT context, makes it current, and returns a handle to the new context. The
       handle returned is of type IceTContext.	This is an opaque type that should not be handled directly, but rather simply passed to other IceT
       functions.

       Like  OpenGL  ,the  IceT  engine  behaves like a large state machine. The parameters for engine operation is held in the current state. The
       entire state is encapsulated in a context. Each new context contains its own state.

       It is therefore possible to change the entire current state of IceT by simply switching contexts. Switching contexts is	much  faster,  and
       often more convenient, than trying to change many state parameters.

Errors
       None.

Warnings
       None.

Bugs
       It  may	be  tempting to use contexts to run different IceT operations on separate program threads. Although certainly possible, great care
       must be taken. First of all, all threads will share the same context. Second of all, IceT is not thread safe. Therefore,  a  multi-threaded
       program	would  have to run all IceT commands in `critical sections' to ensure that the correct context is being used, and the methods exe-
       cute safely in general.

Notes
       icetCreateContext duplicates the communicator comm.  Thus, to avoid deadlocks on certain implementations (such as MPI), the user level pro-
       gram should call icetCreateContext on all processes with the same comm object at about the same time.

Copyright
       Copyright (C)2003 Sandia Corporation

       Under the terms of Contract DE-AC04-94AL85000 with Sandia Corporation, the U.S. Government retains certain rights in this software.

       This source code is released under the New BSD License.

See Also
       icetDestroyContext(3), icetGetContext(3), icetSetContext(3), icetCopyState(3), icetGet(3)

IceT Reference							  August  9, 2010					      icetCreateContext(3)
Man Page