cn09+@andrew.cmu.edu (Christopher Kalevi Nuuja) (11/10/90)
--> Solution: Create TAP module which uses unix sleep call to wait 20 seconds and output an integer asynchronously. This becomes the impetus for the data module to fire. tap->science->geometry->render->write. Kind o' Kludgy. I solved the problem by writing an input coroutine module. Coroutines execute whenever they please. There is a routine called AVScorout_wait() that halts the module from executing again until the network is done processing the the last data it sent out. The module takes as inputs a file base name, a low bound, and a highbound. It executes by loading filebase.lowbound.fld, sending it out as output, waiting for the network to process it, then loading filebase.lowbound+1.fld, etc. It can either stop at the high bound, or set the filenumber back to lowbound and simply cycle through the files. No kludge at all. Chris Nuuja Pittsburgh SuperComputing Center nuuja@a.psc.edu Blah Blah Blah