Hello Tom, Our group has demos numbered 23, 24, and 25. First, has our Immersadesk and Octane been 'volunteered' into the pool for use by others? We have a site visit scheduled the week before Alliance '98 and would like to (need to) keep our Immersadesk here for that. What would be best for us if it's possible is for us to use our own Immersadesk, Octane, and PC for our demos. We can set things up here and then just make sure they are ready to ship (we could use some help on this) to the Assembly Hall in time for assembly and demos at Alliance '98. If they need to be used for other demos, the best thing would be if you could have an alternative disk to boot with that we could attach and reboot as necessary - that could be set up the week before on another system and then just attached to our Octane at the Assembly Hall location. Here are the answers to the best of my ability - If we could use our own setup that really would be the best - we're short on people-power so the less we have to do "different" just for Alliance '98 the better. Eric will review these responses when he gets back. Others, please see if I have missed anything on the demos you are involved in. 23 = Parallel application performance analysis and optimization (SvPablo) 24 = Collaborative Virtual Environments (Virtue/Habanero/Orbit) 25 = I/O Characterization and Optimization (with HDF) QUESTIONS 1. Each ImmersaDesk will have at least 100 Mb/s individually switched IP connectivity to NCSA's core network, and from there to the vBNS and the outside world. Multicast will also be provided to other vBNS sites. Is this sufficient for your application's networking needs? If not, please explain. Will one network connection be sufficient? If not, how many will be needed? If your application will do point-to-point communication, what other sites will you need connectivity to? If your application requires multicast, what other sites will you need connectivity to? 23: One connection should be sufficient 24: We will need more than one connection - one for the Octane, and one for 3 PCs participating in the collaborative environment. This does use multicast, although we could run with all of these on an isolated net for this demo - they don't have to be on the main net. << Eric and Dan - I'm thinking octane, PC for tracker, PC for Orbit, PC for Habanero, PC for voice server - does that seem reasonable? >> 25: One connection should be sufficient. << Luiz and Ying - we need to verify that svPablo interface works well on the SGI platform >> 2. If your application is an ImmersaDesk application, what will the frame rate be on the following hardware: Octane Irix 6.4, dual R10K cpus, MXi graphics, 256 MB RAM Onyx Irix 6.2, four R4400 CPUs, 256 MB RAM, RE2 graphics (with two RM5s of texture memory) Onyx Irix 6.2, four R10K cpus, 256 MB RAM, IR graphics (DG4-2 with two RM64s of texture memory) Onyx2 Irix 6.4, two R10K cpus, 256 MB RAM, IR graphics (DG4-2 with two RM64s of texture memory) 24: This is an Immersadesk application but I don't know the frame rate. Our Octane with 2 CPUs will be sufficient. 3. Beyond a standard SGI (as listed above) running an ImmersaDesk, does your application require any other type of machine/OS. such as a SUN, PC, or Macintosh? If so, what machine/OS is needed? Can you supply it if needed? 23: Nothing additional needed 24: Need PC for tracker, PC for voice server and also 2 PCs for collaborative environment. We can supply these. 25: Nothing additional needed 4. An ImmersaDesk will be available as a large-format, passive display device capable of displaying output from both SGIs and PCs. If applicable, does your application require any other type of display device? If so, please describe. 23: Nothing additional 24: Uses IDesk capability 25: May use Idesk capability. 5. Does your application require more than 500 MB of local disk space? If so, how much local disk space does it need? 23, 24, 25 - possibly all will require more disk space as we have large trace files. It depends on what the demo "slots" will be. If we use our own system we will take care of the disk requirement. 6. Does your application require a telephone on the demo show floor? Will it require more than one telephone line? If so, how many? 23, 24, 25 - no phone required. 7. Each ImmersaDesk machine will have the following software installed: C/C++ (7.1 or 7.2) F77/90 (7.1 or 7.2) CAVE, pfCAVE Libs (2.6) CAVERN MPI NEXUS/GLOBUS NCSA vss and sound lib CaseVision CosmoPlayer (1.0.2) CosmoWorlds Java Development environment (SGI's JDK) Inventor Performer (2.1 or 2.2) GNU tools (gmake, gzip, emacs/xemacs) Habanero Multicast tools (sdr, vic, vat) Netscape Communicator Does your application require any additional software? If so, please list. Can you provide it along with suitable licenses, if needed? 23: HPF compiler if we do this in real-time. Else, we can pre-run the apps and just show the results of the run. We have HPF on our Octane. It is also on Origin where apps are typically run 24: We will supply what s/w we need here. 25: HDF with Pablo extensions if we do this in real-time. More likely we will run the apps ahead of time any only show perf results here. We can supply this. 8. Beyond a standard SGI (as listed above) running an ImmersaDesk, does your application require any auxiliary computing resources *not* on the show floor (eg. remote servers or supercomputers)? If so, what resources do you need? Have you made the necessary arrangements for them? 23, 25: we may want to run on the Origin at NCSA while doing the demo. We have not discussed this in detail and I won't know for sure until week after next. We have not made these arrangments and if the system is not available we should be able to demo w/o it. 9. Beyond a standard ImmersaDesk configuration, does your application require any additional input/output devices? If so, what are they? Can you provide them? What is needed to connect them to an ImmersaDesk? 24: We need a PC acting as a voice server and the other systems listed earlier. WE can bring those and the microphone, etc. 10. Does your application use the NCSA 'vss' sound server? Does your application require the use of a dedicated Indy as a sound server? Does your application do ImmersaDesk-to-ImmersaDesk communication and require a corresponding audio connection? If your application is a non-VR presentation, does it need amplification? What other audio requirements do you have? 24: We have all the audio things we need on our hardware. 11. Does your application use the standard ImmersaDesk VR tracker daemon? If not, which tracker daemon does it use? 24, 25: Eric? I think it's standard tracker but am not positive. --RAA08320.890178383/cymbal.cs.uiuc.edu--