Difference between revisions of "Dynamic Runtime Community Meeting"
| Line 3: | Line 3: | ||
Several computing communities have recognized a common need for dynamic runtimes to support our future computing infrastructure. Having arisen from common needs, but developed in separate application communities we can learn from our experiences and build a common community. We are going to hold a workshop in the Washington DC area in late July that will bring people together to discuss common experiences | Several computing communities have recognized a common need for dynamic runtimes to support our future computing infrastructure. Having arisen from common needs, but developed in separate application communities we can learn from our experiences and build a common community. We are going to hold a workshop in the Washington DC area in late July that will bring people together to discuss common experiences | ||
| − | We foresee a 2-day agenda in | + | We foresee a 2-day agenda in four parts |
1) Retrospectives from several projects on what we | 1) Retrospectives from several projects on what we | ||
| − | learned and how it applies to each application domain. 1/2 day | + | learned and how it applies to each application domain. Focus on application experience: 1/2 day |
| − | + | 9:00am - 12:00pm | |
| − | + | ||
| − | 3) an open session that defines a list of topics for | + | 2) Talks on the common elements that have been learned among the projects: 1/2 day |
| + | |||
| + | 1:00pm - 5:00pm | ||
| + | |||
| + | 3) A short session on the characteristics of prospective hardware that will need to be managed: 2 hours | ||
| + | |||
| + | 9:00am - 11:am | ||
| + | |||
| + | 4) an open session that defines a list of topics for | ||
common community work for the next year or two. This can also be a | common community work for the next year or two. This can also be a | ||
| − | blueprint for federal managers to use as RFP material. | + | blueprint for federal managers to use as RFP material.: 1/2 day |
| + | |||
| + | 11:00am - 4:00pm with a beak for lunch | ||
Revision as of 21:45, 22 May 2017
Join us July 25-26, 2017 in the Washington DC Area
Several computing communities have recognized a common need for dynamic runtimes to support our future computing infrastructure. Having arisen from common needs, but developed in separate application communities we can learn from our experiences and build a common community. We are going to hold a workshop in the Washington DC area in late July that will bring people together to discuss common experiences
We foresee a 2-day agenda in four parts
1) Retrospectives from several projects on what we learned and how it applies to each application domain. Focus on application experience: 1/2 day
9:00am - 12:00pm
2) Talks on the common elements that have been learned among the projects: 1/2 day
1:00pm - 5:00pm
3) A short session on the characteristics of prospective hardware that will need to be managed: 2 hours
9:00am - 11:am
4) an open session that defines a list of topics for common community work for the next year or two. This can also be a blueprint for federal managers to use as RFP material.: 1/2 day
11:00am - 4:00pm with a beak for lunch
