Archive Trac getting

Getting

Legacy Trac archive page imported from getting. Source: https://genapp.rocks/wiki/wiki/getting. Review age, links, and examples before treating as current.

Here are some notes to help one get started.

On the machine sassie2 (ssh ​ then ssh to sassie2)

• You have the following directories and files. A short description of each is provided below the name of the directory or file.

  • bin/

    Contains the directory that holds the executable files. It currently holds perl scripts that accept json formatted input directly from the web page, perform functions, and returns json formatted data back to the web page. The functions currently are to show how the various widgets are used. In the future the perl scripts will be replaced with python scripts that do the same json input/output and call sassie code and capture output from sassie etc.

  • directives.json

    This file contains options for configuring the web application in general.

  • menu.json

    This file contains the main sassie menu that calls the various module json files located in the modules/ directory.

  • modules/

    This directory contains the specific json files that handle the layout for each module web-page.

  • output/

    This directory contains the latest "build" of the sassie web page. This is updated when one runs the genapp.pl script.

  • pngs/

    This directory contains the graphic files for the web page.

The idea is to edit the layout files (directive.json, menu.json and modules/.json) and executable scripts (bin/) to link the web application layer to the python sassie layer.

• After editing files one updates the current web page for the server (and hence the files in output/) by typing

genapp.pl

at the command line.

Server information

services: idrac 160.36.200.10 ups 10.1.2.5

Master: PowerEdge R320 : service tag 24DTFZ1 : ETH1: F0:1F:AF:E4:B6:C7 (160.36.200.2)

10.1.2.1: (old idrac) (160.36.200.10)

Belkin: F1DC108H

UPS: 3750W

10.1.2.2: compute-0-0 10.1.2.3: compute-0-1

mobile entropy notes:

DELL Precision T5400

Stag: DK6FBK1

CentOS 6.6

Kernel Linux 2.6.32-504.16.2.el6.x86_64

Gnome 2.28.2

32 GB RAM 8 Intel Xeon CPU E5420 @ 2.5 GHz TWO NVIDIA Corporation GK107 [GeForce GTX 650] GPU cards

bin/x86_64/linux/release/deviceQuery Starting...

CUDA Device Query (Runtime API) version (CUDART static linking)

Detected 2 CUDA Capable device(s)

Device 0: "GeForce GTX 650" CUDA Driver Version / Runtime Version 6.5 / 6.5 CUDA Capability Major/Minor version number: 3.0 Total amount of global memory: 1024 MBytes (1073545216 bytes) ( 2) Multiprocessors, (192) CUDA Cores/MP: 384 CUDA Cores GPU Clock rate: 1058 MHz (1.06 GHz) Memory Clock rate: 2500 Mhz Memory Bus Width: 128-bit L2 Cache Size: 262144 bytes Maximum Texture Dimension Size (x,y,z) 1D=(65536), 2D=(65536, 65536), 3D=(4096, 4096, 4096) Maximum Layered 1D Texture Size, (num) layers 1D=(16384), 2048 layers Maximum Layered 2D Texture Size, (num) layers 2D=(16384, 16384), 2048 layers Total amount of constant memory: 65536 bytes Total amount of shared memory per block: 49152 bytes Total number of registers available per block: 65536 Warp size: 32 Maximum number of threads per multiprocessor: 2048 Maximum number of threads per block: 1024 Max dimension size of a thread block (x,y,z): (1024, 1024, 64) Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535) Maximum memory pitch: 2147483647 bytes Texture alignment: 512 bytes Concurrent copy and kernel execution: Yes with 1 copy engine(s) Run time limit on kernels: No Integrated GPU sharing Host Memory: No Support host page-locked memory mapping: Yes Alignment requirement for Surfaces: Yes Device has ECC support: Disabled Device supports Unified Addressing (UVA): Yes Device PCI Bus ID / PCI location ID: 1 / 0 Compute Mode: < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

Device 1: "GeForce GTX 650" CUDA Driver Version / Runtime Version 6.5 / 6.5 CUDA Capability Major/Minor version number: 3.0 Total amount of global memory: 1023 MBytes (1073020928 bytes) ( 2) Multiprocessors, (192) CUDA Cores/MP: 384 CUDA Cores GPU Clock rate: 1058 MHz (1.06 GHz) Memory Clock rate: 2500 Mhz Memory Bus Width: 128-bit L2 Cache Size: 262144 bytes Maximum Texture Dimension Size (x,y,z) 1D=(65536), 2D=(65536, 65536), 3D=(4096, 4096, 4096) Maximum Layered 1D Texture Size, (num) layers 1D=(16384), 2048 layers Maximum Layered 2D Texture Size, (num) layers 2D=(16384, 16384), 2048 layers Total amount of constant memory: 65536 bytes Total amount of shared memory per block: 49152 bytes Total number of registers available per block: 65536 Warp size: 32 Maximum number of threads per multiprocessor: 2048 Maximum number of threads per block: 1024 Max dimension size of a thread block (x,y,z): (1024, 1024, 64) Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535) Maximum memory pitch: 2147483647 bytes Texture alignment: 512 bytes Concurrent copy and kernel execution: Yes with 1 copy engine(s) Run time limit on kernels: Yes Integrated GPU sharing Host Memory: No Support host page-locked memory mapping: Yes Alignment requirement for Surfaces: Yes Device has ECC support: Disabled Device supports Unified Addressing (UVA): Yes Device PCI Bus ID / PCI location ID: 2 / 0 Compute Mode: < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

Peer access from GeForce GTX 650 (GPU0) -> GeForce GTX 650 (GPU1) : No Peer access from GeForce GTX 650 (GPU1) -> GeForce GTX 650 (GPU0) : No

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 6.5, CUDA Runtime Version = 6.5, NumDevs = 2, Device0 = GeForce GTX 650, Device1 = GeForce GTX 650 Result = PASS

Upon rebooting ... login to compute node as root (sudo on entropy)

cp /share/apps/local/cuda_6.5_compute.tar.gz /usr/local cd /usr/local tar -xvzf cuda_6.5_compute.tar.gz ln -s cuda-6.5 cuda