It is with great pleasure that ASU Research Computing announces the inaugural Research Computing Speaker Series, presented by the Working Group for Research Computing. The series will include two to three speakers each semester from a variety of disciplines and will highlight the real-world applications of high performance computing. The first event kicks off in March 2016.
Computing the Past
J. Daniel Rogers
Curator of Archaeology, Department of Anthropology
Smithsonian National Museum of Natural History
Thursday, March 24, 2016
Biodesign Institute (BDB) Auditorium (B105), Tempe campus [map]
Register today — seats are limited
About the Talk
The past is a mysterious and complicated land. To make sense of such a place, many archaeologists now employ sophisticated analytical tools in combination with older methods. Advances in computational capabilities, especially in agent-based modeling and network analysis have opened new paths for the study of social dynamics and have sparked a shift in theoretical developments. As archaeology engages with the cyber research future the challenges of massive data, generative methodologies, and computing capacity have taken on a new importance.
About J. Daniel Rogers, Ph.D.
Rogers received a Ph.D. in Anthropology from the University of Chicago. Over his career, he has conducted field research in the Southwest, the Great Plains, the Caribbean, Mexico, Peru, and eastern Asia. Since 2002, he has studied the early empires of Inner Asia and developed computational models to analyze the social implications of climate change. His research topics also include the role of colonialism, culture contact, and emerging social complexity.
About the Research Computing Working Group
The Research Computing Working Group considers and recommends resources, policies, plans, and capabilities that affect faculty research computing and scholarly activities. To learn more about Research Computing, please visit researchcomputing.asu.edu or email Marisa Brazil, Research Computing Program Manager, at email@example.com.