DOCSLIB.ORG

Scientific Visualization at Jülich Supercomputing Centre

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Scientific Visualization at Jülich Supercomputing Centre Mitglied der Helmholtz-GemeinschaftderMitglied Scientific Visualization at Jülich Supercomputing Centre 1 Jülich Supercomputing Centre, Forschungszentrum Jülich GmbH, Germany Cross-Sectional-Team „Visualization“ [email protected], [email protected] Page 1 Visualization at JSC Cross-Sectional Team “Visualization” Domain-specific User Support and Research at JSC . Scientific Visualization – R&D + support for visualization of scientific data . Virtual Reality – VR systems for the analysis and presentation . Multimedia – multimedia productions for websites, presentations or on TV Deep Learning http://www.fz-juelich.de/ias/jsc/EN/Expertise/Support/Visualization/_node.html Page 2 Visualization at JSC JURECA: General Hardware Setup JURECA 6x 12x Visualization Nodes vis batch . 2 GPUs Nvidia Tesla K40 per node nodes . 12 GB RAM on each GPU 6x . 6x Vis. Login Nodes vis login nodes . jurecavis.fz-juelich.de . (jurecavis01 to jurecavis06 in round-robin fashion) 12x login . 512 GB RAM each nodes . 6x Vis. Batch Nodes InfiniBand . 4 nodes with 512 GB RAM 1872x . 2 nodes with 1024 GB RAM compute nodes . special partition: vis Data . Use vis. batch nodes via job submit. GPFS Keep in mind: Visualization is NOT limited to vis. nodes ONLY. (software rendering is possible on any node) Page 3 Visualization at JSC JUWELS: General Hardware Setup 4x Visualization Login Nodes . juwelsvis.fz-juelich.de . (juwelsvis00 to juwelsvis03 in round-robin fashion) . 768 GB RAM each . 1 GPUs Nvidia Pascal P100 per node . 12 GB RAM on GPU Vis nodes not ready to use as of today, but very soon! Page 4 Visualization at JSC General Software Setup Special Software Stack on Vis Nodes: Base Software: X-Server, X-Client (Window-Manager) OpenGL (libGL.so, libGLU.so, libglx.so), Nvidia Middleware: Virtual Network Computing: VNC-Server, VNC-Client VirtualGL Parallel and Remote Rendering Apps, In-Situ Visualization: ParaView VisIt Other Visualization Packages: VMD, PyMol, Blender, GPicView, GIMP Page 5 Visualization at JSC Usage Model for Vis Nodes JURECA projects: - Visualization possible on 6 vis login nodes - Every project gets a small contingent (1000 core h) for vis batch nodes in addition to project contingent - Contingent is valid for partition “vis” - If you need more compute time for visualization: send a request to [email protected] JUWELS projects: - Visualization will be possible on 4 vis login nodes - No visualization batch nodes - As of today, visualization software stack not production ready, but close. Available soon Non HPC-Project Users: - apply for test project - get a small contingent for vis nodes (1000 core h) Page 6 Mitglied der Helmholtz-GemeinschaftderMitglied Remote 3D Visualization 1 Jülich Supercomputing Centre, Forschungszentrum Jülich GmbH, Germany Cross-Sectional-Team „Visualization“ [email protected], [email protected] Page 7 Remote 3D Visualization General Setup JURECA User’s Work- 6x vis batch station nodes 6x vis login nodes Firewall 12x login vis login node: nodes - direct user access - no accounting InfiniBand - shared with other users 1872x compute nodes - no parallel jobs (no srun) Data vis batch node: GPFS - access via batch system, partition “vis” - accounting - exclusive usage - parallel jobs possible Page 8 Remote 3D Visualization at Jülich Supercomputing Centre . X forwarding + Indirect Rendering slow, maybe incompatible bad idea . “remote aware” visualization apps (ParaView, VisIt) application dependent error-prone setup . VNC (Virtual Network Computing) + VirtualGL our recommendation good idea . Xpra - stream application content with H.264 + VirtualGL alternative recommendation good idea Page 9 Remote 3D Visualization with X Forwarding + Indirect Rendering Traditional Approach (X forwarding + Indirect Rendering) ssh –X <USERID>@<SERVER> . uses GLX extension to X Window System . X display runs on user workstation . OpenGL command are encapsulated inside X11 protocol stream . OpenGL commands are executed on user workstation . disadvantages . User´s workstation requires a running X server. User´s workstation requires a graphic card capable of the required OpenGL. User´s workstation defines the quality and speed of the visualization. User´s workstation requires all data needed to visualize the 3d scene. This approach is known to be error prone (OpenGL version mismatch, …) Try to AVOID for 3D visualization. Page 10 Remote 3D Visualization with VNC (Virtual Network Computing) + VirtualGL State-of-the-Art Approach (VNC with VirtualGL) vncserver, vncviewer . platform independent . application independent . session sharing possible . advantages . No X is required on user´s workstation (X display on server, one per session). No OpenGL is required on user´s workstation (only images are send). Quality of visualization does not depend on user´s workstation. Data size send is independent from data of 3d scene. Disconnection and reconnection possible. http://www.virtualgl.org Try to USE this approach for 3D visualization. Page 11 Remote 3D Visualization with VNC (Virtual Network Computing) + VirtualGL VNC + VirtualGL vglrun <application> . OpenGL applications send both GLX and X11 commands to the same X display. Once VirtualGL is preloaded into an OpenGL application, it intercepts the GLX function calls from the application and rewrites them. The corresponding GLX commands are then sent to the X display of the 3d X server, which has a 3D hardware accelerator attached. http://www.virtualgl.org Page 12 Remote 3D Visualization with VNC (Virtual Network Computing) + VirtualGL VNC + VirtualGL vglrun <application> . Recommended solution for any OpenGL application e.g. ParaView, VisIt, IDL, VMD, PyMol, … . Allows fast and reliable server-side hardware rendering (GPU acceleration) with VirtualGL . User only installs local VNC viewer . Desktop sharing possible . Should also be used for the frontend of “remote aware” applications (e.g. for ParaView and VisIt, …) http://www.virtualgl.org Our recommendation: Use VNC for remote rendering Page 13 Remote 3D Visualization Predefined Desktop Profiles with VNC + VirtualGL vncserver –profile vis nice blue JSC background clock counting up/down MOTD window desktop CPU, memory utilization symbols for vis apps, visualization application LLview, … GPU utilization VNC utilization Page 14 Remote 3D Visualization with VNC + VirtualGL JURECA 6x vis batch nodes 6x vis login nodes Firewall 12x login HowTo start a VNC session nodes 1. SSH to HPC system, authenticate via SSH key pair 2. Start vncserver e.g. by InfiniBand “vncserver –geometry 1920x1080 –profile vis –fg” 1872x 3. Look at the output and note the display number, compute nodes e.g. „ … desktop is jrc1386:3“ (Display 3 corresponds to TCP-port 5900+3=5903) Data 4. establish SSH tunnel to exactly this node with GPFS correct source and destination port (5903 in the example above) 5. start local VNC client and connect to remote display https://trac.version.fz-juelich.de/vis/wiki/vnc3d/manual Page 15 Mitglied der Helmholtz-GemeinschaftderMitglied Remote 3D Visualization (possible scenarios) 1 Jülich Supercomputing Centre, Forschungszentrum Jülich GmbH, Germany Cross-Sectional-Team „Visualization“ [email protected], [email protected] Page 16 Visualization Scenario 1: Vis Login Node with VNC JURECA User’s Work- 6x station vis batch nodes 6x vis login nodes Firewall ssh + VNC tunnel (port 590<d>) 12x login nodes InfiniBand 1872x vis login node: compute nodes + no batch job needed, no accounting - resources shared between users Data GPFS https://trac.version.fz-juelich.de/vis Page 17 Visualization Scenario 2: Vis Batch Node with VNC JURECA User’s Work- 6x station vis batch nodes 6x vis login nodes Firewall ssh + VNC tunnel (port 590<d>) 12x login nodes InfiniBand 1872x compute nodes Data GPFS vis batch node: - batch job needed, accounting, exclusive + server can run in parallel (but number of vis nodes limited to 4) https://trac.version.fz-juelich.de/vis Page 18 Visualization Scenario 3: Vis.Login for GUI, Comp. Nodes for Server JURECA User’s Work- 6x station vis batch nodes 6x vis login nodes Firewall ssh + VNC tunnel (port 590<d>) 12x login nodes InfiniBand 1872x vis login node: compute nodes + no batch job needed, no accounting - resources shared between users Data GPFS vis batch node: - batch job needed, accounting, exclusive + server can run in parallel (but number of vis nodes limited to 4) https://trac.version.fz-juelich.de/vis Page 19 Visualization Scenario 4: Vis Login for GUI, Compute for Server JURECA User’s Work- 6x station vis batch nodes 6x vis login nodes Firewall ssh + VNC tunnel (port 590<d>) 12x login nodes InfiniBand 1872x vis login node: compute nodes + no batch job needed, no accounting - resources shared between users Data GPFS compute nodes: + vis app server can be run in parallel on a really huge number of nodes - only software rendering https://trac.version.fz-juelich.de/vis Page 20 Visualization Scenario 5: ParaView (or VisIt) without VNC JURECA User’s Work- 6x station vis batch nodes 6x vis login nodes Firewall ssh+ tunnel 12x (ParaView: port 11111) login nodes InfiniBand 1872x user workstation: compute nodes - user has to install ParaView or VisIt on his/her workstation Data GPFS vis batch node: - batch job needed, accounting, exclusive + server can run in parallel (but number of vis nodes limited to 4) https://trac.version.fz-juelich.de/vis Page 21 Mitglied der Helmholtz-GemeinschaftderMitglied Remote 3D Visualization (alternatives) 1 Jülich Supercomputing Centre, Forschungszentrum Jülich GmbH, Germany
Load more

Recommended publications
  • Release Notes for X11R6.8.2 the X.Orgfoundation the Xfree86 Project, Inc
    Release Notes for X11R6.8.2 The X.OrgFoundation The XFree86 Project, Inc. 9February 2005 Abstract These release notes contains information about features and their status in the X.Org Foundation X11R6.8.2 release. It is based on the XFree86 4.4RC2 RELNOTES docu- ment published by The XFree86™ Project, Inc. Thereare significant updates and dif- ferences in the X.Orgrelease as noted below. 1. Introduction to the X11R6.8.2 Release The release numbering is based on the original MIT X numbering system. X11refers to the ver- sion of the network protocol that the X Window system is based on: Version 11was first released in 1988 and has been stable for 15 years, with only upwardcompatible additions to the coreX protocol, a recordofstability envied in computing. Formal releases of X started with X version 9 from MIT;the first commercial X products werebased on X version 10. The MIT X Consortium and its successors, the X Consortium, the Open Group X Project Team, and the X.OrgGroup released versions X11R3 through X11R6.6, beforethe founding of the X.OrgFoundation. Therewill be futuremaintenance releases in the X11R6.8.x series. However,efforts arewell underway to split the X distribution into its modular components to allow for easier maintenance and independent updates. We expect a transitional period while both X11R6.8 releases arebeing fielded and the modular release completed and deployed while both will be available as different consumers of X technology have different constraints on deployment. Wehave not yet decided how the modular X releases will be numbered. We encourage you to submit bug fixes and enhancements to bugzilla.freedesktop.orgusing the xorgproduct, and discussions on this server take place on <[email protected]>.
    [Show full text]
  • Virtualgl / Turbovnc Survey Results Version 1, 3/17/2008 -- the Virtualgl Project
    VirtualGL / TurboVNC Survey Results Version 1, 3/17/2008 -- The VirtualGL Project This report and all associated illustrations are licensed under the Creative Commons Attribution 3.0 License. Any works which contain material derived from this document must cite The VirtualGL Project as the source of the material and list the current URL for the VirtualGL web site. Between December, 2007 and March, 2008, a survey of the VirtualGL community was conducted to ascertain which features and platforms were of interest to current and future users of VirtualGL and TurboVNC. The larger purpose of this survey was to steer the future development of VirtualGL and TurboVNC based on user input. 1 Statistics 49 users responded to the survey, with 32 complete responses. When listing percentage breakdowns for each response to a question, this report computes the percentages relative to the total number of complete responses for that question. 2 Responses 2.1 Server Platform “Please select the server platform(s) that you currently use or plan to use with VirtualGL/TurboVNC” Platform Number of Respondees (%) Linux/x86 25 / 46 (54%) ● Enterprise Linux 3 (x86) 2 / 46 (4.3%) ● Enterprise Linux 4 (x86) 5 / 46 (11%) ● Enterprise Linux 5 (x86) 6 / 46 (13%) ● Fedora Core 4 (x86) 1 / 46 (2.2%) ● Fedora Core 7 (x86) 1 / 46 (2.2%) ● Fedora Core 8 (x86) 4 / 46 (8.7%) ● SuSE Linux Enterprise 9 (x86) 1 / 46 (2.2%) 1 Platform Number of Respondees (%) ● SuSE Linux Enterprise 10 (x86) 2 / 46 (4.3%) ● Ubuntu (x86) 7 / 46 (15%) ● Debian (x86) 5 / 46 (11%) ● Gentoo (x86) 1 /
    [Show full text]
  • MC-1200 Series Linux Software User's Manual
    MC-1200 Series Linux Software User’s Manual Version 1.0, November 2020 www.moxa.com/product © 2020 Moxa Inc. All rights reserved. MC-1200 Series Linux Software User’s Manual The software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement. Copyright Notice © 2020 Moxa Inc. All rights reserved. Trademarks The MOXA logo is a registered trademark of Moxa Inc. All other trademarks or registered marks in this manual belong to their respective manufacturers. Disclaimer Information in this document is subject to change without notice and does not represent a commitment on the part of Moxa. Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time. Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use. This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication. Technical Support Contact Information www.moxa.com/support Moxa Americas Moxa China (Shanghai office) Toll-free: 1-888-669-2872 Toll-free: 800-820-5036 Tel: +1-714-528-6777 Tel: +86-21-5258-9955 Fax: +1-714-528-6778 Fax: +86-21-5258-5505 Moxa Europe Moxa Asia-Pacific Tel: +49-89-3 70 03 99-0 Tel: +886-2-8919-1230 Fax: +49-89-3 70 03 99-99 Fax: +886-2-8919-1231 Moxa India Tel: +91-80-4172-9088 Fax: +91-80-4132-1045 Table of Contents 1.
    [Show full text]
  • X Window System Network Performance
    X Window System Network Performance Keith Packard Cambridge Research Laboratory, HP Labs, HP [email protected] James Gettys Cambridge Research Laboratory, HP Labs, HP [email protected] Abstract havior (or on a local machine, context switches between the application and the X server). Performance was an important issue in the develop- One of the authors used the network visualization tool ment of X from the initial protocol design and contin- when analyzing the design of HTTP/1.1 [NGBS 97]. ues to be important in modern application and extension The methodology and tools used in that analysis in- development. That X is network transparent allows us volved passive packet level monitoring of traffic which to analyze the behavior of X from a perspective seldom allowed precise real-world measurements and compar- possible in most systems. We passively monitor network isons. The work described in this paper combines this packet flow to measure X application and server perfor- passive packet capture methodology with additional X mance. The network simulation environment, the data protocol specific analysis and visualization. Our experi- capture tool and data analysis tools will be presented. ence with this combination of the general technique with Data from this analysis are used to show the performance X specific additions was very positive and we believe impact of the Render extension, the limitations of the provides a powerful tool that could be used in the analy- LBX extension and help identify specific application and sis of other widely used protocols. toolkit performance problems. We believe this analysis With measurement tools in hand, we set about char- technique can be usefully applied to other network pro- acterizing the performance of a significant selection of tocols.
    [Show full text]
  • Release Notes for Xfree86® 4.8.0 the Xfree86 Project, Inc December 2008
    Release Notes for XFree86® 4.8.0 The XFree86 Project, Inc December 2008 Abstract This document contains information about the various features and their current sta- tus in the XFree86 4.8.0 release. 1. Introduction to the 4.x Release Series XFree86 4.0 was the first official release of the XFree86 4 series. The current release (4.8.0) is the latest in that series. The XFree86 4.x series represents a significant redesign of the XFree86 X server,with a strong focus on modularity and configurability. 2. Configuration: aQuickSynopsis Automatic configuration was introduced with XFree86 4.4.0 which makes it possible to start XFree86 without first creating a configuration file. This has been further improved in subsequent releases. If you experienced any problems with automatic configuration in a previous release, it is worth trying it again with this release. While the initial automatic configuration support was originally targeted just for Linux and the FreeBSD variants, as of 4.5.0 it also includes Solaris, NetBSD and OpenBSD support. Full support for automatic configuration is planned for other platforms in futurereleases. If you arerunning Linux, FreeBSD, NetBSD, OpenBSD, or Solaris, try Auto Configuration by run- ning: XFree86 -autoconfig If you want to customise some things afterwards, you can cut and paste the automatically gener- ated configuration from the /var/log/XFree86.0.log file into an XF86Config file and make your customisations there. If you need to customise some parts of the configuration while leav- ing others to be automatically detected, you can combine a partial static configuration with the automatically detected one by running: XFree86 -appendauto If you areusing a platform that is not currently supported, then you must try one of the older methods for getting started like "xf86cfg", which is our graphical configuration tool.
    [Show full text]
  • Proceedings of the FREENIX Track: 2002 USENIX Annual Technical Conference
    USENIX Association Proceedings of the FREENIX Track: 2002 USENIX Annual Technical Conference Monterey, California, USA June 10-15, 2002 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2002 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. XCL : An Xlib Compatibility Layer For XCB Jamey Sharp Bart Massey Computer Science Department Portland State University Portland, Oregon USA 97207–0751 fjamey,[email protected] Abstract 1 The X Window System The X Window System [SG86] is the de facto standard technology for UNIX applications wishing to provide a graphical user interface. The power and success of the X model is due in no small measure to its separation of The X Window System has provided the standard graph- hardware control from application logic with a stable, ical user interface for UNIX systems for more than 15 published client-server network protocol. In this model, years. One result is a large installed base of X applica- the hardware controller is considered the server, and in- tions written in C and C++. In almost all cases, these dividual applications and other components of a com- programs rely on the Xlib library to manage their inter- plete desktop environment are clients.
    [Show full text]
  • Sun Ray Server Software 4.2 Administration Guide
    Sun Ray Server Software 4.2 Administration Guide April 2011 Sun Ray Server Software 4.2 Administration Guide Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • New Evolutions in the X Window System
    New Evolutions in the X Window System Matthieu Herrb∗ and Matthias Hopf† October 2005 Abstract This paper presents an overview of recent and on-going evolutions in the X window system. First, the state of some features will be presented that are already available for several months in the X server, but not yet widely used in applications. Then some ongoing and future evolutions will be shown: on the short term, the new EXA acceleration framework and the new modular- ized build system. The last part will focus on a longer term project: the new Xgl server architecture, based on the OpenGL technology for both 2D and 3D acceleration. Introduction The X window system celebrated its twentieth birthday last year. After some quick evolution in its early years, its development slowed down during the nineties, be- cause the system had acquired a level of maturity that made it fit most of the needs of the users of graphical work stations. But after all this time, pushed by the com- petition with other systems (Mac OS X and Microsoft Windows) the need for more advanced graphics features triggered new developments. The first part of this paper is going to describe some of these features that are already available (and have been used) for a couple of years but not necessarily known by users of the X window system. A second part will address some on-going work that will be part of the X11R7 release: a new 2D acceleration architecture and the modularization of the source tree. In the third part, a complete redesign of the device dependent layer of the X server, based on OpenGL, will be presented.
    [Show full text]
  • R 3.1 Open Source Packages
    R 3.1 Open Source Packages Package Version Purpose accountsservice 0.6.15-2ubuntu9.3 query and manipulate user account information acpid 1:2.0.10-1ubuntu3 Advanced Configuration and Power Interface event daemon adduser 3.113ubuntu2 add and remove users and groups apport 2.0.1-0ubuntu12 automatically generate crash reports for debugging apport-symptoms 0.16 symptom scripts for apport apt 0.8.16~exp12ubuntu10.27 commandline package manager aptitude 0.6.6-1ubuntu1 Terminal-based package manager (terminal interface only) apt-utils 0.8.16~exp12ubuntu10.27 package managment related utility programs apt-xapian-index 0.44ubuntu5 maintenance and search tools for a Xapian index of Debian packages at 3.1.13-1ubuntu1 Delayed job execution and batch processing authbind 1.2.0build3 Allows non-root programs to bind() to low ports base-files 6.5ubuntu6.2 Debian base system miscellaneous files base-passwd 3.5.24 Debian base system master password and group files bash 4.2-2ubuntu2.6 GNU Bourne Again Shell bash-completion 1:1.3-1ubuntu8 programmable completion for the bash shell bc 1.06.95-2 The GNU bc arbitrary precision calculator language bind9-host 1:9.8.1.dfsg.P1-4ubuntu0.16 Version of 'host' bundled with BIND 9.X binutils 2.22-6ubuntu1.4 GNU assembler, linker and binary utilities bsdmainutils 8.2.3ubuntu1 collection of more utilities from FreeBSD bsdutils 1:2.20.1-1ubuntu3 collection of more utilities from FreeBSD busybox-initramfs 1:1.18.5-1ubuntu4 Standalone shell setup for initramfs busybox-static 1:1.18.5-1ubuntu4 Standalone rescue shell with tons of built-in utilities bzip2 1.0.6-1 High-quality block-sorting file compressor - utilities ca-certificates 20111211 Common CA certificates ca-certificates-java 20110912ubuntu6 Common CA certificates (JKS keystore) checkpolicy 2.1.0-1.1 SELinux policy compiler command-not-found 0.2.46ubuntu6 Suggest installation of packages in interactive bash sessions command-not-found-data 0.2.46ubuntu6 Set of data files for command-not-found.
    [Show full text]
  • Distributed Multihead X Design Kevin E
    Distributed Multihead X design Kevin E. Martin, David H. Dawes, and RickardE.Faith 29 June 2004 (created 25 July 2001) Abstract This document covers the motivation, background, design, and implementation of the distributed multihead X (DMX) system. It is a living document and describes the current design and implementation details of the DMX system. As the project pro- gresses, this document will be continually updated to reflect the changes in the code and/or design. Copyright 2001 by VALinux Systems, Inc., Fremont, California. Copyright 2001-2004 by Red Hat, Inc., Raleigh, North Carolina 1. Introduction 1.1 The Distributed Multihead X Server Current Open Source multihead solutions arelimited to a single physical machine. Asingle X server controls multiple display devices, which can be arranged as independent heads or unified into a single desktop (with Xinerama). These solutions arelimited to the number of physical devices that can co-exist in a single machine (e.g., due to the number of AGP/PCI slots available for graphics cards). Thus, large tiled displays arenot currently possible. The work described in this paper will eliminate the requirement that the display devices reside in the same physical machine. This will be accomplished by developing a front-end proxy X server that will control multiple back-end X servers that make up the large display. The overall structureofthe distributed multihead X (DMX) project is as follows: A single front- end X server will act as a proxy to a set of back-end X servers, which handle all of the visible ren- dering. X clients will connect to the front-end server just as they normally would to a regular X server.
    [Show full text]
  • SECUMOBI SERVER Technical Description
    SECUMOBI SERVER Technical Description Contents SIP Server 3 Media Relay 10 Dimensioning of the Hardware 18 SIP server 18 Media Proxy 18 Page 2 of 18 SIP Server Operatingsystem: Debian https://www.debian.org/ Application: openSIPS http://www.opensips.org/ OpenSIPS is built and installed from source code. The operating system is installed with the following packages: Package Description acpi displays information on ACPI devices acpi-support-base scripts for handling base ACPI events such as the power button acpid Advanced Configuration and Power Interface event daemon adduser add and remove users and groups anthy-common input method for Japanese - common files and dictionary apt Advanced front-end for dpkg apt -utils APT utility programs aptitude terminal-based package manager (terminal interface only) autopoint The autopoint program from GNU gettext backup -manager command -line backup tool base-files Debian base system miscellaneous files base-passwd Debian base system master password and group files bash The GNU Bourne Again SHell bc The GNU bc arbitrary precision calculator language binutils The GNU assembler, linker and binary utilities bison A parser generator that is compatible with YACC bsdmainutils collection of more utilities from FreeBSD bsdutils Basic utilities from 4.4BSD-Lite build -essential Informational list of build -essential packages busybox Tiny utilities for small and embedded systems bzip2 high-quality block-sorting file compressor - utilities ca-certificates Common CA certificates console-setup console font and keymap
    [Show full text]
  • Remote Visualisation Using Open Source Software & Commodity
    Remote visualisation using open source software & commodity hardware Dell/Cambridge HPC Solution Centre Dr Stuart Rankin, Dr Paul Calleja, Dr James Coomer © Dell Abstract It is commonplace today that HPC users produce large scale multi-gigabyte data sets on a daily basis and that these data sets may require interactive post processing with some form of real time 3D or 2D visualisation in order to help gain insight from the data. The traditional HPC workflow process requires that these data sets be transferred back to the user’s workstation, remote from the HPC data centre over the wide area network. This process has several disadvantages, firstly it requires large I/O transfers out of the HPC data centre which is time consuming, also it requires that the user has significant local disk storage and a workstation setup with the appropriate visualisation software and hardware. The remote visualisation procedures described here removes the need to transfer data out of the HPC data centre. The procedure allows the user to logon interactively to the Dell | NVIDIA remote visualisation server within the HPC data centre and access their data sets directly from the HPC file system and then run the visualisation software on the remote visualisation server in the machine room, sending the visual output over the network to the users remote PC. The visualisation server consists of a T5500 Dell Precision Workstation equipped with a NVIDIA Quadro FX 5800 configured with an open source software stack facilitating sending of the visual output to the remote user. The method described in this whitepaper is an OS-neutral extension of familiar remote desktop techniques using open-source software and it imposes only modest demands on the customer machine and network connection.
    [Show full text]