Differences

This shows you the differences between two versions of the page.

--- cluster:189 [2020/01/11 17:27]
hmeij07
+++ cluster:189 [2020/01/11 17:54]
hmeij07 [Funding Policy]
@@ Line 12: / Line 12: @@
 The Wesleyan HPCC is part of the **Scientific Computing and Informatics Center** ([[https://www.wesleyan.edu/scic/| SCIC ]]).  The SCIC project leader is appointed by the Director of the **Quantitative Analysis Center** [[https://www.wesleyan.edu/qac/| QAC ]]. The Director of the QAC reports to the Associate Provost. The hpcadmin has a direct report with ITS Deputy Director and an indirect report with QAC Director.
+The QAC has an [[https://www.wesleyan.edu/qac/apprenticeship/index.html|Apprenticeship]] Program in which students are trained in Linux and several program languagues of their choice and other options. From this pool of students some become the QAC and SCIC helpdesk and tutors.
+==== Funding Policy ====
+After an 8 year run of the HPCC, and a drying up of grant opportunities at NSF, it was decided to explore self-funding so the HPCC effort could continue without external dependence on funds. A report was made of the HPCC progress including topics such as Publications, Citations, Honors Theses, Growth in Jobs Submitted, Pattern of Pending Jobs, and General Inventory. The report summary can be viewed at this page [[cluster:130| Provost Report ]]. This report was discussed between Provost and HPC Advisory Group.
+Several months later a pattern emerged.  The Provost would annually contribute $25K if the HPC user base raised $15K annually.  That would amount to $160K in 4 years enough for a hardware refresh or new hardware acquisition.  Finances also contributed $10K for maintenance such as failed disks, network switches, etc, but these funds do not "roll over". Use it or loose it. All funds start July 1st.
+In order for the HPC user base to raise $15K annually, CPU and GPU hourly usage was deployed. A dictionary is maintained listing PIs and their members (students majors, lab students, grads, phd candidates, collaborators, etc).  Each PI then quarterly contributes to the user fund based on  a scheme yieldingq $15K annually.
+Here is 2019's queue usage [[cluster:188|2019 Queue Usage]] and 2019 contribution scheme.
+Contribution Scheme for 01 July 2019 onwards\\
+Hours (K) - Rate ($/CPU Hour)\\
+  * 0-5 = Free
+  * >5-25 = 0.03
+  * >25-125 = 0.006
+  * >125-625 = 0.0012
+  * >625-3125 = 0.00024
+  * >3125 = 0.000048
+A cpu usage of 3,125,000 hours/year would cost $ 2,400.00 \\
+A gpu hour of usage is 3x the cpu hourly rate.\\
-Add scheme 2016 2019
-Passwd line count 25 coll 200 class
-year review with provost link to paper (honors theses)
-funding policy
-priority access policy
-add VA questions
 user base stats, annual meeting, spring reading week
-queue usage stats link
-adv group details, administrative
 hpcc stats cpu cores, gpus, mem, hdd (rough) link to guide
 latest deployment: nvidia gpu cloud on premise (docker containers) link
-Add funding model
-contrib scheme contrib code ...
- Links to hist use. Usage 2019.
-x gpu vs cpu.
 Script preempts nodes every 2 hours.

DokuWiki

User Tools

Site Tools

Differences

Page Tools