Overview of ICE project: integration of computational fluid dynamics and experiments

Original publisher: [Cleveland, Ohio] : National Aeronautics and Space Administration, Glenn Research Center ; Hanover, MD : Available from NASA Center for Aerospace Information, [2001]. OCLC Number: (OCoLC)50752485 Excerpt: ... Figure 13. - Parallel-processing user interface. various MSTAGE code parameters, and a processor load monitor. The right side of figure 13 depicts the architecture selection screen. The architectures shown for a particular user are determined from a text file that lists all the parallel-processing environments for which the user has an account. The user then chooses the architecture and the individual processors on which to run a CFD code. Parallel archi-tectures are represented graphically with icons. Any unavailable machines or processors are " grayed out. " The user clicks with a mouse on the desired available architecture from the choices shown. The software then shows the available processors on that architecture. Figure 14 illustrates the resulting screen if the user selects the LACE clus-ter. The LACE cluster is composed of 32 IBM RS6000 workstations interconnected by a high-speed network. The user has several options at this point. The user may return to the main screen by clicking on the Main Screen button ( lower left of fig. 14 ). Alternatively, the user may wish to view the processor usage of the selected architecture. The left side of figure 14 shows an example output after clicking on the Processor Usage button ( upper left of fig. 14 ). From this information the user can determine which processors to avoid or select. The user then selects which pro-cessors will be used to execute the parallel CFD code. After the processors are selected, the user clicks on the Create procdef button ( on the lower right of fig. 14 ). Once the parallel architecture is selected, the user designates which field ( or fields ) of MSTAGE's run-time record will be visualized in a x-y plot. A click on the desired data in the knowledge-base screen ...