VSim System Requirements¶
Operating System¶
VSim runs on 64-bit Windows, Linux, and Mac and has installation procedures that users will be familiar with on their respective operating system. Some of the systems supported are:
Windows 10, Server 2019
Linux distributions with glibc 2.17 or later (verified on Fedora/RedHat/CentOS, SUSE, Ubuntu)
Mac OS X Mojave, Catalina, and Big Sur
Cray XC30
Note
The version of glibc can be found with the command: ldd –version
Memory¶
Usage of RAM varies with the computational problem size, but with a minimum of 16 GB will run most all examples as described in the documentation. Examples like the Smith Purcell examples will use more than 16 GB, so a more liberal estimate would be 32 GB, but of course any heavy computation could require more.
Graphics Rendering¶
The visualization in VSim uses OpenGL and requires optimal graphics drivers that support OpenGL 3.2. The standard Linux distributions may not come with drivers written by the graphics-card manufacturer, which are necessary for full hardware acceleration. You should download and install the latest driver for your graphics card from your graphics card vendor’s website. In the case of an NVidia graphics card, you can get the latest driver by going to NVidia’s website, selecting the Download Drivers link, and then selecting the Linux Display Drivers link.
Note
There is a known visualization issue on certain Linux laptops, when Desktop Scaling is set to non-integer scaling values. For example 100% & 200% are ok, but fractional values like 175% (scaling of 1.75) can cause display artifacts in the visualize tab.
Note
There is a known Windows-OpenGL issue when using VSim over a Microsoft Remote Desktop connection where the application window appears blank on some Windows machines with some graphics cards or some drivers. We provide a RemoteVSimComposer.bat script to work around this issue. It disconnects the remote session and starts VSim while disconnected, so that when the user reconnects, VSim works properly. If you see this issue, launch this script by right-clicking on RemoteVSimComposer.bat and choose “Run as administrator”.
On Windows systems using high resolution screens that high DPI (dots-per-inch), poor sizing can occur where fonts are small or panels are cut off. This can be remedied by overriding the scaling behavoir performed by the system. The figure belows shows how to override this scaling by setting a properties of the Composer executable.
Fig. 1 How to override system high DPI scaling on Windows.¶
Disk Space¶
The VSim 11 Windows installer is around 536MB, and requires around 1.5GB of disk space to install. The Linux installer is 992MB due to the inclusion of additional system packages, and unpacks into around 3.3GB. Please ensure you have enough additional space to run your simulations.
Windows Performance¶
VSim performance on Windows compared to Linux can be significantly limited by power settings. If the power setting was on “balanced,” which is the default even on a desktop or server, Windows will limit CPU utilization when VSim is running, i.e. Windows will not allow VSim to take all the CPU resource. To overcome the limitation, change the power settings under “Control Panel -> System and Security -> Power Options -> Preferred plans” to “High performance.”
Large Scale And Accelerated Computing¶
The VSim serial engine (vorpalser) is available for running on single processor workstations. The VSim parallel engine (vorpal) is provided for multi-core systems that support the Message Passing Interface (MPI). There is support for running VSim simulations on Linux clusters with common job schedulers as well as running with the “Windows Clustering” server technology.
VSim is licensed per compute platform, which may be a workstation or a cluster. For a workstation, creating a license requires the MAC (hardware) address.
A cluster is defined to be “A dynamic collection of compute nodes sharing a common filesystem and a single common queuing system.” For a cluster, all nodes be able to determine their own hardware (or MAC) address and hostname. For a cluster, we also require that there is a method available from each compute node that can determine the list of compute nodes from the queuing system given to us by the customer. If the customer wants the capability to dynamically change the size of the cluster after licensing, then we require that the compute nodes be able to remote-shell-connect to each other. If a job is running on a collection of nodes, any one of which is licensed, and all of which can see the shared filesystem and are in the nodes list from the queuing system, then we consider the job to be running on the licensed cluster. Otherwise, if one or more job nodes can reach one the licensed nodes and can validate it, and all of the nodes can see the shared filesystem and are in the nodes list from the queuing system, then we also consider the job to be running on the licensed cluster.
VSim is highly scalable, and has been developed to solve the most challenging computational electromagnetics problems of our time. Some example calculations, particularly for plasma acceleration, require a supercomputer to run adequately in 3D, though VSim desktop users may explore how the files work by running them in 2D. Some microwave device examples, such as the Smith Purcell Radiation example, require 12GB RAM or more to run. However, it is possible to set up an input file at lower resolution if you have limited resources.
For large parallel simulations running across nodes in high performance cluster, there are some requirements that can worked out easily with system administrators and depend on the details of the cluster configurations. In general, we don’t recommend running VSim on AFS file systems.
Note
The Andrew File System (AFS) is not recommended to run VSim in parallel. The distributed AFS system is optimized for location-transparency over a wide area network rather than the low-latency conditions necessary for high performance in cluster storage. File systems such as Lustre or the General Parallel File System (GPFS) perform better when running VSim.
For installation instructions see: VSim Installation Instructions