<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://dokuwiki.wesleyan.edu/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://dokuwiki.wesleyan.edu/feed.php">
        <title>DokuWiki - cluster</title>
        <description></description>
        <link>https://dokuwiki.wesleyan.edu/</link>
        <image rdf:resource="https://dokuwiki.wesleyan.edu/lib/exe/fetch.php?media=wiki:dokuwiki-128.png" />
       <dc:date>2026-05-21T15:28:51+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:0&amp;rev=1770497756&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:1&amp;rev=1166037762&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:2&amp;rev=1179249147&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:3&amp;rev=1487099238&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:4&amp;rev=1165518625&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:5&amp;rev=1165518501&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:6&amp;rev=1165518673&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:7&amp;rev=1576244602&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:8&amp;rev=1166558393&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:9&amp;rev=1165518755&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:10&amp;rev=1165527581&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:11&amp;rev=1171983056&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:12&amp;rev=1192720684&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:13&amp;rev=1166562194&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:14&amp;rev=1166900271&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:15&amp;rev=1166624344&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:16&amp;rev=1167772997&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:17&amp;rev=1168440202&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:18&amp;rev=1176213106&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:19&amp;rev=1176213256&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:20&amp;rev=1170253883&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:21&amp;rev=1183057683&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:22&amp;rev=1170434132&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:23&amp;rev=1507037672&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:24&amp;rev=1172494637&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:25&amp;rev=1175610944&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:26&amp;rev=1177010929&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:27&amp;rev=1198187315&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:28&amp;rev=1392999810&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:29&amp;rev=1252437321&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:30&amp;rev=1188570272&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:31&amp;rev=1177011947&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:32&amp;rev=1179329247&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:33&amp;rev=1278630854&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:34&amp;rev=1179345511&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:35&amp;rev=1252437093&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:36&amp;rev=1205779469&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:37&amp;rev=1179249181&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:38&amp;rev=1247499179&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:39&amp;rev=1506691194&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:40&amp;rev=1185464986&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:41&amp;rev=1192633914&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:42&amp;rev=1186692482&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:43&amp;rev=1186758650&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:44&amp;rev=1189694225&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:45&amp;rev=1188223122&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:46&amp;rev=1190217176&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:47&amp;rev=1189111391&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:48&amp;rev=1222367390&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:49&amp;rev=1375988869&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:50&amp;rev=1304960549&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:51&amp;rev=1191005825&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:52&amp;rev=1195571918&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:53&amp;rev=1486653269&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:54&amp;rev=1192839795&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:55&amp;rev=1194026986&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:56&amp;rev=1194361707&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:57&amp;rev=1193927025&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:58&amp;rev=1221837905&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:59&amp;rev=1199905455&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:60&amp;rev=1213885258&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:61&amp;rev=1198681450&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:62&amp;rev=1198264081&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:63&amp;rev=1203957835&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:64&amp;rev=1200001375&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:65&amp;rev=1212514042&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:66&amp;rev=1214683171&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:67&amp;rev=1214769080&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:68&amp;rev=1219167251&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:69&amp;rev=1224687261&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:70&amp;rev=1239887501&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:71&amp;rev=1230051037&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:72&amp;rev=1245254011&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:73&amp;rev=1756492899&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:74&amp;rev=1237576609&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:75&amp;rev=1239297932&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:76&amp;rev=1239888443&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:77&amp;rev=1252502487&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:78&amp;rev=1247086470&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:79&amp;rev=1366314047&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:80&amp;rev=1251471412&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:81&amp;rev=1291909609&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:82&amp;rev=1296763734&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:83&amp;rev=1284475226&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:84&amp;rev=1272897743&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:85&amp;rev=1277303279&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:86&amp;rev=1273775382&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:87&amp;rev=1274302517&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:88&amp;rev=1282074964&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:89&amp;rev=1290452713&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:90&amp;rev=1285705974&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:91&amp;rev=1294433373&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:92&amp;rev=1301500776&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:93&amp;rev=1294779358&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:94&amp;rev=1295973572&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:95&amp;rev=1374678031&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:96&amp;rev=1426269173&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:97&amp;rev=1329419381&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:98&amp;rev=1313768167&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:99&amp;rev=1300721786&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:100&amp;rev=1301322202&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:101&amp;rev=1326898142&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:102&amp;rev=1598267968&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:103&amp;rev=1324582469&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:104&amp;rev=1326309658&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:105&amp;rev=1354215776&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:106&amp;rev=1479759767&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:107&amp;rev=1378905534&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:108&amp;rev=1392996336&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:109&amp;rev=1381950833&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:110&amp;rev=1369402757&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:111&amp;rev=1360006122&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:112&amp;rev=1381259043&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:113&amp;rev=1391447289&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:114&amp;rev=1378839598&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:115&amp;rev=1378839843&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:116&amp;rev=1391540233&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:117&amp;rev=1374590789&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:118&amp;rev=1377197887&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:119&amp;rev=1623958367&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:120&amp;rev=1392996279&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:121&amp;rev=1379344140&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:122&amp;rev=1380652255&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:123&amp;rev=1382554322&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:124&amp;rev=1457727297&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:125&amp;rev=1393446749&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:126&amp;rev=1763827695&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:127&amp;rev=1396878513&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:128&amp;rev=1401219091&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:129&amp;rev=1403100272&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:130&amp;rev=1507039662&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:131&amp;rev=1429020970&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:132&amp;rev=1407766129&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:133&amp;rev=1426703181&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:134&amp;rev=1408712719&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:135&amp;rev=1554988204&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:136&amp;rev=1595956885&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:137&amp;rev=1560358826&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:138&amp;rev=1466532672&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:139&amp;rev=1534424292&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:140&amp;rev=1449255200&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:141&amp;rev=1452708321&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:142&amp;rev=1582811943&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:143&amp;rev=1449779768&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:144&amp;rev=1532631173&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:145&amp;rev=1491405768&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:146&amp;rev=1504013773&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:147&amp;rev=1582826808&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:148&amp;rev=1579891009&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:149&amp;rev=1481055197&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:150&amp;rev=1480448189&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:151&amp;rev=1481055243&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:152&amp;rev=1485531375&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:153&amp;rev=1512574492&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:154&amp;rev=1534510139&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:155&amp;rev=1491395703&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:156&amp;rev=1491403373&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:157&amp;rev=1491507119&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:158&amp;rev=1490793488&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:159&amp;rev=1490816374&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:160&amp;rev=1496243269&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:161&amp;rev=1594919783&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:162&amp;rev=1504722963&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:163&amp;rev=1559063599&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:164&amp;rev=1537531170&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:165&amp;rev=1516115771&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:166&amp;rev=1530100260&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:167&amp;rev=1533132684&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:168&amp;rev=1537710834&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:169&amp;rev=1604604684&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:170&amp;rev=1552932716&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:171&amp;rev=1534773308&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:172&amp;rev=1594835571&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:173&amp;rev=1553515455&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:174&amp;rev=1535459902&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:175&amp;rev=1543514430&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:176&amp;rev=1551900551&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:177&amp;rev=1552056520&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:178&amp;rev=1693860396&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:179&amp;rev=1561729402&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:180&amp;rev=1564599368&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:181&amp;rev=1565698533&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:182&amp;rev=1576243989&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:183&amp;rev=1729019833&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:184&amp;rev=1578057777&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:185&amp;rev=1582826722&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:186&amp;rev=1576244190&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:187&amp;rev=1597665663&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:188&amp;rev=1576508179&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:189&amp;rev=1707756462&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:190&amp;rev=1601293111&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:191&amp;rev=1579901762&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:192&amp;rev=1646764160&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:193&amp;rev=1726591917&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:194&amp;rev=1754398824&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:195&amp;rev=1595700549&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:196&amp;rev=1605019437&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:197&amp;rev=1598539143&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:198&amp;rev=1607000999&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:199&amp;rev=1607716307&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:200&amp;rev=1613673188&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:201&amp;rev=1608996797&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:202&amp;rev=1634756515&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:203&amp;rev=1615405588&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:204&amp;rev=1694805167&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:205&amp;rev=1621857591&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:206&amp;rev=1625753899&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:207&amp;rev=1698432479&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:208&amp;rev=1667410112&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:209&amp;rev=1649620159&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:210&amp;rev=1641222879&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:211&amp;rev=1646153438&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:212&amp;rev=1646246449&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:213&amp;rev=1771534466&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:214&amp;rev=1692375593&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:215&amp;rev=1765379258&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:216&amp;rev=1654632458&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:217&amp;rev=1656078796&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:218&amp;rev=1750347824&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:219&amp;rev=1668607317&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:220&amp;rev=1719845438&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:221&amp;rev=1678802358&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:222&amp;rev=1678111693&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:223&amp;rev=1695070609&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:224&amp;rev=1705070176&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:225&amp;rev=1716300402&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:226&amp;rev=1778170482&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:227&amp;rev=1729685785&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:228&amp;rev=1763391323&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:229&amp;rev=1740077670&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:230&amp;rev=1742845065&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:231&amp;rev=1762529519&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:232&amp;rev=1769722567&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:tmp&amp;rev=1175632235&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://dokuwiki.wesleyan.edu/lib/exe/fetch.php?media=wiki:dokuwiki-128.png">
        <title>DokuWiki</title>
        <link>https://dokuwiki.wesleyan.edu/</link>
        <url>https://dokuwiki.wesleyan.edu/lib/exe/fetch.php?media=wiki:dokuwiki-128.png</url>
    </image>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:0&amp;rev=1770497756&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-02-07T20:55:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>0</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:0&amp;rev=1770497756&amp;do=diff</link>
        <description>High Performance Compute Cluster

At Wesleyan University, Middletown, CT

	*  HPCC  Funding Acknowledgements  
	*  the  Brief User Guide &amp; Introduction,  continuously updated ... 
	*  the   Structure, History, Funding &amp; Priority Policies 
	*  the  endless   Software list  ... (CentOS 5&amp;6&amp;7)
	*  the OpenHPC  Software list  ... (Rocky 8)

this will be a chronological archive of our progress</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:1&amp;rev=1166037762&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-13T19:22:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>1</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:1&amp;rev=1166037762&amp;do=diff</link>
        <description>Home

Some details about the proposed cluster

	*       The cluster will be initially funded by an NSF grant.

	*       The cluster is expected to generate large savings for Wesleyan over its lifetime. The University Cluster will reduce or eliminate the need for new individual faculty clusters.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:2&amp;rev=1179249147&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-15T17:12:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>2</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:2&amp;rev=1179249147&amp;do=diff</link>
        <description>Home

Cluster Steering Committee (12/1/2006)

	*  Eric Aaron &lt;http://eaaron.web.wesleyan.edu/&gt;

	*  David Beveridge &lt;http://dbeveridge.web.wesleyan.edu/&gt;

	*  Tsampikos Kottos

	*  George Petersson

	*  Francis Starr &lt;http://fstarr.web.wesleyan.edu/&gt;



Home</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:3&amp;rev=1487099238&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-02-14T19:07:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>3</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:3&amp;rev=1487099238&amp;do=diff</link>
        <description>Home

Usage Survey (circa early Nov 2006)

Brief synopsis of emerging themes

	*  some commercial software will have to be bought outside of the grant: Matlab, Linda and Portland compilers
	*  most current code is “coarse grain” parallel (meaning split a big problem into tiny pieces) rather than</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:4&amp;rev=1165518625&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-07T19:10:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>4</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:4&amp;rev=1165518625&amp;do=diff</link>
        <description>Home

Cluster Configuration

In general, the cluster configuration should remain as “standard” as possible; this is not be a bleeding edge venture.  

Some general information gleaned from our anticipated user base:

	*  Software: mostly home grown code, C/C++ and Fortran programs (probably a Portland suite of compilers), Matlab (and MatlabMPI), AMBER, NAMD, CHARMM, and Gaussian.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:5&amp;rev=1165518501&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-07T19:08:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>5</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:5&amp;rev=1165518501&amp;do=diff</link>
        <description>Home

Description of Quotes (Nov-Dec 2006)

A final round of quoting is underway now (about 8 months later) to settle on a vendor and configuration.  Because of the time that&#039;s passed, all the chipsets have changed, so it&#039;s essentially a new round, rather than some type of clarification.  Dell has offered a quote but it came in too high, and they agreed to offer a revision. Sun&#039;s quote is due today (12/1/06) and may come very close to the target price (roughly $190,000). We have received a quote…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:6&amp;rev=1165518673&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-07T19:11:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>6</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:6&amp;rev=1165518673&amp;do=diff</link>
        <description>Home

Academic UNIX Support Specialist

Job Description

JOB TITLE: Academic UNIX Support Specialist

----------

DEPARTMENT: Information Technology Services

----------

GRADE: ?

----------

RANGE: $?

----------

TYPICAL DUTIES:  Reporting to the Assistant Director of Technology Support Services with management support from the Manager of Academic Computing for Natural Sciences and Mathematics, the Academic UNIX Support Specialist will provide systems support to the user community.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:7&amp;rev=1576244602&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-13T13:43:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>7</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:7&amp;rev=1576244602&amp;do=diff</link>
        <description>Home

TITLE OF PROPOSED PROJECT

“Acquisition of Cluster Computing Facilities for Research and Education at Wesleyan University”

NATIONAL SCIENCE FOUNDATION PROPOSAL AUTHORS

	*  Francis W Starr
	*  David L Beveridge
	*  Kathryn V Johnston

PROJECT SUMMARY</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:8&amp;rev=1166558393&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-19T19:59:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>8</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:8&amp;rev=1166558393&amp;do=diff</link>
        <description>Home

Description of Quotes (Dec 06)

vendor #1
Quote 1#140 node HPCC $188,700Nodes a total of 40 nodes, 80 cpus, 160 cores, 48 port switch 36 Xeon, 2*(Dual Core 5148LV 2.3 Ghz), 2 Gb@667Mhzdual 80 Gb 7.2K RPM Satalight, 144 cores 04 Xeon, 2*(Dual Core 5160, 3.0 Ghz), 16 Gb@667Mhz</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:9&amp;rev=1165518755&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-07T19:12:35+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>9</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:9&amp;rev=1165518755&amp;do=diff</link>
        <description>Home

Integer &amp; Floating Benchmarks

pulled from &lt;http://www.spec.org&gt;, the SPEC2000 Results Page ...

Integer and Floating Point processing benchmarks.

	*  “speed” is relatively measured with the “results” column
		*  “throughput” is relatively measured with the</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:10&amp;rev=1165527581&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-07T21:39:41+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>10</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:10&amp;rev=1165527581&amp;do=diff</link>
        <description>Home

Target config




lightweight nodes (40 3.0 ghz or 60 2.0 ghz)  (160 or 240 cores)

	*  2gb RAM
	*  single HD
	*  two dual-core processors (high efficiency for opteron)



4 heavyweight nodes (32 cores)

	*  2 with 16gb RAM 2 with 32gb RAM
	*  single HD</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:11&amp;rev=1171983056&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-20T14:50:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>11</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:11&amp;rev=1171983056&amp;do=diff</link>
        <description>Home

What is ROCKS or Platform/ROCKS?

(no idea what the acronym, if any, stands for)
ROCKSPlatform Rocks:-o ROCKS is an open-source software stack that enables the consistent delivery of scale-out application clusters :-O Platform Open Cluster Stack (OCS) is a pre-integrated, vendor certified, software stack that enables the consistent delivery of scale-out application clusters using ROCKS</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:12&amp;rev=1192720684&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-10-18T15:18:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>12</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:12&amp;rev=1192720684&amp;do=diff</link>
        <description>Home

HPC: Will it fly?


The attendance at the UUG meetings so far has been very disappointing.  It&#039;s apparent that the V charisma was a horizontal penetration of the market place so to speak with little vertical leverage.  The sun has set beyond the horizon, alumnification has set in.  Now what?  We need departmental admins to show up and others in charge of maintaining unix machines on campus.  We have a solid group of ITS folks showing up so this could be a real resource for those attending.…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:13&amp;rev=1166562194&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-19T21:03:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>13</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:13&amp;rev=1166562194&amp;do=diff</link>
        <description>Home

Down to 2 Vendors (Dec 06)

vendor #1
Quote 1#164 node HPCC $196,700Nodes a total of 64 nodes, 128 cpus, 272 cores 60 Xeon, 2*(Dual Core 5130 2.0 Ghz), 2 Gb@667Mhzdual 80 Gb 7.2K RPM Satalight, 240 cores 04 Xeon, 2*(Quad Core 5355, 2.6 Ghz), 16 Gb@667Mhz</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:14&amp;rev=1166900271&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-23T18:57:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>14</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:14&amp;rev=1166900271&amp;do=diff</link>
        <description>Home

Final Configuration &amp; Quote (yea!)



At Last ... in time for Christmas Lights?

	*  via Platform/Rocks technical support: PBS/LSF currently can manage jobs at the core unit for dual core processors.  It is expected that in Q1 of 2007, PBS/LSF will support scheduling jobs at the core unit for quad core processors.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:15&amp;rev=1166624344&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-20T14:19:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>15</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:15&amp;rev=1166624344&amp;do=diff</link>
        <description>Home

Scali/Manage

	*  &lt;http://www.scali.com&gt;



Like Platform/ROCKS (see link), Scali/Manage is a software suite of tools to manage clusters.  It appears very, very versatile.  Lots of stuff you can do but what attracted my interests in my brief perusals were:



	*  heterogeous clusters (as in, manage the other clsuters on campus</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:16&amp;rev=1167772997&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-02T21:23:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>16</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:16&amp;rev=1167772997&amp;do=diff</link>
        <description>Home

Useful Documentation
Platform Rocks &amp; Dell   Platform Rocks: A Cluster Software
Package for Dell HPC PlatformsAdministrators can employ cluster solution packages such as Platform Rocks to help deploy, maintain, and manage high-performance computing (HPC) clusters  Workload Management and Job Scheduling on Platform Rocks ClustersPlatform Lava, a free and fully functional entry-level workload manager for Platform Rocks, is becoming popular in the high-performance computing community</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:17&amp;rev=1168440202&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-10T14:43:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>17</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:17&amp;rev=1168440202&amp;do=diff</link>
        <description>Home

Webcast Demo of Platform/OCS by Platform Computing

William DeSalvo, from Platform Computing, did a webcast presentation about Platform/OCS ... the administrative software layer of our cluster design.  Several documents were obtained detailing administrative aspects of the Platform/OCS software stack (see below).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:18&amp;rev=1176213106&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-10T13:51:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>18</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:18&amp;rev=1176213106&amp;do=diff</link>
        <description>Home

Thoughts on Cluster Network / Future Growth

As i&#039;m working my way through some of the Platform/OCS documentation provided, some thoughts came up that i want to keep track of.  This page is not intended to detail how the cluster&#039;s final configuration will look like, but could act as a guideline. So first, the big picture.  Drawn in black is the cluster as ordered, drawn in green the connections if additional switches were bought, which leads to the red drawings, the additional nodes that c…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:19&amp;rev=1176213256&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-10T13:54:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>19</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:19&amp;rev=1176213256&amp;do=diff</link>
        <description>Home

HPCC 36 Node Design Conference with Dell

Questions/Issues

After the conference, with the erratic behavior of our freight elevator enlightening everybody, i think we have but a few questions to work on:
Question/IssuesAnswerShall we use the 2nd disk in the compute nodes as /localscratch?</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:20&amp;rev=1170253883&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-31T14:31:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>20</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:20&amp;rev=1170253883&amp;do=diff</link>
        <description>Home

Design Issues

These topics flowed out of our Design Conference with Dell, read about that on this page.

2nd disks
As Detailed In Cluster QuoteHard Drive:80GB, SATA, 3.5-inch 7.2K RPM Hard DriveAdditional Storage Products:80GB, SATA, 3.5-inch 7.2K RPM Hard Drive
	*  Shall we use the 2nd disk in the compute nodes as /localscratch?</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:21&amp;rev=1183057683&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-06-28T19:08:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>21</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:21&amp;rev=1183057683&amp;do=diff</link>
        <description>Home

SAN File Systems

The idea of managing very large file systems has certain implications.  For example

	*  a single point of failure (if the part of the file systems goes corrupt, does the entire file systems go off line?)
	*  fsck may take an excessive amount of time (one reference i found was 1 hour/TB for a clean file system, other references we&#039;ve seen is days for 1 TB in reference to a mail spool)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:22&amp;rev=1170434132&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-02T16:35:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>22</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:22&amp;rev=1170434132&amp;do=diff</link>
        <description>Home

Cluster Arrival Day ... 02/01/2007
Today5th floor. freight elevator out. project $ave or something. where am i?5 floors of stairs, that was hard. where are these characters?it&#039;s empty?oh,oh. it is! somebody stole our cluster?1,500 lbs, 288 cores.  this is going to hurt?</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:23&amp;rev=1507037672&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-10-03T13:34:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:23&amp;rev=1507037672&amp;do=diff</link>
        <description>Home

Towards Deployment

	*  I think i will close this page.  The one major outstanding issue standing in the way of declaring ourselves “in production” mode is a serious backup policy.  I&#039;m snapshotting via the NetApp filers but need Tivoli backups of home directories.  So lets close this page.  Once you see the</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:24&amp;rev=1172494637&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T12:57:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>24</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:24&amp;rev=1172494637&amp;do=diff</link>
        <description>Home

Daylight Savings Time &#039;07
IF YOU NEED ASSISTANCE PERFORMING THE SUGGESTED ACTIONS FOR LINUX, SOLARIS AND JAVA --- PLEASE EMAIL ACSUNIX@WESLEYAN.EDU --- THE STEPS OUTLINED BELOW ARE ... AT YOUR OWN RISK ...
Linux

How to do this will vary from distro to distro, and should be handled by your update mechanism (yum, up2date, aptitude, etc) and distro for you rather easily, but basically you need to update your zoneinfo with the new info (typically /usr/share/zoneinfo) and then make sure that /…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:25&amp;rev=1175610944&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-03T14:35:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>25</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:25&amp;rev=1175610944&amp;do=diff</link>
        <description>Back
Zebra Swallowtail from Enchanted Learning[zebra swallowtail]
Monday

Dell engineer Amol Choukekar arrives to do the final configuration of the cluster.  First we set up two consoles; one for walking by the compute nodes and one permanently connected to head node.  

Following that Amol embarks on undoing my handy work with the ethernet cables connected to the Dell switch. I had run the cables down the other side of the rack but this is also were the power cables are concentrated.  To avoid …</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:26&amp;rev=1177010929&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-19T19:28:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>26</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:26&amp;rev=1177010929&amp;do=diff</link>
        <description>Back

The production copy of OpenMPI is in /share/apps/openmpi-1.2.

 --- Henk Meij 2007/04/19 15:27

HPLinpack Runs

The purpose here is to rerun the HPLinpack benchmarks Amol ran while configuring the cluster.  
Before[Idle!]During[Heat!]Ooops[Burn!]
FAQ External Link

Problem Sizes

N calculation, for example:</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:27&amp;rev=1198187315&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-20T21:48:35+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>27</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:27&amp;rev=1198187315&amp;do=diff</link>
        <description>Back

&lt;html&gt;&lt;h1&gt;Production!&lt;/h1&gt;&lt;/html&gt;

We officially went into production when the backup policy was put in place.

Read about that here: Link

&lt;html&gt;&lt;h1&gt;Early - Bird Butterfly Access Period&lt;/h1&gt;&lt;/html&gt;

Until we officially deploy into production with all software installed and a formally stated backup policy of home directories; access is provided to all with the following caveat:</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:28&amp;rev=1392999810&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-21T16:23:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>28</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:28&amp;rev=1392999810&amp;do=diff</link>
        <description>Home

Pretty old stuff but may be useful, up to date info is here Brief Guide to HPCC

User Guide &amp; Manuals

	*  Account and Access

	*  Login and Debug

	*  Filesystems

	*  the   Queue Update page 03/01/2013
		*  old Queues


	*  Job Submissions for serial jobs

	*  Job Submissions for parallel jobs using Infiniband.

	*   Software installed: Petaltail OCS 5.1 (since June 2009)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:29&amp;rev=1252437321&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-08T19:15:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>29</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:29&amp;rev=1252437321&amp;do=diff</link>
        <description>Back

The information displayed here will undoubtedly change very quickly.

So your mileage and  output may be different.

=&gt; Platform/OCS&#039;s very good [Running Jobs with Platform Lava] (read it). 

=&gt; In all the examples below, man command will provide you with detailed information, like for example</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:30&amp;rev=1188570272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-31T14:24:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>30</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:30&amp;rev=1188570272&amp;do=diff</link>
        <description>Back

=&gt; Platform/OCS&#039;s very good [Running Jobs with Platform Lava] (read it). 

=&gt; In all the examples below, man command will provide you with detailed information, like for example man bsub.

Jobs

Non-Infiniband! For Infiniband submissions go to Internal Link

This write up will only focus on how to submit jobs using scripts, meaning in batch mode.  There is an interactive mode but in general if you create a script then you have a record of how you submitted your job.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:31&amp;rev=1177011947&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-19T19:45:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>31</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:31&amp;rev=1177011947&amp;do=diff</link>
        <description>Back

OpenMPI ENV

Tests

To test your environment execute the following two binaries and compare the output.  It should all be set up for you already.  If not, contact the HPCadmin.

#1


[hmeij@swallowtail ~]$ /share/apps/bin/hello.run
Running on ilogin1 and ilogin2 with -np=16
Hello, world, I am 0 of 16
Hello, world, I am 11 of 16
Hello, world, I am 1 of 16
Hello, world, I am 2 of 16
Hello, world, I am 3 of 16
Hello, world, I am 4 of 16
Hello, world, I am 5 of 16
Hello, world, I am 6 of 16
He…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:32&amp;rev=1179329247&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-16T15:27:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>32</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:32&amp;rev=1179329247&amp;do=diff</link>
        <description>Back

=&gt; Lava, the scheduler, is not natively capable for parallel jobs submissions.  So a wrapper script is necessary.  It will obtain the hosts from the LSB_HOSTS variable and build the “machines” file. Follow the TEST link below for detailed information.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:33&amp;rev=1278630854&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-08T23:14:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>33</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:33&amp;rev=1278630854&amp;do=diff</link>
        <description>Back

Login

June 2009 ... the cluster has been upgraded using a new front end node named petaltail.wesleyan.edu.  The old host swallowtail.wesleyan.edu has been added and  you can login and submit jobs on either host.  If you change your password, please do this on host petaltail.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:34&amp;rev=1179345511&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-16T19:58:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>34</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:34&amp;rev=1179345511&amp;do=diff</link>
        <description>Back

General

After you have logged in and read the User Guides &amp; Manuals, you should be able to get some work done.

If you have large compilations to perform please use one of the login nodes.  You will also speed up your compilations if you use the localscratch area.  To stage data and programs you are welcome to do so in your home directory.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:35&amp;rev=1252437093&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-08T19:11:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>35</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:35&amp;rev=1252437093&amp;do=diff</link>
        <description>Back

&lt;hi #ffff00&gt;For the recent set of tools go directly to petaltail.wesleyan.edu&lt;/hi&gt;

----------

The rest of this page applies to OCS 4.1.1 (the old swallowtail), now defunct.

----------










=&gt; Note that some of these tolls prompt for a password wihtout encryption (http vs https).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:36&amp;rev=1205779469&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-03-17T18:44:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>36</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:36&amp;rev=1205779469&amp;do=diff</link>
        <description>Home

ok, so this story begins with ... i thought i had met my inability to comprehend new technology when i was shown that disks can run multiple raid levels simultaneously. but this multipathing eclipses that. just weird, therefore worth describing.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:37&amp;rev=1179249181&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-15T17:13:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>37</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:37&amp;rev=1179249181&amp;do=diff</link>
        <description>Home

Cluster Steering Committee 05/09/2007

Present: James Taft, Jolee West, Henk Meij, Francis Starr, David Beveridge, Eric Aaron, Tsampikos Kottos, George Petersson

ToDos

	*  fix PE2950s (dell issued)

	*  dm-multipath failover (fiber channel) done! 05/14/07</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:38&amp;rev=1247499179&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-13T15:32:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>38</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:38&amp;rev=1247499179&amp;do=diff</link>
        <description>Back

&lt;hi #ffff00&gt;THIS IS THE LIST OF SOFTWARE FOR THE HOST SWALLOWTAIL UNDER OCS 4.4.1, RHEL 4, GlibC 2.3.5-2.19&lt;/hi&gt;

The listings below will be updated as software is installed.

In no particular order ...

PyPat

	*  program: python egg, version 1.0)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:39&amp;rev=1506691194&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-09-29T13:19:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>39</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:39&amp;rev=1506691194&amp;do=diff</link>
        <description>Back

Matlab Update

Summer 2017 we converted our Wesleyan Matlab license to a campus wide Total Academic Headcount license. This implies no more license restrictions, so you can run as many Matlab jobs as you wish using the matlab2017b binary. At this time I see no need to license the Distributed Computation Engine in R2017b.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:40&amp;rev=1185464986&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-26T15:49:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>40</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:40&amp;rev=1185464986&amp;do=diff</link>
        <description>Back

LSF RTM

Platfrom/LSF RTM Demo (Real Time monitoring)

This is a slick application that monitors multiple or individual clusters.  Build on top of Cacti.  The demo below is somewhat heavy but if you&#039;re interested have a looksie.  It “might” run on top of Platform/Lava, our current scheduler.  Some features it includes are:</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:41&amp;rev=1192633914&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-10-17T15:11:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>41</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:41&amp;rev=1192633914&amp;do=diff</link>
        <description>Back

A parallel code example pulled from the BCCD project to probe around the notion of what is parallel computing?

=&gt; This is page 1 of 3, navigation provided at bottom of page

GalaxSee: N-Body Physics

Default Behavior

The problem is described Here.

The Shodor web version of Galaxsee</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:42&amp;rev=1186692482&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-09T20:48:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>42</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:42&amp;rev=1186692482&amp;do=diff</link>
        <description>Back

⇒ This is page 2 of 3, navigation provided at bottom of page

Switch &amp; MPI Flavors

As you can see in the GalaxSee example, parallel code has the ability to provide  significant speed up in job processing times.  Until some saturation point is achieved when performance takes a hit because of the excessive time spend on passing messages.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:43&amp;rev=1186758650&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-10T15:10:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>43</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:43&amp;rev=1186758650&amp;do=diff</link>
        <description>Back

This secton focuses on some debugging tools which are pretty nifty in understanding message passing.  In order to use them, another flavor of MPI is introduced. Sorry.  Good news is, OpenMPI is trying to replace them all.

=&gt; This is page 3 of 3, navigation provided at bottom of page</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:44&amp;rev=1189694225&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-09-13T14:37:05+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>44</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:44&amp;rev=1189694225&amp;do=diff</link>
        <description>Back

Since i went to a workshop on Basic LSF 6.2 Configuration and Administration held in Boston by Platform Computing...

=&gt; consider me dangerous :-P

Our cluster is driven by Platform/Lava as the scheduler, which in essence is LSF 6.1 ... so i&#039;ve staged all the documentation at the link below.  There is a ton of it, all very good.  Covering all aspects of LSF, how to use it and administer it.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:45&amp;rev=1188223122&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-27T13:58:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>45</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:45&amp;rev=1188223122&amp;do=diff</link>
        <description>Back

Ok, so we have a data center power outage for some electrical maintenance work sunday 8/26 2am-9am.  

How to shut down the cluster?  Here are the steps i took.

Cluster Power Down

	*  #1
		*  Turn all queues to inactive 24 hours before shut down.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:46&amp;rev=1190217176&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-09-19T15:52:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>46</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:46&amp;rev=1190217176&amp;do=diff</link>
        <description>Back

Here is a listing of the reasons i know of, so far, why we should upgrade to LSF for HPC.

The documentation for LSF v6.1 is here (although we would go to v7 right away).

&lt;hi #00ffff&gt;
We are getting LSF :!:  Thanks ITS.

 --- Henk Meij 2007/09/19 11:52&lt;/hi&gt;

LSF for HPC</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:47&amp;rev=1189111391&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-09-06T20:43:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>47</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:47&amp;rev=1189111391&amp;do=diff</link>
        <description>Back

Running Gaussian

To run Gaussian jobs on the cluster, read this page. 

It may help in identifying some errors you may encounter

getting your jobs to run. It may also give you ideas to

increase your overall job throughput rate.

Access

You must be a member of the group</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:48&amp;rev=1222367390&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-09-25T18:29:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>48</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:48&amp;rev=1222367390&amp;do=diff</link>
        <description>Back

&lt;hi #ffff00&gt;
SNAPSHOTS ARE NOT ENABLED AS OF 06/30/2008&lt;/hi&gt; 

 --- Meij, Henk 2008/06/30 09:11

Backup Policy

The backup policy of the cluster is described below.  There are 2 different mechanisms.  NetApp snapshots are taken and provide a convenient way to restore &#039;point-in-time&#039;. Snapshots store the changes at the block level.  Tivoli incremental backups store files when metadata of those files has changed. It serves as a backup for file restorations and deleted files.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:49&amp;rev=1375988869&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-08-08T19:07:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>49</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:49&amp;rev=1375988869&amp;do=diff</link>
        <description>Back

Lava/LSF works via a variety of daemon processes that communicate with each other.

	*  Load Information Manager (LIM, master &amp; slaves)
		*  gathers built-in resource load information directly from /dev/kmem
		*  forwards information to master LIM</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:50&amp;rev=1304960549&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-05-09T17:02:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>50</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:50&amp;rev=1304960549&amp;do=diff</link>
        <description>Back

Job Arrays

Just have to document this. Very handy.

You can find detailed informaton at this Link

A job array makes it easy to manage a sequence of jobs with “shorthand” syntax.  It could be managing 20 jobs or 2,000 jobs, managed by a single command.  Once submitted the array job itself can be managed or the individual jobs that make up the job array.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:51&amp;rev=1191005825&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-09-28T18:57:05+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>51</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:51&amp;rev=1191005825&amp;do=diff</link>
        <description>Back

This is for experimental purposes only. 

Proof of concept type of a thing. 

 --- Henk Meij 2007/09/28 11:38

The Story Of NAT

The cluster is served file systems from our NetApp Fabric Attached Storage Device.  These file systems are NFS mounted on each compute node via the IO node.  The NFS traffic is isolated to one of our private networks on the cluster, the 10.3.1.xxx subnet, running across a Cisco 7000 gigabit ethernet switch.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:52&amp;rev=1195571918&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-11-20T15:18:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>52</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:52&amp;rev=1195571918&amp;do=diff</link>
        <description>Back

Upgrading to LSF

Why?  Here is my summation of some items i wish to take advantage of: Link

We&#039;re running Platform/OCS which includes the Lava scheduler.  It&#039;s sorta like LSF but with functionality removed.  However, it is free and very good.  Our Dell cluster came pre-configured with Lava but it&#039;s time to leverage the resources of our cluster in more detail.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:53&amp;rev=1486653269&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-02-09T15:14:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>53</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:53&amp;rev=1486653269&amp;do=diff</link>
        <description>Back

Acknowledgement

If you publish a paper where the cluster was used for calculation, please include the following acknowledgement:

“We thank Wesleyan University for computer time supported by the NSF under grant number CNS-0619508 and CNS-0959856.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:54&amp;rev=1192839795&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-10-20T00:23:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>54</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:54&amp;rev=1192839795&amp;do=diff</link>
        <description>Back

Job Slots

I was asked in the UUG meeting yesterday how one determines how many job slots are still available.  Turns out to be a tricky question. In CluMon you might observe one host with only one JOBPID running yet it is declared &#039;Full&#039; by the scheduler.  This would be a parallel job claiming all job slots with the</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:55&amp;rev=1194026986&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-11-02T18:09:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>55</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:55&amp;rev=1194026986&amp;do=diff</link>
        <description>Back

Overloading Job Slots

Typically, in a particular configuration file, you define how many “cores” a node has.  This is then equated to “job slots”.  In a default scenario, the number of cores and job slots are equal.  The assumption behind this is that each job contains a task that will consume all resources available to that core.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:56&amp;rev=1194361707&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-11-06T15:08:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>56</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:56&amp;rev=1194361707&amp;do=diff</link>
        <description>Back

[CLACReps] High Performance Cluster @ Wesleyan

General answers to questions posed by the CLACReps.

This wiki may have much more detailed information scattered about and i&#039;ll point to some relevant pages.  Click on the Back link above to go to the main page.  Our cluster resides on our internal VLAN, hence is only accessible via Active Directory guest accounts and VPN for non-wesleyan users.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:57&amp;rev=1193927025&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-11-01T14:23:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>57</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:57&amp;rev=1193927025&amp;do=diff</link>
        <description>Home

Cluster Steering Committee 10/29/2007

Present: Jolee West, Henk Meij, Francis Starr, George Petersson, Ganesan Ravishanker

ToDos

	*  continue to look for the person to fill the Coordinator, Scientific Computing and Informatics Center  position</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:58&amp;rev=1221837905&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-09-19T15:25:05+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>58</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:58&amp;rev=1221837905&amp;do=diff</link>
        <description>Back

Platform LSF 6.2 Documentation

This is a local copy of the information available at External Link and available to connections from wesleyan.edu only.

The documentation is quite good. 

Here are some useful links into the local site mentioned above above:</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:59&amp;rev=1199905455&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-01-09T19:04:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>59</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:59&amp;rev=1199905455&amp;do=diff</link>
        <description>Back

Complete Documentation

It&#039;s all at this link COMPLETE DOCUMENTATION FOR LSF/HPC 6.2 and very good.

New Features in LSF 6.2

This page will be expanded to show examples of LSF/HPC advanced features.

The more information you can provide to the scheduler regarding run times, resources needed and when, the more efficient the scheduling will be.  The examples below are just made up scenarios.  Try to get familiar with them or ask for hands-on working sessions.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:60&amp;rev=1213885258&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-19T14:20:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>60</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:60&amp;rev=1213885258&amp;do=diff</link>
        <description>Back

The basic configuration of the cluster is detailed below.  This information was requested for inclusion in proposals and the like.  I&#039;m not regularly updating this information so email me if you need this page to be updated.

 --- Meij, Henk 2007/12/03 13:39</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:61&amp;rev=1198681450&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-26T15:04:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>61</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:61&amp;rev=1198681450&amp;do=diff</link>
        <description>Home

Cluster Steering Committee 12/18/2007

Present: Jolee West, Henk Meij, Ganesan Ravishanker, Albert Fry, Francis Starr, David Beveridge.

ToDos

	*  continue to look for the person to fill the Coordinator, Scientific Computing and Informatics Center</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:62&amp;rev=1198264081&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-21T19:08:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>62</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:62&amp;rev=1198264081&amp;do=diff</link>
        <description>Back

Automated Submissions

Quanli walked into the office with a request: how can one automate the submission of tons of jobs?  In his case Gaussian jobs.  “Job Arrays” i answered confidently, but that turned out to be a bit of a problem.  Still working on that.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:63&amp;rev=1203957835&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-25T16:43:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>63</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:63&amp;rev=1203957835&amp;do=diff</link>
        <description>Home

Green?

Christmas/New Years 07/08

Green computing it is not.  Perhaps i should shut down idle hosts ;-)

[save electric?]

Fun!

An honorable mention goes to ...
 [root@swallowtail ~]# bjobs -u qgu  JOBID    USER    STAT    QUEUE    FROM_HOST    EXEC_HOST    JOB_NAME</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:64&amp;rev=1200001375&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-01-10T21:42:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>64</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:64&amp;rev=1200001375&amp;do=diff</link>
        <description>Home

LSF &amp; MPI

The new installation of LSF supports an integrated environment for submitting parallel jobs.  What this means is that the scheduler can keep track of the resource consumption of a job spawning many parallel tasks.  Lava was unable to do so.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:65&amp;rev=1212514042&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-03T17:27:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>65</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:65&amp;rev=1212514042&amp;do=diff</link>
        <description>Back

Milestone!

June 3rd 2008, shortly before 1 pm, the job with JOBID 100,000 was completed. 
JOBIDUSERSTATQUEUEFROM_HOSTEXEC_HOSTJOB_NAMESUBMIT_TIME100000ztanDONEimwswallowtailcompute-1-23ising-spring-2008-swt/simpleRuns/data018/t0.900000/mu-2.630000</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:66&amp;rev=1214683171&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-28T19:59:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>66</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:66&amp;rev=1214683171&amp;do=diff</link>
        <description>Back

The catastrophic crash of June 08.

The actual cause of the crash is the filling of the 4TB home directory file system.  This happened on 

Sun Jun 22 16:23:54 EDT [filer3: wafl.vol.full:notice]: file system on volume cluster_home is full

My notes on the recovery are below.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:67&amp;rev=1214769080&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-29T19:51:20+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>67</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:67&amp;rev=1214769080&amp;do=diff</link>
        <description>Back

The catastrophic crash of June 08

A huge thank you to all for being patient, understanding, and supportive during the week of downtime!

Here are some notes taken while restoring the custer:  LINK

Configuration Changes

Previously, our home directories and sanscratch file system areas were 4 TB and 1 TB volumes, respectively, on host</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:68&amp;rev=1219167251&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-08-19T17:34:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>68</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:68&amp;rev=1219167251&amp;do=diff</link>
        <description>Back

RTM

This is a collection of interesting graphs generated by the Real Time Monitoring tool Platform is developing.  Data covers our evaluation period.

 What is RTM ?  RTM is used to monitor and graph LSF resources (including networks, disks, applications, etc.) in a cluster, or multiple clusters. In graph or table formats, RTM displays resource-related information such as the number of jobs submitted, the details of individual jobs (like load average, cpu usage, job owner), or the hosts o…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:69&amp;rev=1224687261&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-10-22T14:54:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>69</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:69&amp;rev=1224687261&amp;do=diff</link>
        <description>Back

NAMD

Most of your question can be answered on the web site  NAMD or subscribe to their community supported list namd-l.

The rest of this page are simple instruction to get you going.

Jobs

The NAMD binary was compiled against the Topspin libraries, hence can only run on the</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:70&amp;rev=1239887501&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-16T13:11:41+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>70</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:70&amp;rev=1239887501&amp;do=diff</link>
        <description>Back

Milestone

Job number 100,000 finished. June 03, 2008.


JOBID   USER    STAT  QUEUE      FROM_HOST   EXEC_HOST   JOB_NAME   SUBMIT_TIME
100000  ztan    DONE   imw        swallowtail compute-1-23 ising-spring-2008-swt/simpleRuns/data018/t0.900000/mu-2.630000 Jun  3 12:48</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:71&amp;rev=1230051037&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-12-23T16:50:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>71</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:71&amp;rev=1230051037&amp;do=diff</link>
        <description>Back

How To

To make a movie (mpeg4) from png files, type the following line in the console from the folder containing the png files.

mencoder “mf:*.png” -mf fps=10 -o output.avi -ovc lavc -lavcopts vcodec=mpeg4




Back</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:72&amp;rev=1245254011&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-17T15:53:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>72</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:72&amp;rev=1245254011&amp;do=diff</link>
        <description>Back

Links

	*  Home Page page with links to all relevant documentation.

	*  Software page for petaltail.

	*  Ganglia monitors node availability, system load, network usage, and other resource information.

	*  Cacti is a complete network graphing solution.(need to add LSF data). Login as guest/guest to view graphs.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:73&amp;rev=1756492899&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-29T18:41:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>73</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:73&amp;rev=1756492899&amp;do=diff</link>
        <description>Back

Software

OpenHPC Software for Rocky 8

Below is all centos 6 and/or 7, which may or may not run in 8.

IMPORTANT NOTE: Since moving to the TrueNAS/ZFS appliance all references to /home/apps should be replaced with /share/apps which points to /zfshomes/apps

 ---</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:74&amp;rev=1237576609&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-20T19:16:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>74</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:74&amp;rev=1237576609&amp;do=diff</link>
        <description>Home

Usage

Here is the academic compute cluster usage starting 01/01/2008.

[:cluster:bqueues_mar09.jpg]



Home</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:75&amp;rev=1239297932&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-09T17:25:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>75</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:75&amp;rev=1239297932&amp;do=diff</link>
        <description>Home

OCS5.1/RHEL5.1/Lava

Some run times here testing the new hosts.  Ofcourse there is still contention inside the switches with swallowtail.

 C-00 is on Infiniband, C-01 is on Gig Ethernet switch.  Please note that if N&lt;=8 all MPI message passing remains local to the host and does not travel through the switches.  So these are not benchmarks.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:76&amp;rev=1239888443&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-16T13:27:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>76</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:76&amp;rev=1239888443&amp;do=diff</link>
        <description>Back

Milestone

Job number 200,000 finished. April 15th, 2009.


&quot;JOB_FINISH&quot; &quot;6.2&quot; 1239715256 200000 14846 33554450 1 1239708461 0 0 1239713000 
&quot;scoppage&quot; &quot;elw&quot; &quot;&quot; &quot;&quot; &quot;&quot; &quot;swallowtail&quot; &quot;ct2/run/v2j11Fit4&quot; &quot;&quot; &quot;2-11-2.out&quot; &quot;&quot; 
&quot;1239708461.200000&quot; 0 1 &quot;compute-1-23&quot; 64 240.0 &quot;&quot; &quot;./run 5000 2 11 2 6051223 
4359.980846 4359.980846 3.054267 3.054267 0.731855 0.692813&quot; 2250.508870 0.274958 
0 0 -1 0 0 1424 0 0 0 0 -1 0 0 0 173 62771 -1 &quot;&quot; &quot;default&quot; 0 1 &quot;&quot; &quot;&quot; 0 4616 121116 
&quot;&quot; &quot;&quot; &quot;&quot; &quot;&quot; 0 &quot;&quot; 0 &quot;&quot; -1 &quot;/…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:77&amp;rev=1252502487&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-09T13:21:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>77</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:77&amp;rev=1252502487&amp;do=diff</link>
        <description>Back

Expansion

Donation of hardware by Blue Sky Studios

4 racks with blade servers, 52 servers per rack, will be dropped off tomorrow.  Not all will be turned on as 5% of the servers are kaput.  So the first step is to build a fully working rack.  Memory footprint of the servers is either 12 or 24</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:78&amp;rev=1247086470&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-08T20:54:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>78</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:78&amp;rev=1247086470&amp;do=diff</link>
        <description>Back

Clusters That Produce: 25 Open HPC Applications

Informative article on open source applications for

	*  Bioinformatics
	*  Molecular Dynamics
	*  Electronic Structure/Quantum Chemistry
	*  Environment/Weather
	*  Computational Fluid Dyanamics
	*  Finite Element Analysis</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:79&amp;rev=1366314047&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-04-18T19:40:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>79</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:79&amp;rev=1366314047&amp;do=diff</link>
        <description>Back

Deprecated.  We only have rack running (on demand) offering access to 1.1 TB of memory.  The bss24 queue on head node greentail represents the Blue Sky Studio job slots available.
 --- Meij, Henk 2013/04/18 15:39



[sharptail saltmarsh sparrow]

Update: 21 Sept 09

Cluster sharptail has undergone some changes.  Courtesy of ITS, 2 more blade enclosures have permanently been added.  Another 3 blade enclosures have temporarily been added (destined for another ITS project so they may disappea…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:80&amp;rev=1251471412&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-28T14:56:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>80</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:80&amp;rev=1251471412&amp;do=diff</link>
        <description>Back

Cluster: sharptail

Doing some test runs for rough comparisons.

 Gaussian 

Running one small example using g03 ...

	*  swallowtail/petaltail (N=2, imw) 65 mins
	*  sharptail (N=2, bss12) 121 mins
	*  sharptail (N=8!, bss12, so across nodes) --</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:81&amp;rev=1291909609&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-12-09T15:46:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>81</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:81&amp;rev=1291909609&amp;do=diff</link>
        <description>Back

Gaussian never fixed the connectivity with Linda so it can not be run across multiple nodes.
 --- Meij, Henk 2010/12/09 10:45

Gaussian &amp; Linda

(I wrote this up for a user so am sharing it here until we get clarification from Gaussian.com)

Hi Anthony,

I observed your job below on sharptail.  This must be running with the standard g09 executable.  Gaussian is program that forks itself on the same host for as many threads you define, in your case 16.  You’ll notice below that the schedule…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:82&amp;rev=1296763734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-02-03T20:08:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>82</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:82&amp;rev=1296763734&amp;do=diff</link>
        <description>Back

There is a newer version of this page at this page

Brief Description

For inclusion in proposals.  This page is not maintained.

Academic High Performance Computing at Wesleyan

Wesleyan University HPC environment is comprised of two clusters: The “swallowtail” Dell hardware cluster and the “sharptail” Angstrom hardware clusters.  A brief description of each follows.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:83&amp;rev=1284475226&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-09-14T14:40:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>83</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:83&amp;rev=1284475226&amp;do=diff</link>
        <description>Back

Overview

With the second NSF proposal in a “recommended for funding” state, I&#039;m preparing this page so we can address some looming issues and make decisions on our potential new acquisition.  In general, these are the main topics:

	*  Data Center/ITS Items</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:84&amp;rev=1272897743&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-03T14:42:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>84</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:84&amp;rev=1272897743&amp;do=diff</link>
        <description>Back

Cluster Support

So, the Dell cluster (petal/swallow-tails) has run out of support January 25th of this year.  As I found out when I called on 03/01/2010 with a hardware problem.  So the question is what to do next?

The Dell hardware is now 3 years old, but still in good condition. The failure rate during those 3 years has included:  replaced 4 disks, 2 system boards and power fans, and perhaps 8-10 memory sticks. Lets assume that stays the same for now.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:85&amp;rev=1277303279&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-23T14:27:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>85</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:85&amp;rev=1277303279&amp;do=diff</link>
        <description>Back

Recent Queue Usage
  01 April thru 09 June, 2010        Cluster Petaltail/Swallowtail                The Sharptail Cluster          
Historic Queue Usage

So we know we have a need for home directory disk space.  But if we got more nodes, which would they be?  So here is a look at that.  The 2-3 week period from Christmas to end of first week of Jan, represented by no jobs running/pending, was when the electrical work was done on our building. The tremendous spikes are from a single user w…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:86&amp;rev=1273775382&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-13T18:29:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>86</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:86&amp;rev=1273775382&amp;do=diff</link>
        <description>Back

Cloud Or Not?

There is a lot of buzz about cloud computing.  Recently, this has spilled over into the HPC world.  There are private and public clouds.  And private clouds at external organization or internal to your own organization.  I do not have the gist of it down yet, but this page explores the option: can or should we consider HPC cloud for spending our $298K NSF award on or stay the course buying new hardware?</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:87&amp;rev=1274302517&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-19T20:55:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>87</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:87&amp;rev=1274302517&amp;do=diff</link>
        <description>Back

Cluster Software

	*  A good overview, swallowtail is platform OCS/LSF and sharptail is Kusu/Lava

	*  HPCprojects

	*  And I guess this is the spinoff of Kusu/Lava - UniCluster (scheduler?)

	*  UniCluster ... works with schedulers ???

	*  Then there is HP&#039;s version</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:88&amp;rev=1282074964&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-08-17T19:56:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>88</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:88&amp;rev=1282074964&amp;do=diff</link>
        <description>Back

Blue Sky Studios

Hardware

We have 4 racks of which 3 are powered up. All on utility power including head/login node.  Racks are surprisingly cool compared  to our Dell cluster.  Some digging revealed that the AMD Opteron chip cycles down to 1 Ghz if not used instead of running at 2.4 Ghz all the time (You can observe this in /proc/cpuinfo).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:89&amp;rev=1290452713&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-11-22T19:05:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>89</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:89&amp;rev=1290452713&amp;do=diff</link>
        <description>Back

HP HPC

Notes for the cluster design conference with HP.

“do later” means we tackle after the HP on site visit.

S &amp; H

	*  Shipping Address: 5th floor data center
	*  No 13&#039;6“ truck, 12&#039;6” is ok or box truck
	*  Delivery on standard raised dock, no ways to lift rack out of truck if not docked</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:90&amp;rev=1285705974&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-09-28T20:32:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>90</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:90&amp;rev=1285705974&amp;do=diff</link>
        <description>Back

Recent Queue Usage
  14 Sept thru 28 Sept, 2010        Cluster Petaltail/Swallowtail                The Sharptail Cluster          


Back</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:91&amp;rev=1294433373&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-07T20:49:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>91</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:91&amp;rev=1294433373&amp;do=diff</link>
        <description>Back

Linpack

Grabbed the Linpack source and compiled against /opt/openmpi/1.4.2 ... using the Make.Linux_PII_CBLAS makefile.  Had to grab the atlas libraries from another host.  We changed $HOME and pointed to libmpi.so ($MPdir and $MPlib) and repointed $LAdir.  Then it compiled fine.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:92&amp;rev=1301500776&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-30T15:59:36+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>92</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:92&amp;rev=1301500776&amp;do=diff</link>
        <description>Home

a “bottom&#039;s up” page of tasks performed while inching towards deployment.

Closing this page.

Update (03/28/2011)

greentail&#039;s home directories are now served up on petaltail/swallowtail cluster ... this means your home directory is the same across the Dell and HP clusters (minus one host, will work on that tomorrow as well as cluster sharptail).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:93&amp;rev=1294779358&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-11T20:55:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>93</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:93&amp;rev=1294779358&amp;do=diff</link>
        <description>Back
  greentail  
Greentail

Time to introduce our new high performance cluster greentail, an Hewlett Packard HPC solution.  If you want to read more about the details of the hardware, you can find it at Enternal Link. The name refers to the Smooth Green Snake, which no surprise, has a green tail.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:94&amp;rev=1295973572&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-25T16:39:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>94</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:94&amp;rev=1295973572&amp;do=diff</link>
        <description>Back

	*  JAC and Factor_IX are two sample programs included with Amber (one memory intensive, one IO intensive, forgot what is what).

	*  “1g6r” is a program from Surjit Dixit that should scale really well in his opinion.

Swallowtail
  Amber    What</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:95&amp;rev=1374678031&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-07-24T15:00:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>95</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:95&amp;rev=1374678031&amp;do=diff</link>
        <description>Back

	*  the   Queue Update page 03/01/2013

Newest Configuration

The Academic High Performance Compute Cluster is comprised of two login nodes (greentail and swallowtail, both Dell PowerEdge 2050s).  Old login node petaltail (Dell PowerEdge 2950) can be used for testing code (does not matter if it crashes, it&#039;s primary duty is backup to physical tape library).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:96&amp;rev=1426269173&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-03-13T17:52:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>96</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:96&amp;rev=1426269173&amp;do=diff</link>
        <description>Home

Note

You can also run matlab jobs via scripts like other software.

Create a file with the matlab commands and then create a shell script to submit the job.

It would look like



#!/bin/bash
# submit via &#039;bsub &lt; run.serial&#039;

#BSUB -q matlab

#BSUB -J test
#BSUB -o test.stdout
#BSUB -e test.stderr



matlab -no display &lt; my_code.m &gt; /dev/null</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:97&amp;rev=1329419381&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-02-16T19:09:41+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>97</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:97&amp;rev=1329419381&amp;do=diff</link>
        <description>Home

Summary

The purpose of this testing is to find out how fast the storage systems respond either directly attached to compute nodes, or attached via ethernet (gigabit ethernet) or infiniband (SDR via queue imw or QDR via queue hp12).  When using infiniband interconnects we use IPoIB (IP traffic over infiniband interconnects which theoretically might be 3-4 times faster than ethernet).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:98&amp;rev=1313768167&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-19T15:36:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>98</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:98&amp;rev=1313768167&amp;do=diff</link>
        <description>Back

Recent Queue Usage
      Cluster Greentail  (hp12 queue)                    Cluster Greentail  (all queues)                01 Jan 2011 thru 17 Jan, 2011        Cluster Greentail                Cluster Petaltail/Swallowtail                The Sharptail Cluster</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:99&amp;rev=1300721786&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-21T15:36:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>99</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:99&amp;rev=1300721786&amp;do=diff</link>
        <description>Back

Milestone

Bummer, i&#039;m unable to grab the 1,000,000 or 999,999 jobpids.  Wonder what happened to them.
JOBIDUSERSTATQUEUEFROM_HOSTEXEC_HOSTJOB_NAMESUBMIT_TIME999997jwamplerDONEemwc26c25./run 50000 0 18 55 20.179700 203.690000 4.000000 0.325000 10.605000 0.750000 0.500000</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:100&amp;rev=1301322202&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-28T14:23:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>100</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:100&amp;rev=1301322202&amp;do=diff</link>
        <description>Back

Quotas

On 03/25/2011 quotas have been enabled on cluster greentail.  Because group quota numbers are weird, it is like counting duplicates or following links or looping, not sure, we have to rely on individual quotas. Just as well.

Here is what was put in place, and will mature/change over time.  But first, it is important to understand:</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:101&amp;rev=1326898142&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-18T14:49:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>101</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:101&amp;rev=1326898142&amp;do=diff</link>
        <description>Back

2011 Queue Usage

These data reflect the combined queues on the HP greentail cluster.
  01 Jan 2011 thru 31 Dec, 2011        Cluster Greentail                01 Jan 2011 thru 31 Dec, 2011        Cluster Greentail  (Subset, less than 1,000 pending jobs)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:102&amp;rev=1598267968&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-08-24T11:19:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>102</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:102&amp;rev=1598267968&amp;do=diff</link>
        <description>Back

Note #1

CentOS 8.1 with the standard firewalld.

If this is of interest to you this was how I managed to get it work:


EXTIFACE=MASTER_NODE_EXT_INTERFACE_DEVICE (e.g. eno1)
INTIFACE=MASTER_NODE_INTERNAL_INTERFACE_DEVICE (e.g. eno2)
INTIPADDR=MASTER_IP_OF_INTERNAL_IFAC
PREFIX=PREFIX_OF_INTERNAL_NETWORK
firewall-cmd --change-interface=${EXTIFACE} --zone=public
firewall-cmd --change-interface=${INTIFACE} --zone=trusted --permanent
firewall-cmd --permanent --direct --passthrough ipv4 -t nat …</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:103&amp;rev=1324582469&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-22T19:34:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>103</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:103&amp;rev=1324582469&amp;do=diff</link>
        <description>Back

Some general information for SAS users.

SAS

SAS, the statistical analysis software (&lt;http://sas.com&gt;), and much more, frequently used in the social sciences, is available on the High Performance Academic Computing Cluster.  It is not a parallel version of SAS, but we do offer an unlimited linux license for Teaching and Research.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:104&amp;rev=1326309658&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-11T19:20:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>104</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:104&amp;rev=1326309658&amp;do=diff</link>
        <description>Back

Milestone

Starting anew with greentail Lava scheduler
  JOBPID    USER    STAT    QUEUE    FROM_HOST    EXEC_HOST    JOB_NAME  SUBMIT_TIME    500000    lvargaslara    EXIT    hp12    greentail    n23    n2l16f4L20c26    Dec 28 11:04 2011</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:105&amp;rev=1354215776&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-11-29T19:02:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>105</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:105&amp;rev=1354215776&amp;do=diff</link>
        <description>Back

2012 Queue Usage

These data reflect the combined queues on the HP greentail cluster.
  2012        Cluster Greentail                2012        Cluster Greentail  (Subset, less than 1,000 pending jobs)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:106&amp;rev=1479759767&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-11-21T20:22:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>106</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:106&amp;rev=1479759767&amp;do=diff</link>
        <description>Back

Stata

Some general information for Stata users.

Sample

* save in a script say called run and submit to scheduler bsub &lt; run


#!/bin/bash

rm -rf err out 

# relevant commands
# find available hosts: bhosts 
# find queues: bqueues 
# submit job: bsub &lt; run
# show jobs submitted: bjobs

#BSUB -q stata
#BSUB -J test
#BSUB -o out
#BSUB -e err

# use n cores (job slots) ... a license limitation of 6
#BSUB -n 6
# force using all on one node (hosts=1) 
#BSUB -R &quot;span[hosts=1]&quot;

# can stata-mp…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:107&amp;rev=1378905534&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-09-11T13:18:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>107</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:107&amp;rev=1378905534&amp;do=diff</link>
        <description>Back

GPU History

&lt;http://en.wikipedia.org/wiki/Graphics_processing_unit&gt;

What is a GPU cluster?

	*  CPU = Central Processing Unit
		*  the chip on the motherboard with L1/L2 caches and often comprised of cores (like dual quad or 8)
		*  each core typically processes one computing job
		*  kernel also has ability to swap to disk (not a desired long term state)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:108&amp;rev=1392996336&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-21T15:25:36+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>108</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:108&amp;rev=1392996336&amp;do=diff</link>
        <description>Back

This outdated page replaced by Brief Guide to HPCC

Our Queues

An updated on our queues ...
 --- Meij, Henk 2013/09/10 14:43
QueueNr Of NodesTotal GB Mem Per NodeTotal Cores In QueueSwitchHostsNotes  matlab    na    na    na   either   any host in hp12,elw,emw,imw   max jobs &#039;per user&#039; or &#039;per host&#039; is 8</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:109&amp;rev=1381950833&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-10-16T19:13:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>109</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:109&amp;rev=1381950833&amp;do=diff</link>
        <description>Back

Lammps GPU Testing (EC)

	*  32 cores E2660
	*  4 K20 GPU
	*  workstation
	*  MPICH2 flavor

Same tests (12 cpu cores) using lj/cut, eam, lj/expand, and morse: AU.reduced
  CPU only 6 mins 1 secs
  1 GPU 1 mins 1 secs (a 5-6 times speed up)
  2 GPUs 1 mins 0 secs (never saw 2nd GPU used, problem set too small?)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:110&amp;rev=1369402757&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-05-24T13:39:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>110</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:110&amp;rev=1369402757&amp;do=diff</link>
        <description>Back

Notes

	*  HP cluster off support 11/30/2013
	*  We need greentail/disk array support maybe 2 more years?
		*  Karen added to budget, Dave to approve ($2200/year)

	*  We need another disk array
		*  For robust D2D backup

	*  Pressed HP Procurve ethernet backup switch into production</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:111&amp;rev=1360006122&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-02-04T19:28:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>111</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:111&amp;rev=1360006122&amp;do=diff</link>
        <description>Back

Amber GPU Testing (EC)

We are interested in benchmarking the serial, MPI, cuda and cuda.MPI versions of pmemd.

Results

	*  Verified the MPI threads and GPU invocations
	*  Verified the output data
	*  pmemd.cuda.MPI errors
	*  Script used is listed at end of this page</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:112&amp;rev=1381259043&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-10-08T19:04:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>112</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:112&amp;rev=1381259043&amp;do=diff</link>
        <description>Back

All campus utilities are within the physical plant chart of accounts. Departments are not charged.

Overview
  Cluster  Blue Sky  Dell  HP  GPU  CPU  Comment      12/2006  11/2010  04/2013  04/2013    Age (yrs)  11  5.5  1.5  0  0    Nodes (Nr)  45</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:113&amp;rev=1391447289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-03T17:08:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>113</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:113&amp;rev=1391447289&amp;do=diff</link>
        <description>Back

2013 Queue Usage

These data reflect the combined queues on the HP greentail cluster.
  2013        Cluster Greentail                2013        Cluster Greentail  (Subset, less than 1,000 pending jobs)                2013        Cluster Greentail  (mwgpu queue jobs)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:114&amp;rev=1378839598&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-09-10T18:59:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>114</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:114&amp;rev=1378839598&amp;do=diff</link>
        <description>Back

Build Hadoop (test) Cluster

Use Hadoop (test) Cluster

These are my notes building a test Hadoop cluster on virtual machines in VMware. They consists of a blending of instructions posted by others with my commentary added.  Please review these sites so this page makes sense to you.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:115&amp;rev=1378839843&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-09-10T19:04:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>115</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:115&amp;rev=1378839843&amp;do=diff</link>
        <description>Back

Use Hadoop Cluster

Build Hadoop Cluster

Word count, vanilla

Ross writes ....

I did the classic map-reduce example: a word count of a flat text file, in this case James Joyce&#039;s Ulysses. 

	*  First, I downloaded the data.
	*  Second, I copied the data from my home folder to the Hadoop Distributed File System (HDFS).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:116&amp;rev=1391540233&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-04T18:57:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>116</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:116&amp;rev=1391540233&amp;do=diff</link>
        <description>Back

Since deployment of sharptail the information below is out of date. /home is now the same across the entire HPCC and served out by sharptail.

 --- Meij, Henk 2014/02/04 13:56

Sharptail Cluster

A recycle head node name, seems appropriate.

The new hardware has been delivered and rack&amp;stacked.  First priority was looking around while /home was copied from greentail:/home.  This cluster is comprised of one head node (sharptail) and 5 compute nodes (n33-n37).  The head node has a 48 TB disk…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:117&amp;rev=1374590789&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-07-23T14:46:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>117</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:117&amp;rev=1374590789&amp;do=diff</link>
        <description>Back

Milestone

Starting anew with Lava scheduler (hp + dell + bss hardware, microway hardware in recess stay&amp;play mode).
  JOBPID    USER    STAT    QUEUE    FROM_HOST    EXEC_HOST    JOB_NAME    SUBMIT_TIME    999998  blycette    DONE    bss24    greentail</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:118&amp;rev=1377197887&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-08-22T18:58:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>118</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:118&amp;rev=1377197887&amp;do=diff</link>
        <description>Back

PGI Accelerator

Some quick notes for our trial environment. PGI compilers comes with it&#039;s own MPI flavor, Java JRE and Cuda (4.2 and 4.5).  These compilers can compile straight C/C++ and Fortran code.  But they can also compile that code for parallel invocation using MPI and GPU enable the code stack.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:119&amp;rev=1623958367&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-17T19:32:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>119</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:119&amp;rev=1623958367&amp;do=diff</link>
        <description>Back

Submitting GPU Jobs

Please plenty of time between multiple GPU job submissions.  Like minutes.

Jobs need to be submitted to the scheduler via cottontail to queues mwgpu, amber128, exx96.

This page is old, the gpu resource gpu4 should be used, a more recent page can be found</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:120&amp;rev=1392996279&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-21T15:24:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>120</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:120&amp;rev=1392996279&amp;do=diff</link>
        <description>Back

This outdated page replace by Brief Guide to HPCC
 --- Meij, Henk 2014/02/21 10:23

Updated 
 --- Meij, Henk 2013/09/10 14:42

	*  the   Queue Update 

New Configuration

The Academic High Performance Compute Cluster is comprised of two login nodes (greentail and swallowtail, both Dell PowerEdge 2050s).  Old login node petaltail (Dell PowerEdge 2950) can be used for testing code (does not matter if it crashes, it&#039;s primary duty is backup to physical tape library).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:121&amp;rev=1379344140&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-09-16T15:09:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>121</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:121&amp;rev=1379344140&amp;do=diff</link>
        <description>Back

Hadoop Summary

Our production Hadoop Cluster is based on Cloudera&#039;s CD3U6 repository.  Here are some details :

	*  namenode (that is login node): whitetail.wesleyan.edu
		*  whitetail also runs the Hadoop Scheduler and Health Monitor
			*   Health Status
			*   Job Tracker

		*</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:122&amp;rev=1380652255&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-10-01T18:30:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>122</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:122&amp;rev=1380652255&amp;do=diff</link>
        <description>Back

Workshop and Q&amp;A Fall 2013

	*  Clusters! We have ...
		*  New Configuration


	*  Tails! We have ...
		*  greentail (HP) primary login node and scheduler (do not run long running programs on it)
			*  current file server, to be backup file server

		*  swallowtail (Dell) secondary login node and scheduler (do not run long running programs on it)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:123&amp;rev=1382554322&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-10-23T18:52:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>123</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:123&amp;rev=1382554322&amp;do=diff</link>
        <description>Back

Replace Dell Racks

A Novella: Replace the Dell Racks with new hardware

Subtitle: A win-win solution proposed by Physical Plant and ITS

Once upon a time, back in 2013,  two Dell racks full of compute nodes, sat noisily chewing away energy on the 5th floor of Science Tower.  They drew in nicely cooled air from the floor spewing it out the back of the racks at 105-110 degrees (F).  They were giving the three Liebert cooling towers a run for their BTUs.  So much so that if one failed the De…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:124&amp;rev=1457727297&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-03-11T20:14:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>124</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:124&amp;rev=1457727297&amp;do=diff</link>
        <description>Back

Queue tinymem supports BLCR
 --- Henk 2016/03/03 13:57

Adjust your PATH and LD_LIBRARY_PATH accordingly.

BLCR

So we need a day of down time to switch file server functionality from greentail to sharptail. It would be nice if everybody did not loose any computational progress.  To do that, we need to learn to checkpoint at the application level.  If a node crashes or power is lost, those applications can then restart the job from the last checkpoint.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:125&amp;rev=1393446749&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-26T20:32:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>125</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:125&amp;rev=1393446749&amp;do=diff</link>
        <description>Back

Done!
 --- Meij, Henk 2014/02/21 09:54

Dell Racks Power Off

Soon (Feb/2014), we&#039;ll have to power down the Dell Racks and grab one L6-30 circuit supplying power to those racks and use it to power up the new Microway servers.

That leaves some spare L6-30 circuits (the Dell racks use 4 each), so we could contemplate grabbing two and powering up two more shelves of the Blue Sky Studio hardware.  That would double the Hadoop cluster and the</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:126&amp;rev=1763827695&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-22T16:08:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>126</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:126&amp;rev=1763827695&amp;do=diff</link>
        <description>Back

Brief Guide to HPCC

This page will be maintained and provide information to get users started using the compute cluster. It is a merger of the old “brief description” page and the “queue description” page.

In General

HPCC maintains and regularly updates an extensive software stack. Including provisioning tools, resource management, file transfer clients, development tools, a variety of scientific libraries, a variety of compilers (e.g. gcc/g++, OneAPI) and communication libraries (e.g.,…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:127&amp;rev=1396878513&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-04-07T13:48:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>127</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:127&amp;rev=1396878513&amp;do=diff</link>
        <description>Back

Virtual HPCC services

Thoughts on how to create virtual compute nodes in the HPCC stack. Specifically, trying to solve the need for tiny, but many, compute nodes for the nano physic applications. Like virtual compute nodes with a single core CPU with 128</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:128&amp;rev=1401219091&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-05-27T19:31:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>128</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:128&amp;rev=1401219091&amp;do=diff</link>
        <description>Back

Milestone

Switching to Openlava ... starting count again

Here is a history line

	*  jul 2007 40+ accounts deployed
	*  jun 2008 100,000 job marker 70
	*  may 2009 200,000 job marker 76
	*  mar 2011 1,000,000 job marker 99 (dell)
	*  nov 2012 500,000 job marker</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:129&amp;rev=1403100272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-06-18T14:04:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>129</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:129&amp;rev=1403100272&amp;do=diff</link>
        <description>Back

Gaussian Checkpointing

When you have one or more jobs running that rely on Gaussian internal checkpoint mechanism, heavy read/write operations may result.  That traffic should definitely not hit the /home file system but the /sanscratch file system.  That scratch space is also NFS mounted over the Infiniband interconnects (via IPoIB). The result is that this file systems IO operations will also slow our file server down tremendously (even though /sanscratch is a 5 disk Raid 0 setup).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:130&amp;rev=1507039662&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-10-03T14:07:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>130</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:130&amp;rev=1507039662&amp;do=diff</link>
        <description>Back

Jobs Pending Historic

First some interesting progress graphs from our report to the provost.
        
Report



Total Jobs Submitted

Just because I keep track =), 2 millionth milestone reached in July 2013.



A picture of our total number of job slots availability and cumulative total of jobs processed.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:131&amp;rev=1429020970&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-04-14T14:16:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>131</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:131&amp;rev=1429020970&amp;do=diff</link>
        <description>Back

For other years view: 2013 Queue Usage, 2012 Queue Usage, 2011 Queue Usage ...

2014 Queue Usage

These data reflect the combined queues on the HP greentail cluster.
  2014        HPC Cluster                2014        HPC Cluster  (Subset, less than 1,000 pending jobs)                2014</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:132&amp;rev=1407766129&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-08-11T14:08:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>132</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:132&amp;rev=1407766129&amp;do=diff</link>
        <description>Back

LXC Linux Containers

Ok, virtualization again. Trying this approach on a Dell PowerEdge 2950.

	*  &lt;https://linuxcontainers.org/&gt;
	*  &lt;http://docs.oracle.com/cd/E37670_01/E37355/html/ol_config_os_containers.html&gt;
	*  &lt;http://wiki.centos.org/HowTos/LXC-on-CentOS6&gt;

Starting with the latter.

When you get the SElinux policy, create the *.te file then



[root@petaltail ~]# vi lxc.te
[root@petaltail ~]# semodule -l | grep lxc
[root@petaltail ~]# checkmodule -M -m -o lxc.mod lxc.te
checkmodul…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:133&amp;rev=1426703181&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-03-18T18:26:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>133</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:133&amp;rev=1426703181&amp;do=diff</link>
        <description>Back

High Core Count - Low Memory Footprint

I polled some folks with the problem described below to find a solution. Then ...

&lt;http://www.nytimes.com/2014/08/08/science/new-computer-chip-is-designed-to-work-like-the-brain.html&gt;

We&#039;re on the cusp of a new era!

Other solutions than the one described below

	*  Amax 4U/288 cores &lt;http://www.amax.com/hpc/product.asp?value=High%20Density%20/%20Performance&gt;
	*  Microway 2U/144 cores</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:134&amp;rev=1408712719&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-08-22T13:05:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>134</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:134&amp;rev=1408712719&amp;do=diff</link>
        <description>Back

Slurm

The Simple Linux Utility for Resource Management (SLURM) is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters. The architecture is described here &lt;https://computing.llnl.gov/linux/slurm/quickstart.html&gt;.

	*  Installation</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:135&amp;rev=1554988204&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-04-11T13:10:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>135</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:135&amp;rev=1554988204&amp;do=diff</link>
        <description>Back

RSTORE Update

The rstore0/2 access points will go into read only mode early 2019. These access points will be replace by a similar but new platform rstore4/6.  Each share owner will be contacted and content will be copied if needed (we have two copies of everything on the old platform so hopefully most of it can remain there).  The new platform is</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:136&amp;rev=1595956885&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-07-28T17:21:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>136</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:136&amp;rev=1595956885&amp;do=diff</link>
        <description>Back

/home is defunct but remains for compatibility. It has been moved from sharptail to whitetail. New home directories are at /zfshomes. Although quotas are in place (starting at 1T for new accounts) users typically get what they need.  Static content should eventually be migrated to our Rstore platform.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:137&amp;rev=1560358826&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-06-12T17:00:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>137</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:137&amp;rev=1560358826&amp;do=diff</link>
        <description>Back

Submitting R2017+ Jobs

Wesleyan has obtained a campus wide site license for Matlab since version 2017.  Hence there is no need to check out a license and the queue matlab has been removed. You can use version 2017 and onward on all queues in unlimited number off jobs. Your submit script should do something simple like</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:138&amp;rev=1466532672&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-06-21T18:11:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>138</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:138&amp;rev=1466532672&amp;do=diff</link>
        <description>Back

Expansion

We will be bringing online 280 more physical cores (560 hyper threads) with Haswell-EP E2650v3 chips 2.3 Ghz with a turbo boost speed of 3.0 Ghz.

That&#039;s an 85% increase in job slots. Yea. 

Final Round

	*  ExacctCorp: Quantum IXR110-512N E5-2600 v3 family</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:139&amp;rev=1534424292&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-16T12:58:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>139</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:139&amp;rev=1534424292&amp;do=diff</link>
        <description>Back

Warewulf Stateless

	*  &lt;http://warewulf.lbl.gov/trac&gt; Warewulf is a scalable systems management suite originally developed to manage large high-performance Linux clusters.  My Project Kusu replacement since IBM bought up Platform LSF and dished the hpccommunnity.org web site, grrrh. (old info at</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:140&amp;rev=1449255200&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-12-04T18:53:20+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>140</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:140&amp;rev=1449255200&amp;do=diff</link>
        <description>Back

2015 Summer Expansion

Fourteen Supermicro 1U servers were purchased each with dual 10 core processors. With hyper threading turned on that yields us 40 logical cores per 1U rack space or a total of 560 new logical cores. However, we maximized on cores and minimized our spending on memory. Each node has 32</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:141&amp;rev=1452708321&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-01-13T18:05:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>141</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:141&amp;rev=1452708321&amp;do=diff</link>
        <description>Back

For other years view: 2014 Queue Usage, 2013 Queue Usage, 2012 Queue Usage, 2011 Queue Usage ...

2015 Queue Usage
  2015 Totals        HPC Cluster                2015 before summer expansion        HPC Cluster</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:142&amp;rev=1582811943&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-02-27T13:59:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>142</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:142&amp;rev=1582811943&amp;do=diff</link>
        <description>Back

Scratch Spaces

We have different locations for scratch space. Some local to the nodes, some mounted across the network. Here is the current setup as of August 2019.

	*  /localscratch
		*  Local to each node, different sizes roughly around 50-80</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:143&amp;rev=1449779768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-12-10T20:36:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>143</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:143&amp;rev=1449779768&amp;do=diff</link>
        <description>Back



Back

Warewulf Statefull

	*  &lt;http://warewulf.lbl.gov/trac&gt; Warewulf is a scalable systems management suite originally developed to manage large high-performance Linux clusters.

So now that we can script stateless provisioning, we might also want to use stateful provisioning. That is PXE boot node once to format drive and install kernel +</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:144&amp;rev=1532631173&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-07-26T18:52:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>144</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:144&amp;rev=1532631173&amp;do=diff</link>
        <description>Back

Warewulf Golden Image

Also read these pages and this page will make more sense: Warewulf Stateless, Warewulf Statefull.

For some time now I have been looking for a provisioning tool. I&#039;ve tried along the way ...

	*  Project Kusu, now defunct, but a great, simple template driven system. No fancy gui.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:145&amp;rev=1491405768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-04-05T15:22:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>145</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:145&amp;rev=1491405768&amp;do=diff</link>
        <description>Back

IPoIB

Redoing our RHEL5.5 HP Proliant blade servers with CentOS 6.7 using Warewulf Golden Image provisioning.

Not quite there yet, but I&#039;ll document here how Infiniband was installed. These compute nodes are connect to a Voltaire interconnect, and aging quite a bit.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:146&amp;rev=1504013773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-08-29T13:36:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>146</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:146&amp;rev=1504013773&amp;do=diff</link>
        <description>Back

Openlava 3.1.2

Build process, switching to git approach.

Prequisites (for rpm.sh)

	*  yum install git
	*  yum install rpm-build
	*  yum install rpmdevtools
	*  yum install tcl tcl-devel
	*  yum install ncurses ncurses-devel
	*  yum install automake libtool</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:147&amp;rev=1582826808&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-02-27T18:06:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>147</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:147&amp;rev=1582826808&amp;do=diff</link>
        <description>Back

BLCR Checkpoint in OL3

Deprecated since we did OS upgrades OS Update

We will install DMTCP as a replacement...DMTCP 

 --- Henk 2020/01/14 14:28

	*  This page concerns SERIAL jobs only; SERIAL jobs can restart on any node

	*  Installation and what it does BLCR

	*</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:148&amp;rev=1579891009&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-01-24T18:36:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>148</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:148&amp;rev=1579891009&amp;do=diff</link>
        <description>Back

BLCR Checkpoint in OL3

Deprecated since we did OS Update 

We will replace it with DMTCP  

 --- Henk 2020/01/14 14:31

	*  This page concerns PARALLEL mpirun jobs only; there are some restrictions
		*  all MPI threads need to be confined to one node
		*  restarted jobs must use the same node (not sure why)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:149&amp;rev=1481055197&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-12-06T20:13:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>149</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:149&amp;rev=1481055197&amp;do=diff</link>
        <description>Back

The “information dive” into enterprise storage was an educational one. This write up is more for my note taking so I can keep track of and recall things.

The Storage Problem

In a commodity HPC setup deploying plain NFS, bottle necks can develop.  Then the compute nodes hang and a cold reboot of the entire HPCC is needed. NFS clients on a compute node may contact NFS daemons on our file server sharptail and ask for say a file. The NFS daemon assigned the task then locates the content via …</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:150&amp;rev=1480448189&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-11-29T19:36:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>150</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:150&amp;rev=1480448189&amp;do=diff</link>
        <description>Back

Rsync Daemon/Rsnapshot

The Problem

Trying to offload heavy read/write traffic from our file server. I also did a deep information dive to assess if we could afford enterprise level storage. That answer basically means a $42K layout at the low end and up to $70K for the high end. I&#039;ve detailed the result here</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:151&amp;rev=1481055243&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-12-06T20:14:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>151</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:151&amp;rev=1481055243&amp;do=diff</link>
        <description>Back

beeGFS

A document for me to recall and make notes of what I read in the manual pages and what needs testing.

Basically during the Summer of 2016 I investigated if the HPCC could afford enterprise level storage. I wanted 99.999% uptime, snapshots, high availability and other goodies such as parallel NFS. Netapp came the closest but, eh, still at $42K lots of other options show up. That story is detailed at</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:152&amp;rev=1485531375&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-01-27T15:36:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>152</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:152&amp;rev=1485531375&amp;do=diff</link>
        <description>Back

For other years view: 2015 Queue Usage, 2014 Queue Usage, 2013 Queue Usage, 2012 Queue Usage, 2011 Queue Usage ...

2016 Queue Usage
  2016 Totals        HPC Cluster              


[root@cottontail ~]# grep ^2016 /share/apps/logs/bjobs_done.log | tail

date,lifetime_total,daily_total
20161222,3014237,17
20161223,3014389,152
20161224,3014460,71
20161225,3014512,52
20161226,3014570,58
20161227,3014595,25
20161228,3014627,32
20161229,3014652,25
20161230,3014677,25
20161231,3014682,5</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:153&amp;rev=1512574492&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-12-06T15:34:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>153</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:153&amp;rev=1512574492&amp;do=diff</link>
        <description>Back

&lt;https://nsf.gov/pubs/2018/nsf18508/nsf18508.htm&gt;

Due Jan 30, 2018, totally refocused on network, killing the ideas on this page
 --- Henk 2017/12/06 08:50

NSF CC*

	*  Create a $1 Million+ CC* proposal to meet the research, staff and cyberinfrastructure
	*  Needs/Wants of small, primarily undergraduate, northeast Higher Ed institutions</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:154&amp;rev=1534510139&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-17T12:48:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>154</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:154&amp;rev=1534510139&amp;do=diff</link>
        <description>Back

OpenHPC page 1

	*  install vanilla CentOS 7.2 on master
	*  find Install_guide-CentOS7.2-SLURM-1.2.1-x86_64.pdf recipe guide on &lt;http://openhpc.community&gt;
	*  turn selinux off
	*  next switch to iptables


             
[root@ohpc0-test ~]# systemctl disable NetworkManager 
             
[root@ohpc0-test ~]# systemctl disable firewalld         
     
[root@ohpc0-test ~]#  yum install iptables-services -y   
                       
[root@ohpc0-test ~]# systemctl enable iptables

[root@ohpc…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:155&amp;rev=1491395703&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-04-05T12:35:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>155</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:155&amp;rev=1491395703&amp;do=diff</link>
        <description>Back

OpenHPC page 2

Additional tools for the OpenHPC environment. First add these two lines to SMS and all compute nodes. Patch CHROOT as well.

	*  /etc/security/limits.conf



# added for RLIMIT_MEMLOCK warnings with libibverbs -hmeij
*                soft    memlock         unlimited
*                hard    memlock         unlimited</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:156&amp;rev=1491403373&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-04-05T14:42:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>156</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:156&amp;rev=1491403373&amp;do=diff</link>
        <description>Back

OpenHPC page 3

 Tools 



yum -y groupinstall ohpc-autotools
yum -y install valgrind-ohpc
yum -y install EasyBuild-ohpc
yum -y install spack-ohpc
yum -y install R_base-ohpc



	*  “Valgrind is an instrumentation framework for building dynamic analysis tools. There are Valgrind tools that can automatically detect many memory management and threading bugs</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:157&amp;rev=1491507119&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-04-06T19:31:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>157</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:157&amp;rev=1491507119&amp;do=diff</link>
        <description>Back

Centralize SSH Key Management

Lets assume we have 3 colleges (CollegeA, CollegeB, CollegeC) and we write a grant proposal and each institution will do something unique science wise. Grant gets funded and specialized hardware or software gets deployed at each college (for maybe brain scan analyses, deep learning, and engineering).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:158&amp;rev=1490793488&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-03-29T13:18:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>158</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:158&amp;rev=1490793488&amp;do=diff</link>
        <description>Back

Openlava Elim

Pulling some information together for Openlava users documenting the ability to write your own monitor resources which the scheduler will then manage. This is handy so jobs go in PENDing mode while waiting for custom resoures to become available instead of crashing immeditaley upon submission.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:159&amp;rev=1490816374&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-03-29T19:39:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>159</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:159&amp;rev=1490816374&amp;do=diff</link>
        <description>Back

HPC Survey 2017

“High-Performance Computing,” or HPC, is the application of “compute nodes” to computational problems that are either too large for standard computers or would take too long individually. HPC typically consists of a system manager server (SMS, also know as login node or master node, or all combined) and compute nodes. HPC designs may differ but frequently offer high speed networks, large home directories, scratch space, archive space and a job scheduler. A provision applic…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:160&amp;rev=1496243269&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-05-31T15:07:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>160</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:160&amp;rev=1496243269&amp;do=diff</link>
        <description>Back

OpenHPC page 4

 ib0 

Using Infiniband for MPI traffic involves somewhat more configurations. So from the ground up (v1.3 documentation) we start with installing packages needed on CHROOT.  Be sure to follow recipe and install these on SMS too.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:161&amp;rev=1594919783&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-07-16T17:16:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>161</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:161&amp;rev=1594919783&amp;do=diff</link>
        <description>Back

lammps-11Aug17

lammps-11Aug17 (n78)

and now lammps-22Aug18 (n33-n37)

and now lammps-5Jun19 (microway)


Update:

	*  n78/gtx1080 lammps 11aug17 (centos7, mpich3/mpic++, cuda 8/sm_61, /usr/local)
			*  GTX 1080 Ti

	*  n37/k20 lammps 22aug18 (centos7, openmpi 1.8.4/mpic++, cuda 9.2/sm_35, /usr/local)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:162&amp;rev=1504722963&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-09-06T18:36:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>162</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:162&amp;rev=1504722963&amp;do=diff</link>
        <description>Back

	*  Jobs can be submitted from any node.
	*  cottontail is primary scheduler login node.
	*  You can login in to any tail node directly (via ssh).
	*  All nodes are CentOS 6.x with some exceptions noted.

Test Queue

	*  Wall time (CPULIMIT) has been removed (was 8 hrs/job)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:163&amp;rev=1559063599&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-05-28T17:13:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>163</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:163&amp;rev=1559063599&amp;do=diff</link>
        <description>Back

Cacti Monitor

Cacti server has died, need to build new zenoss/cacti server summer 2019

 --- Henk 2019/05/28 13:11

ZenOSS went on the blink last month, very old install. So I tried Zabbix but not happy with that. Went back to old friend Cacti, very easy install.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:164&amp;rev=1537531170&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-09-21T11:59:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>164</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:164&amp;rev=1537531170&amp;do=diff</link>
        <description>Back

GTX 1080 Ti
GPUGTX 1080 TiTransistor Count12 billionNvidia Cores3,584FP32 (single precision) Teraflops11.4FP64 (double precision) Teraflops0.355Memory Capacity11GBPower250 WattPrice$700Maximum GPU Temperature91 (in C)
We have Enterprise Level Telsa K20 GPU compute nodes (graphical processing units). Four per node for a total of 20 K20s capable of roughly 23 total Teraflops (floating point, double precision). $100K in 2013.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:165&amp;rev=1516115771&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-01-16T15:16:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>165</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:165&amp;rev=1516115771&amp;do=diff</link>
        <description>Back

For other years view: 2016 Queue Usage, 2015 Queue Usage, 2014 Queue Usage, 2013 Queue Usage, 2012 Queue Usage, 2011 Queue Usage ...

2017 Queue Usage
  2017 Totals        HPC Cluster              


[root@cottontail ~]# grep ^2017 /share/apps/logs/bjobs_done.log | tail

date,lifetime_total,daily_total
20171222,3141784,43
20171223,3141806,22
20171224,3141816,10
20171225,3141822,6
20171226,3141852,30
20171227,3141893,41
20171228,3141910,17
20171229,3141940,30
20171230,3141966,26
20171231,31…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:166&amp;rev=1530100260&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-06-27T11:51:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>166</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:166&amp;rev=1530100260&amp;do=diff</link>
        <description>Back

HPC Users Meeting

	*  Brief history 
		*  2006 swallowtail (Dell PE1955, Infiniband, imw, emw)
		*  2010 greentail (HP gen6 blade servers, hp12)
		*  2013 sharptail (Microway storage, K20s, Infiniband, mw256/mwgpu) 
		*  2014 mw256fd (Dell 2006 replacement with Supermicro nodes)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:167&amp;rev=1533132684&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-01T14:11:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>167</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:167&amp;rev=1533132684&amp;do=diff</link>
        <description>Back

CPU vs GPU

So the question was raised what does our usage look like between CPU and GPU devices? I have no idea what the appropriate metrics would be but lets start with comparing the hardware deployed. We&#039;ll also need to make some assumptions</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:168&amp;rev=1537710834&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-09-23T13:53:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>168</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:168&amp;rev=1537710834&amp;do=diff</link>
        <description>Back

2018 GPU Expansion

Important notes ... about GeForce GTX1080Ti

☎ From Nvidia web site: Warranted Product is intended for consumer end user purposes only, and is not intended for datacenter use and/or GPU cluster commercial deployments (“Enterprise Use”). Any use of Warranted Product for Enterprise Use shall void this warranty.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:169&amp;rev=1604604684&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-11-05T19:31:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>169</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:169&amp;rev=1604604684&amp;do=diff</link>
        <description>Back

Acknowledgement

If you publish a paper where the cluster was used for calculation, please include the following acknowledgement:

“We thank Wesleyan University for computer time supported by the NSF under grant number CNS-0619508 and CNS-0959856.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:170&amp;rev=1552932716&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-03-18T18:11:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>170</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:170&amp;rev=1552932716&amp;do=diff</link>
        <description>Back

 --- Henk 2019/03/18 13:58
Note self

	*  Host ohpc0-test + n29 + n31 did form a tiny openhpc/slurm/ww test cluster, redone -slurm
	*  Host sharptail2 act as a Centos7 Warewulf server (host petaltail is Centos6 warewulf server)

OpenHPC 1.3.1

Consult these pages for my earlier testing of OpenHPC. I simply copy&amp;paste my way through these pages while consulting the recipe PDF for CentOS7.5 plus Warewulf. Any changes are logged on this page.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:171&amp;rev=1534773308&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-20T13:55:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>171</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:171&amp;rev=1534773308&amp;do=diff</link>
        <description>Back

Warewulf Golden Image

Build an OpenHPC provisioning server using the Warewulf/Slurm recipe CentOS 7.5 x86_64. Described at local page OpenHPC 1.3.1 and web site &lt;http://openhpc.community/downloads/&gt;. Make sure stateless works. 

We have a standalone Warewulf 3.6.99 provisioning server on CentOS 6.10 with golden images so we can fall back if necessary.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:172&amp;rev=1594835571&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-07-15T17:52:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>172</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:172&amp;rev=1594835571&amp;do=diff</link>
        <description>Back

K20 Redo

In 2013 we bought five servers each with 4 K20 GPUs inside. Since then they have been used but not maintained. Since we have newer GPUs (consult page GTX 1080 Ti) usage has dropped off somewhat. So I&#039;m taking the opportunity to redo them using latest Nvidia, CentOS and application software. After all, it provides 23 teraflops GPU compute capacity (dpfp).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:173&amp;rev=1553515455&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-03-25T12:04:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>173</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:173&amp;rev=1553515455&amp;do=diff</link>
        <description>Back

K20 Redo Usage

One node n37 has been redone with latest Nvidia CUDA drives during summer 2018.  Please test it out before we decide to redo all of them. It is running CentOS 7.5 and I&#039;m interested to see if programs compiled under 6.x or 5.x break.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:174&amp;rev=1535459902&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-28T12:38:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>174</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:174&amp;rev=1535459902&amp;do=diff</link>
        <description>Back

SQL on GPU

MapD built the first ever open source SQL engine to harness GPU computing for analytics. Designed for maximum performance, the MapD SQL engine dynamically compiles SQL to run across multiple GPUs and CPUs. Massively parallel database servers.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:175&amp;rev=1543514430&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-29T18:00:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>175</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:175&amp;rev=1543514430&amp;do=diff</link>
        <description>Back

As of 
 --- Henk 2018/10/08 08:56 

The P100 with 12 GB is end of life, replaced by the P100 16 GB or V100 and 

The GTX 1080Ti will be replaced by the GTX 2080 (no specs yet and not certified for Amber18, yet)

As of
 --- Henk 2018/11/29 12:55

New GROMACS performance benchmarks featuring 2x and 4x NVIDIA RTX 2080 GPUs are now available (GTX too). The RTX 2080 graphics card utilizes the new NVIDIA Turing GPU architecture and provides up to 6x the performance of the previous generation. (E…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:176&amp;rev=1551900551&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-03-06T19:29:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>176</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:176&amp;rev=1551900551&amp;do=diff</link>
        <description>Back

HPC Power

As part of our reevaluation of our data center cooling capacity and overhaul, we need to get a handle on non-emergency power consumption in data center. This will be done by a third party consultant by clamping power cables in the penthouse of Excley. So I bought myself a metered PDU and have been busy plugging entire racks into it one at a time. I then measure</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:177&amp;rev=1552056520&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-03-08T14:48:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>177</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:177&amp;rev=1552056520&amp;do=diff</link>
        <description>Back

For other years view: 2017, 2016, 2015, 2014, 2013, 2012, 2011 ...

2018 Queue Usage
  2018 Totals        HPC Cluster              
 

Back</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:178&amp;rev=1693860396&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-09-04T20:46:36+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>178</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:178&amp;rev=1693860396&amp;do=diff</link>
        <description>Back

New design

Exley Science Center – 265 Church St. – Data Center HVAC Replacement

Replace computer room air conditioning units, replace rooftop condensing units, install new economizer and pump package, install new drop ceiling and lighting, install hot and cold isle containment system.  New system will replace a ~40-year-old system that is critical for the campus IT infrastructure.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:179&amp;rev=1561729402&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-06-28T13:43:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>179</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:179&amp;rev=1561729402&amp;do=diff</link>
        <description>Back

GPU Allocation Problems

GPUs predate our Openlava software stack and need to be integrated into the scheduler as resources. This, along with other issues, has raised some scheduler allocation problems detailed on this page.

A problem arose when we bought node</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:180&amp;rev=1564599368&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-07-31T18:56:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>180</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:180&amp;rev=1564599368&amp;do=diff</link>
        <description>Back

OpenStructure

Open-Source Computational Structural Biology Framework. “This project aims to provide an open-source, modular, flexible, molecular modelling and visualization environment. It is targeted at interested method developers in the field of structural bioinformatics.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:181&amp;rev=1565698533&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-08-13T12:15:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>181</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:181&amp;rev=1565698533&amp;do=diff</link>
        <description>Back

2019 GPU Models

We do not do AI (yet).  Our GPU usage pattern is mostly one job per GPU for exclusive access.  So no NVlink requirements, CPI connections sufficient.  The application list is Amber, Gromacs, Lammps and some python biosequencing packages. Our current per GPU memory footprint is 8</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:182&amp;rev=1576243989&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-13T13:33:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>182</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:182&amp;rev=1576243989&amp;do=diff</link>
        <description>Back

P100 vs RTX 6000 &amp; T4

The specifications of these GPU models are detailed at this page 2019 GPU Models

This page will mimic the work done on this page in 2018 P100 vs GTX &amp; K20

Credits: This work was made possible, in part, through HPC time donated by Microway, Inc. We gratefully acknowledge Microway for providing access to their GPU-accelerated compute cluster.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:183&amp;rev=1729019833&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-15T19:17:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>183</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:183&amp;rev=1729019833&amp;do=diff</link>
        <description>Back

We have moved away from Zenoss, it was getting too old and throwing false alerts. It relies on SNMP and we wnated to go agent based. For the speed of installion we first installed Ganglia (not developed anymore but an awesome package based tool). Then we added Zabbix for completion.  Details at</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:184&amp;rev=1578057777&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-01-03T13:22:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>184</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:184&amp;rev=1578057777&amp;do=diff</link>
        <description>Back

Turing/Volta/Pascal

	*  &lt;https://graphicscardhub.com/turing-vs-volta-v-pascal/&gt;

AWS deploys T4

	*  &lt;https://www.hpcwire.com/2019/09/20/aws-makes-t4-gpu-instances-broadly-available-for-inferencing-graphics/&gt;

Look at this, the smallest Elastic Cloud Compute Instances are g4dn.xlarge yielding access to 4 vCPUs, 16GiB memory and 1x T4 GPU. The largest is g4dn.16xlarge yielding access to 64 vCPUs 256 GiB memory and 1x T4 GPUs. Now the smallest is priced at $0.526/hr, and running that card 2…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:185&amp;rev=1582826722&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-02-27T18:05:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>185</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:185&amp;rev=1582826722&amp;do=diff</link>
        <description>Back

OS Update

Keeping track of operating system updates and quirks.



n1
CentOS release 6.10 (Final)
Linux n1 2.6.32-754.18.2.el6.x86_64 #1 SMP Wed Aug 14 16:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
n2
kaput
n3
CentOS release 6.10 (Final)
Linux n3 2.6.32-754.18.2.el6.x86_64 #1 SMP Wed Aug 14 16:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
n4
CentOS release 6.10 (Final)
Linux n4 2.6.32-754.22.1.el6.x86_64 #1 SMP Tue Sep 17 16:24:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
n5
CentOS relea…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:186&amp;rev=1576244190&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-13T13:36:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>186</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:186&amp;rev=1576244190&amp;do=diff</link>
        <description>Back

Solution: TrueNAS, ZFS, 190T usable, RaidZ2 6 spares, read cache, 800G write cache, self healing, snapshots, compression on, deduplication off, encryption off, dual controllers (high availability), 64G ram, 6x 1Gbe RJ45, SAS drives (not SATA), three year warranty, ssh access​</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:187&amp;rev=1597665663&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-08-17T12:01:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>187</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:187&amp;rev=1597665663&amp;do=diff</link>
        <description>Back

Slurm links:

	*  &lt;https://slurm.schedmd.com/SLUG19/NVIDIA_Containers.pdf&gt;
	*  &lt;https://devblogs.nvidia.com/how-to-run-ngc-deep-learning-containers-with-singularity/&gt;
	*  &lt;https://devblogs.nvidia.com/automating-downloads-ngc-container-replicator/&gt;
	*  &lt;https://devblogs.nvidia.com/docker-compatibility-singularity-hpc/&gt;

Other useful links.

	*  &lt;https://www.nvidia.com/en-us/gpu-cloud/containers/&gt;
	*  &lt;https://docs.nvidia.com/ngc/ngc-user-guide/index.html&gt;
		*   scheduler wrapper, inside con…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:188&amp;rev=1576508179&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-16T14:56:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>188</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:188&amp;rev=1576508179&amp;do=diff</link>
        <description>Back

For other years view: 2018, 2017, 2016, 2015, 2014, 2013, 2012, 2011 ...

2019 Queue Usage
  2019 Totals        HPC Cluster              
 

Back</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:189&amp;rev=1707756462&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-02-12T16:47:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>189</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:189&amp;rev=1707756462&amp;do=diff</link>
        <description>Back

Structure and History of HPCC

As promised at the CLAC HPC Mindshare event at Swarthmore College Jan 2020. Here is the Funding and Priority Policies with some context around it. Questions/Comments welcome.

History

In 2006, 4 Wesleyan faculty members approached ITS with a proposal to centrally manage a high performance computing center (HPCC) seeding the effort with an NSF grant (about $190K, two racks full of Dell PE1950, a total of 256 physical cpu cores on Infiniband). ITS offered 0.5 …</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:190&amp;rev=1601293111&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-09-28T11:38:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>190</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:190&amp;rev=1601293111&amp;do=diff</link>
        <description>Back

DMTCP

	*  &lt;https://sourceforge.net/projects/dmtcp/&gt;
	*  DMTCP (Distributed MultiThreaded Checkpointing)

DMTCP Checkpoint/Restart allows one to transparently checkpoint to disk a distributed computation.  It works under Linux, with no modifications to the Linux kernel nor to the application binaries.  It can be used by
unprivileged users (no root privilege needed).  One can later restart from a checkpoint, or even migrate the processes by moving the checkpoint files to another host prior …</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:191&amp;rev=1579901762&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-01-24T21:36:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>191</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:191&amp;rev=1579901762&amp;do=diff</link>
        <description>Back

NewsBytes for Jan 2020

2019 Queue Usage

&lt;https://dokuwiki.wesleyan.edu/doku.php?id=cluster:188&gt;

2019 dedicated monitoring and alerting server Zenoss

&lt;https://dokuwiki.wesleyan.edu/doku.php?id=cluster:183&gt;

2020 upcoming changes and updates

Tuesday&#039;s (1/21) power outage removed BLCR&#039;s kernel modules from the compute nodes kernels. If you need to do checkpointing the new tool is Distributed MultiThreaded Checkpointing (DMTCP).  Details on how to use DMTCP can be found here</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:192&amp;rev=1646764160&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-03-08T18:29:20+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>192</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:192&amp;rev=1646764160&amp;do=diff</link>
        <description>Back

EXX96

A page for me on how these 12 nodes were build up after they arrived. To make them “ala n37” which was the test node in redoing our K20 nodes, see K20 Redo and K20 Redo Usage

Page best followed bottom to top if interested in the whole process.

The Usage section below is HPCC users wnatig to use queue</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:193&amp;rev=1726591917&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-09-17T16:51:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>193</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:193&amp;rev=1726591917&amp;do=diff</link>
        <description>Back

Docker Containers Usage

Page build up from the bottom to top.  We&#039;re not making a traditional “MPI” docker integration with our scheduler.  We&#039;ll see what usage patterns will emergence and go from there. I can help with workflow.  If more containers are desired please let me know which ones to</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:194&amp;rev=1754398824&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-05T13:00:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>194</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:194&amp;rev=1754398824&amp;do=diff</link>
        <description>Back

TrueNAS/ZFS x20ha

Notes. Mainly for me but might be useful/of interest to users.

Message:

Our current file server is sharptail.wesleyan.edu which serves out home directories (/home, 10T). A new file server hpcstore.wesleyan.edu will be deployed taking over this function (/zfshomes, 190T). This notice is to inform you your home directory has been cut over.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:195&amp;rev=1595700549&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-07-25T18:09:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>195</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:195&amp;rev=1595700549&amp;do=diff</link>
        <description>Back

Comments

Here are some useful comments from lists/vendors etc

	*  LAMMPS uses a hybrid OpenMP/MPI model. If you don&#039;t set the number of OpenMP threads (ompthreads or OMP_NUM_THREADS) explicitly, it will likely take the number of CPU cores (ncpus) as its default value and you will end up with having too many OpenMP threads and MPI processes on a physical core. You can see this by logging in to the compute node and do</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:196&amp;rev=1605019437&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-11-10T14:43:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>196</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:196&amp;rev=1605019437&amp;do=diff</link>
        <description>Back

Netdata

We use Zenoss for monitor and alerting the whole HPC. Page can be found here Zenoss

At PEARC20 conference I became aware of Netdata which seems a good tool for our “tails” (login, storage servers for example).  Lots of detailed information.



bash &lt;(curl -Ss https://my-netdata.io/kickstart.sh)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:197&amp;rev=1598539143&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-08-27T14:39:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>197</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:197&amp;rev=1598539143&amp;do=diff</link>
        <description>Back

XFS quotas

In XFS you first enable quotas on the mountpoint 

(you add the options to /etc/fstab and remount)



# user and group quotas example:
/dev/mapper/VolGroup00-lvhome /home  xfs defaults,usrquota,grpquota 0 1

# user and project quotas example:
/dev/sdb1  /mindstore   xfs   defaults,uquota,pquota    1 2</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:198&amp;rev=1607000999&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-12-03T13:09:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>198</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:198&amp;rev=1607000999&amp;do=diff</link>
        <description>Back

GPU checkpoint/restart

Why I thought this was an easy problem to solve I do not know. CPU checkpoint/restart has come a long way with DMTCP for serial and parallel jobs (including multi-host). But the CPU/GPU environment adds much complexity.

A good</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:199&amp;rev=1607716307&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-12-11T19:51:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>199</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:199&amp;rev=1607716307&amp;do=diff</link>
        <description>Back

ERN 2020



Powerpoint presentation by Karen Warren for Eastern Regional Network describing HPC history and current bottleneck issues.



Back</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:200&amp;rev=1613673188&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-02-18T18:33:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>200</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:200&amp;rev=1613673188&amp;do=diff</link>
        <description>Back

Update 
 --- Henk 2021/02/12 14:27

----------

For CUDA_ARCH (or nvcc -arch) versions check this Matching CUDA arch and CUDA gencode for various NVIDIA architectures web page. “When you compile CUDA code, you should always compile only one ‘-arch‘ flag that matches your most used GPU cards. This will enable faster runtime, because code generation will occur during compilation.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:201&amp;rev=1608996797&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-12-26T15:33:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>201</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:201&amp;rev=1608996797&amp;do=diff</link>
        <description>Back

DMZ with DTN

While attending the 2020 Eastern Regional Network conference (view Karen&#039;s slides presented at ERN) an idea surfaced around 10G network.  If we deploy Cottontail2 and migrate onto 10G network speeds what if we tried for a Science DMZ with a Data Transfer Node (click on Architecture, left side, scroll down for simple setup) with a</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:202&amp;rev=1634756515&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-10-20T19:01:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>202</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:202&amp;rev=1634756515&amp;do=diff</link>
        <description>Back

For other years view: 2019, 2018, 2017, 2016, 2015, 2014, 2013, 2012, 2011 ...

2020 Queue Usage
  2020 Totals        HPC Cluster                          


date,total,pending,running,
07/13/20_07:00,total,82192,770,
07/13/20_07:30,total,166156,796,
...
07/15/20_17:30,total,145188,1549,
07/16/20_07:30,total,137694,1197,
07/16/20_08:00,total,137124,1161,
07/16/20_08:30,total,136542,1209,</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:203&amp;rev=1615405588&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-03-10T19:46:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>203</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:203&amp;rev=1615405588&amp;do=diff</link>
        <description>Back

ICC vs ICX

Following an inquiry on the XSEDE list about the differences between ICC and ICX I was informed  that “Parallel Studio Cluster Edition” has become OneAPI, free-to-use.

So I followed up on that and found a CentOS 7 server to do a local install for testing. We currently run icc/ifort 2016 version and it is time for a new set of compilers.  Now there is also lots of discussions about</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:204&amp;rev=1694805167&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-09-15T19:12:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>204</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:204&amp;rev=1694805167&amp;do=diff</link>
        <description>Back

Lammps: MAKE or CMAKE

Using make and compiling libquip.a into the lammps binary generates an error like error 1 in &#039;geryon/nvd_kernel.h&#039; in line 364 when package gpu tries to set up the runtime env for a lammps gpu job. 

This problem disappears when compiling with</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:205&amp;rev=1621857591&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-05-24T11:59:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>205</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:205&amp;rev=1621857591&amp;do=diff</link>
        <description>Back

XFS panic

We run a lot of XFS storage arrays with hardware raid controllers (Areca, MegaRAID).  Rsync is used to pull content from active server to standby server in a continuous loop.

Usually something like this happens; a disk fails, a hot spare deploys, array rebuilds parity, failed disk gets replaced, new hot spare is created. All is well.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:206&amp;rev=1625753899&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-07-08T14:18:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>206</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:206&amp;rev=1625753899&amp;do=diff</link>
        <description>Back

Python to C

When installing &lt;https://mtazzari.github.io/galario/&gt; via miniconda3 the the web site states “Due to technical limitations, the conda package does not support GPUs at the moment. If you want to use a GPU, you have to build galario by hand.”

A compilation by hand yields two standalone libraries and presumably GPU functionality. There is an example of an invocation using</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:207&amp;rev=1698432479&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-10-27T18:47:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>207</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:207&amp;rev=1698432479&amp;do=diff</link>
        <description>Back

Make sure munge/unmunge work between 1.3/2.4, that date is in sync (else you get error #16)

Slurm Test Env

Getting a head start on our new login node plus two cpu+gpu compute node project. Hardware has been purchased but there is long delivery time. Meanwhile it makes sense to setup a standalone Slurm scheduler and do some testing and have as a backup. Slurm will be running on</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:208&amp;rev=1667410112&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-11-02T17:28:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>208</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:208&amp;rev=1667410112&amp;do=diff</link>
        <description>Back

Slurm Test Env

There is a techie page at this location Slurm Techie Page for those of you who are interested in the setup.

This page is intended for users to get started with the Slurm scheduler. greentail52 will be the slurm scheduler test “controller” with several cpu+gpu compute nodes configured. Any jobs submitted should be simple, quick running jobs, like a</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:209&amp;rev=1649620159&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-04-10T19:49:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>209</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:209&amp;rev=1649620159&amp;do=diff</link>
        <description>Back

EasyBuild

EasyBuild is a software build and installation framework that allows you to manage (scientific) software on High Performance Computing (HPC) systems in an efficient way.

EasyBuild 4.4.2 supports 2469 different software packages (incl. toolchains, bundles):</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:210&amp;rev=1641222879&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-01-03T15:14:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>210</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:210&amp;rev=1641222879&amp;do=diff</link>
        <description>Back

For other years view: 2020, 2019, 2018, 2017, 2016, 2015, 2014, 2013, 2012, 2011 ...

2021 Queue Usage
  2021 Totals        HPC Cluster                          



/* import total into work.one */


/* import total into work.one */

data two; set one; if var2 eq &#039;total&#039; and var3&lt;50000; run;

title1 j=c &#039;Running (green line) versus Pending (red line)Jobs&#039;;
title2 j=c &#039;Queue: All (max is 2056)&#039; and pending &lt; 50,000;
title3 j=c &#039;Covers time period 01 JAN 2021 to 31 DEC 2021&#039;;

axis1 label=(&quot;…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:211&amp;rev=1646153438&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-03-01T16:50:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>211</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:211&amp;rev=1646153438&amp;do=diff</link>
        <description>Back

DMTCP CRAC

This is a new DMTCP(&lt;https://github.com/dmtcp/dmtcp.git&gt;) plugin to checkpoint- restart CUDA application with noval split-process architecture. 

	*  &lt;https://github.com/JainTwinkle/CRAC-early-development&gt;
	*  &lt;http://dmtcp.sourceforge.net/&gt;

CRAC consists of the plugin on top of DMTCP.

This software runs in the original directory

Compilation needs gcc</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:212&amp;rev=1646246449&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-03-02T18:40:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>212</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:212&amp;rev=1646246449&amp;do=diff</link>
        <description>Back

HPC SDK

	*  &lt;https://docs.nvidia.com/hpc-sdk/index.html&gt;
	*  v 22.2
	*  /share/apps/CENTOS7/nvidia/hpc_sdk/22.2

The NVIDIA Software Development Kit (SDK) Manager is an all-in-one tool that bundles developer software and provides an end-to-end development environment setup solution for NVIDIA SDK. Think</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:213&amp;rev=1771534466&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-02-19T20:54:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>213</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:213&amp;rev=1771534466&amp;do=diff</link>
        <description>Back

New Head Node

We&#039;re embarking on a transition to a new head/login node name cottontail2. This server will be running Rocky 8 operating system. Early design ideas can be found at Cottontail2, all pre-pandemic.  We are staying with a 1G ethernet network as we could not find 10G switches. Maybe in the near term we can upgrade.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:214&amp;rev=1692375593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-08-18T16:19:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>214</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:214&amp;rev=1692375593&amp;do=diff</link>
        <description>Back

Tada

Introducing our new login node cottontail2. It is a server designed to run the Slurm scheduler and will sport the OpenHPC v2.4 software stack (External Link). We are deploying the Slurm/Warewulf recipe. You can find details at External Link: Rocky 8.5 with Architecture = (x86_64).</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:215&amp;rev=1765379258&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-12-10T15:07:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>215</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:215&amp;rev=1765379258&amp;do=diff</link>
        <description>Back

OpenHPC Software

This list of software is compiled for Rocky 8 using the OpenHPC v2.4 gnu9-openmpi4 toolchain (in your default environm,ent). For gpu applications CUDA 11.6 is the default. That module cuda/11.6 will automatically load for those applications.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:216&amp;rev=1654632458&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-06-07T20:07:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>216</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:216&amp;rev=1654632458&amp;do=diff</link>
        <description>Back

Warewulf, ohpc 2.4

There are other pages to view but this is my latest ...

	*  Warewulf Golden Image

stateless

First we create templates network.ww and ifcfg-eth0.ww

This node n59 is bare metal with just a 16G usb stick attached to system board (DOM) to hold operating system. Legacy boot.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:217&amp;rev=1656078796&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-06-24T13:53:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>217</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:217&amp;rev=1656078796&amp;do=diff</link>
        <description>Back

Slurm entangles

So, vaguely I remember when redoing our K20 gpu nodes I had troubles with that ASUS hardware and Warewulf 3.6. Now I have deployed a production cluster using OpenHPC 2.4, Rocky 8.5 and Warewulf 3.9 version. Same deal. Do not know what is going on but just documenting.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:218&amp;rev=1750347824&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-06-19T15:43:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>218</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:218&amp;rev=1750347824&amp;do=diff</link>
        <description>Back

Getting Started with Slurm  Guide

	*  The following resources are now (7/1/2022) managed by Slurm on our new head/login node cottontail2.wesleyan.edu
	*  You must ssh directly to this server (like you do connecting to greentail52) via VPN
			*  ssh username@cottontail2.wesleyan.edu</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:219&amp;rev=1668607317&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-11-16T14:01:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>219</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:219&amp;rev=1668607317&amp;do=diff</link>
        <description>Back

Slurm Consumable Resources

It is important to define as many resources your job needs to run. This allows Slurm to run multiple jobs per node if resources are available (given our configuration).

Monitoring the allocated resources to your job will provide feedback if your</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:220&amp;rev=1719845438&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-07-01T14:50:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>220</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:220&amp;rev=1719845438&amp;do=diff</link>
        <description>Back

NFSoRDMA

Previously used IPoIB, consult this page External Link

With newer hardware (storage and compute nodes) and an EDR Infiniband switch (expensive!) we will try NFSoRDMA.

&lt;https://enterprise-support.nvidia.com/s/article/howto-configure-nfs-over-rdma--roce-x&gt;

Remote Direct Memory Access supposedly gets better performance than IPoIB. Clients (compute nodes) fetch data directly from storage server&#039;s memory, so the remote storage</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:221&amp;rev=1678802358&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-14T13:59:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>221</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:221&amp;rev=1678802358&amp;do=diff</link>
        <description>Back

Infiniband Monitoring

The NVIDIA Firmware Tools (MFT) is a toolset to generate a standard or customized NDIVIA firmware image Querying for firmware information. It is required for ibswinfo which can monitor unmanaged Infiniband switches. Our new Infiniband switch is a</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:222&amp;rev=1678111693&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-06T14:08:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>222</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:222&amp;rev=1678111693&amp;do=diff</link>
        <description>Back

mdadm recreate array

Something went wrong and a compute is complaining some array is corrupt. It was 4x 1T 7.2K rpm disks arrayed together with mdadm to provide /localscratch2tb for heavy IO Gaussian jobs.

This is the process ...



# first wipe the disk and partitions for sd[a-d]

[root@n74 ~]# wipefs --all --force /dev/sda1;  wipefs --all --force /dev/sda
/dev/sda1: 4 bytes were erased at offset 0x00001000 (linux_raid_member): fc 4e 2b a9
/dev/sda: 8 bytes were erased at offset 0x00000…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:223&amp;rev=1695070609&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-09-18T20:56:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>223</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:223&amp;rev=1695070609&amp;do=diff</link>
        <description>Back

cuda toolkit

Upgrading Cuda to latest drivers and tooltkit that supports our oldest gpu model the K20m gpus found in nodes n33-n37 (queue mwgpu). Consult the page on previous K20m upgrade K20 Redo

For legacy hardware find the latest legacy driver here</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:224&amp;rev=1705070176&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-12T14:36:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>224</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:224&amp;rev=1705070176&amp;do=diff</link>
        <description>Back

Recipe for n38-n45 conversion of openlava/centos6 to slurm/centos7.

First install “server with GUI” via USB installation media. Enter BIOS (delete key). Set Date&amp;Time and boot order (Removable, USB, Cd&amp;DVD, Hdd). Reclaim disk space.. Kdump disabled.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:225&amp;rev=1716300402&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-21T14:06:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>225</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:225&amp;rev=1716300402&amp;do=diff</link>
        <description>Back

Cuda

Upgrading Cuda to latest drivers and tooltkit that supports our GeForce RTX 2080 SUPER (and Ti) gpu models (queues exx96 and amber128). Before we embark doing all nodes, we need to test backward compatibility and assess how troublesome the upgrade might be.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:226&amp;rev=1778170482&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-07T16:14:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>226</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:226&amp;rev=1778170482&amp;do=diff</link>
        <description>Back

TrueNAS/ZFS m40ha

Notes on the deployment and production changes on our 500T IXsystem m40ha storage appliance.

Fixed the date on controllers by pointing ntpd to 129.133.1.1

ES 60 middle amber light blinking which is ok, green health check on right</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:227&amp;rev=1729685785&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-23T12:16:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>227</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:227&amp;rev=1729685785&amp;do=diff</link>
        <description>Back

HPC Monitoring

We used to use Zenoss as our health and alerting monitor (Zenoss).

Because of a research project needing quick insight into resource consumations on compute nodes we first quickly installed Ganglia.  Not developed anymore but a great tool. You can quickly download centos 8 packages and grab centos 7 packages. For the latter you need to change the yum repo URLs to (and uncomment the mirrorlist URLs)</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:228&amp;rev=1763391323&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-17T14:55:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>228</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:228&amp;rev=1763391323&amp;do=diff</link>
        <description>Back

IB BIOS settings

	*  applies to nodes n102-n107
	*  NFSoRDMA, see NFSoRDMA
	*  from support at Microway
	*  then fix NFS mount on n103



   Here are the BIOS setting we set for those system prior to shipping;

     Start by entering the BIOS and taking the &quot;Optimized Defaults&quot; (F3)

      Then going down through the menus on the &quot;Advanced&quot; tab in the
BIOS...

      Boot Feature;
          Quiet Boot = disabled
          Wait for &quot;F1&quot; if Error = disabled

      CPU Configuration:
        …</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:229&amp;rev=1740077670&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-20T18:54:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>229</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:229&amp;rev=1740077670&amp;do=diff</link>
        <description>Back

Recipe for RTX4070ti nodes



# image using usb stick rocky 8.10
# enter bios set date, note MAC address
vi /etc/selinux/config
vi /etc/ssh/sshd_config

# SKIP NO WAREWULF
vi /etc/default/grub
# add inet.ifnames=0 to CMD LINE
grub2-mkconfig -o /boot/grub2/grub.cfg
reboot
# add 10 to nodename for ip
cd /etc/sysconfig/network-scripts/
vi ifcfg-en01
mv ifcfg-eno1 ifcfg-eth0
vi ifcfg-eno2
mv ifcfg-eno2 ifcfg-eth1
systemctl restart NetworkManager
ifconfig
# SKIP NO WAREWULFy

# IPTABLES
yum ins…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:230&amp;rev=1742845065&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-03-24T19:37:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>230</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:230&amp;rev=1742845065&amp;do=diff</link>
        <description>Back

cuda-checkpoint

Newly developed cuda tool to keep track of. Sounds initially good but there some items to check/test out.

Also need to track DMTCP CRAC tool that almost worked.

	*  &lt;https://developer.nvidia.com/blog/checkpointing-cuda-applications-with-criu/&gt;

CRIU (Checkpoint/Restore in Userspace) is an open-source checkpointing utility. Works with cuda driver 550 and higher (although I do not see it in exx96&#039;s cuda-12.4 installation). But it is present in test&#039;s (11.6) and mwgpu256&#039;s …</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:231&amp;rev=1762529519&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-07T15:31:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>231</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:231&amp;rev=1762529519&amp;do=diff</link>
        <description>Back

GPU checking

Some excellent articles from &lt;https://support.exxactcorp.com&gt;

	*  &lt;https://support.exxactcorp.com/hc/en-us/articles/30339242702103-How-to-Check-for-GPU-Errors?input_string=hardware+error+messages&gt;

	*  &lt;https://support.exxactcorp.com/hc/en-us/articles/30923566578071-GPU-Troubleshooting-Guide-Resolving-ECC-Errors?input_string=hardware+error+messages&gt;

	*  &lt;https://support.exxactcorp.com/hc/en-us/articles/25920931720343-How-to-Run-GPU-Burn?input_string=hardware+error+messages&gt;…</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:232&amp;rev=1769722567&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-29T21:36:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>232</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:232&amp;rev=1769722567&amp;do=diff</link>
        <description>Back

Lampy

This is a fantastic forehead bang-on-desk exercise. So many applications wrapped together it is an enormous puzzle. I was greatly helped by following a recipe of student Max of the Starr Lab. Hopefully Max can report some performance results later as that was the driver to do this.</description>
    </item>
    <item rdf:about="https://dokuwiki.wesleyan.edu/doku.php?id=cluster:tmp&amp;rev=1175632235&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-03T20:30:35+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>tmp</title>
        <link>https://dokuwiki.wesleyan.edu/doku.php?id=cluster:tmp&amp;rev=1175632235&amp;do=diff</link>
        <description>a page to feed vendors log files</description>
    </item>
</rdf:RDF>
