Difference between revisions of "LittleFe:application"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
* Items the three application types have in common: | * Items the three application types have in common: | ||
** Individual and institutional commitment as shown with a letter outlining their commitment to incorporating the LittleFe/BCCD into their curriculum and to the development of new parallel programming or cluster computing curriculum modules. On institutional letterhead signed by someone(s) with the authority to make those commitments. | ** Individual and institutional commitment as shown with a letter outlining their commitment to incorporating the LittleFe/BCCD into their curriculum and to the development of new parallel programming or cluster computing curriculum modules. On institutional letterhead signed by someone(s) with the authority to make those commitments. | ||
| − | ** Take-back clause, that is after one year of quarterly check-ins if the plans outlined in the letter have not been met we can recall the unit. This and related policies will need to be vetted by the "granting agency", ACM/EAPF. | + | ** Take-back clause, that is after one year of quarterly check-ins if the plans outlined in the letter have not been met we can recall the unit. This and related policies will need to be vetted by the "granting agency", ACM/EAPF. Check with Donna Capo. |
* Items that are different for each application: | * Items that are different for each application: | ||
** The build-it-yourself options require that a team of two people (faculty and student or two faculty) apply. | ** The build-it-yourself options require that a team of two people (faculty and student or two faculty) apply. | ||
Revision as of 16:18, 3 February 2011
Application for an Intel/EAPF LittleFe
Notes:
- Flavors of application:
- Assembled unit delivered to your institution.
- Attend the Intermediate Parallel Programming and Cluster Computing workshop at OU on XXX
- Attend the Build-out hosted by the SC Education Program at SC11 in Seattle
- Items the three application types have in common:
- Individual and institutional commitment as shown with a letter outlining their commitment to incorporating the LittleFe/BCCD into their curriculum and to the development of new parallel programming or cluster computing curriculum modules. On institutional letterhead signed by someone(s) with the authority to make those commitments.
- Take-back clause, that is after one year of quarterly check-ins if the plans outlined in the letter have not been met we can recall the unit. This and related policies will need to be vetted by the "granting agency", ACM/EAPF. Check with Donna Capo.
- Items that are different for each application:
- The build-it-yourself options require that a team of two people (faculty and student or two faculty) apply.
Assembled and Delivered Units
- This option is only available to institutions selected by representatives of Intel and the SC Education Program. Between 5 and 10 LittleFe units will be available through this mechanism.
Intermediate Parallel Workshop @ OU
- Ability to arrive by Sunday morning for the build session which will take place Sunday afternoon.
- Responsible for shipping costs from OU back to their home institution (that is an extra bag charge if they are flying).
- Between 5 and 10 LittleFe units will be available through this mechanism.
Build-out at SC11 in Seattle
- Availability on either Sunday, Monday, Tuesday or Wednesday afternoon of the conference. As part of the application they commit to which one(s) they are available for so we can ensure that we have 2, 2, 3 and 3 groups to schedule over the 4 days.
- Responsible for shipping costs from SC11 back to their home institution (that is an extra bag charge if they are flying).
- Between 5 and 10 LittleFe units will be available through this mechanism.
