Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
|
Last revision
Both sides next revision
|
cluster:189 [2020/02/27 13:12]
hmeij07 [Funding Policy] |
cluster:189 [2020/06/19 08:53]
hmeij07 |
| Several months later a pattern emerged. The Provost would annually contribute $25K **//if//** the HPCC user base raised $15K annually in contributions. These funds would "roll over". That would amount to $160K in 4 years, enough for a hardware refresh or new hardware acquisition. Finances also contributed $10K annually for maintenance such as failed disks, network switches, etc ... but these funds do not "roll over". Use it or loose it. All fund cycles restart July 1st. | Several months later a pattern emerged. The Provost would annually contribute $25K **//if//** the HPCC user base raised $15K annually in contributions. These funds would "roll over". That would amount to $160K in 4 years, enough for a hardware refresh or new hardware acquisition. Finances also contributed $10K annually for maintenance such as failed disks, network switches, etc ... but these funds do not "roll over". Use it or loose it. All fund cycles restart July 1st. |
| |
| In order for the HPCC user base to raise $15K annually, CPU and GPU hourly usage monitoring was deployed (using Openlava ''lsacct'' accounting). A dictionary is maintained listing PIs with their associated members (student majors, lab students, grads, phd candidates, collaborators, etc). Each PI then quarterly contributes to the user fund based on a scheme supposedly yielding $15K annually. | In order for the HPCC user base to raise $15K annually, CPU and GPU hourly usage monitoring was deployed (using scripts parsing the ''lsb.acct'' file). A dictionary is maintained listing PIs with their associated members (student majors, lab students, grads, phd candidates, collaborators, etc). Each PI then quarterly contributes to the user fund based on a scheme supposedly yielding $15K annually. |
| |
| Here is queue usage for 2019 [[cluster:188|2019 Queue Usage]] and below is listed the 2019 contribution scheme. | Here is queue usage for 2019 [[cluster:188|2019 Queue Usage]] and below is listed the 2019 contribution scheme. |
