<XML><RECORDS><RECORD><REFERENCE_TYPE>3</REFERENCE_TYPE><REFNUM>5827</REFNUM><AUTHORS><AUTHOR>Nebel,J-C.</AUTHOR></AUTHORS><YEAR>1998</YEAR><TITLE>A Concurrent Dataflow Algorithm for RayTracing</TITLE><PLACE_PUBLISHED>16th Eurographics UK Conference'98, 25-27 March 1998, Leeds, UK </PLACE_PUBLISHED><PUBLISHER>Academic Press</PUBLISHER><LABEL>Nebel:1998:5827</LABEL><KEYWORDS><KEYWORD>Computer graphics</KEYWORD></KEYWORDS<ABSTRACT>Ray tracing has become established as one of the most important and popular rendering techniques for synthesizing photo-realistic images. However, the high quality images require long computation times and memory-consuming scene description. Parallel architectures with distributed memories are increasingly being used for rendering and provide more memory and CPU power. This paper describes a new way to employ such computers efficiently for ray tracing. Here each pixel is processed independently, so a natural method of parallelization is to distribute pixels over the machine nodes. If the entire scene can be duplicated in the memory of each processor (in the absence of global memory), a scheme without dataflow is used, otherwise, objects composing the scene have to be distributed over processor nodes. In this last case two strategies are applicable to the computation: object dataflow and ray dataflow. The fastest of these algorithms is the one without dataflow. If we want to deal with realistic pictures described by large scenes, we have to distribute objects among processors. Accordingly a choice has to be made between object and ray dataflow. This choice is not easy because of variability in computers, communication networks and scenes, also algorithms might not be based on the same sequential model. Here, we propose a method which chooses the type of flow to use dynamically. This arose from the development of a parallel ray tracing algorithm that included the two modes of dataflow, i.e. a concurrent dataflow algorithm. As our scheme allows the use of both algorithms, processors need to exchange objects and rays. The processors' load and some local parameters are used to choose between ray or object dataflow at any instant. Global information is transmitted by a non-centralized strategy, which assures scalability and the production of relevant messages. Finally, our algorithm offers a dynamic management of concurrent dataflows, which intrinsically assures dynamic load balancing. Using concurrent dataflow our </ABSTRACT></RECORD></RECORDS></XML>