home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #31 / NN_1992_31.iso / spool / comp / graphics / avs / 1032 next >
Encoding:
Internet Message Format  |  1992-12-21  |  2.4 KB

  1. Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!spool.mu.edu!agate!overload.lbl.gov!ux6.lbl.gov!wes
  2. From: wes@ux6.lbl.gov (Wes Bethel)
  3. Newsgroups: comp.graphics.avs
  4. Subject: Re: Help with Synchronization
  5. Date: 21 Dec 1992 17:58:54 GMT
  6. Organization: Lawrence Berkeley Laboratory
  7. Lines: 57
  8. Message-ID: <1h50kuINNejm@overload.lbl.gov>
  9. References: <1992Dec20.054705.8951@ccnews.nctu.edu.tw+
  10. Reply-To: wes@ux6.lbl.gov (Wes Bethel)
  11. NNTP-Posting-Host: ux6.lbl.gov
  12.  
  13. In article <1992Dec20.054705.8951@ccnews.nctu.edu.tw+ blshyu@nctu.edu.tw () writes:
  14. +...
  15. +                                 boolean
  16. +                                    |
  17. +             ----------------------
  18. +            |                      |
  19. +            |                animate_file
  20. +                    |                      |
  21. +            |                 read_field
  22. +            |                      |
  23. +               animate_file           iso_surface
  24. +            |                      |
  25. +            |               render_geometry
  26. +            |                      |
  27. +             ---------    --------- 
  28. +                      |  |
  29. +                               write_image
  30. +
  31. +  The "write_image" module needs two inputs from the two branches of
  32. +the network indevudually.  Since the right branche of the network
  33. +needs more time to complete the calculation than the left branch, I
  34. +need a method to do the synchronization of the two branch or I can have
  35. +many images saved with different names but with the same content.
  36.  
  37. (sorry for including so much of the original article - it was unavoidable)
  38.  
  39. Back when I was in school, the EE's would use a T-flop (trigger
  40. flip-flop) to solve this problem. At the IAC is a module called
  41. "shutter" which provides the functionality that you need. 
  42.  
  43. It takes as input an image, and when a "true" signal is applied to
  44. it's "fire" parameter, it sends the input image to its output port.
  45.  
  46. So, your modified network would look like:
  47.  
  48. +                                 boolean
  49. +                                    |
  50. +             ----------------------
  51. +            |           |          |
  52. +            |           |    animate_file
  53. +                    |           |          |
  54. +            |           |     read_field
  55. +            |           |          |
  56. +               animate_file     |     iso_surface
  57. +            |           |          |
  58. +            |           |   render_geometry
  59. +            |           |          |
  60. +             ---------  | --------- 
  61. +                      | ||
  62. +                      | shutter
  63. +                      |  |
  64. +                               write_image
  65. +
  66.  
  67. Happy holidays!
  68.  
  69. wes
  70.