This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
cluster:153 [2017/03/02 15:29] hmeij07 |
cluster:153 [2017/03/21 13:44] hmeij07 |
||
---|---|---|---|
Line 30: | Line 30: | ||
* https:// | * https:// | ||
* https:// | * https:// | ||
+ | * Probably more aligned with our goals, click on PDF | ||
+ | * http:// | ||
+ | * Regional Access a report to NSF, good read | ||
+ | * https:// | ||
+ | * key part: the local aspect is important (flexibility and personalized attention) to ensure researcher success and productivity...collaborating at the campus and regional levels is an important aspect in building the services | ||
* XSEDE https:// | * XSEDE https:// | ||
* for research this involves writing XSEDE proposals to get time allocations, | * for research this involves writing XSEDE proposals to get time allocations, | ||
Line 39: | Line 44: | ||
**Until we have a 2017 CC* RFP announcements** this is a list of random thoughts to keep track of. | **Until we have a 2017 CC* RFP announcements** this is a list of random thoughts to keep track of. | ||
+ | * 2016 Parsing of proposal language (Science-driven requirements are the primary motivation for any proposed activity.) | ||
+ | * Data Driven Multi-Campus/ | ||
+ | * NSF strongly urges the community to think broadly and not simply rely on traditional models when considering multi-campus and/or multi-institutional cyberinfrastructure | ||
+ | * Proposals are expected to be science-driven | ||
+ | * Proposals...significant impact on the multi-campus, | ||
+ | * methods for assured federated access | ||
+ | * Multi-institution/ | ||
+ | * across a range of disciplines, | ||
+ | * Cyber Team,2-4 awards, | ||
+ | * This program area seeks to build centers of expertise and knowledge in cyberinfrastructure | ||
+ | * Proposals in this area should describe the multi-institutional science-driven needs | ||
+ | * Proposals ... engagement, interactions, | ||
+ | * Proposals ...areas of expertise, such as networking, distributed data management, and scientific computing. | ||
+ | * Proposals may request up to four full-time equivalents (FTE) for up to three years (inside of $1.5M???) | ||
+ | * Proposals should describe plans for broadening participation, | ||
* Leverage a common HPC environment among small, northeast, colleges | * Leverage a common HPC environment among small, northeast, colleges | ||
* we do science too (compare to larger colleges) | * we do science too (compare to larger colleges) | ||
+ | * need to drive proposal with unique science efforts by each college <--- important! | ||
+ | * think about how to build the data driven multi campus effort | ||
* 1-3 sysadmin FTEs covering 3-6 colleges for 3 years | * 1-3 sysadmin FTEs covering 3-6 colleges for 3 years | ||
* redundancy in sysadmin coverage, round robin | * redundancy in sysadmin coverage, round robin | ||
* each member to assess how to provide funding past year 3 | * each member to assess how to provide funding past year 3 | ||
- | * Possible Members (* indicates | + | * Possible Members (underlined=informally contacted, bolded=interested |
- | * Hamilton, | + | * Hamilton, |
+ | * **Lafayette**, engineering college HPC | ||
+ | * **Middlebury**, ? | ||
+ | * **Swarthmore**, | ||
+ | * Trinity, | ||
+ | * __Wellesley__, ? | ||
+ | * **Wesleyan**, Gaussian HPC, text mining HPC | ||
+ | * **Williams**, Islandora DMP | ||
* Each member will do an internal survey of local computing and storage desires, put together 1-2 racks | * Each member will do an internal survey of local computing and storage desires, put together 1-2 racks | ||
* gpu, cpu, hybrid of such, visualization, | * gpu, cpu, hybrid of such, visualization, | ||
Line 68: | Line 97: | ||
* of sysadmin group | * of sysadmin group | ||
* of advisory group | * of advisory group | ||
- | * Data Management Plan | + | * Data Management Plan (DMP) |
* To satisfy NSF public data access policy and distribution | * To satisfy NSF public data access policy and distribution | ||
* One site for all (Islandora, Dspace, ???). One members' | * One site for all (Islandora, Dspace, ???). One members' |