occam capstone spring 2015 occam: repository for open-access, collaborative computer architecture...

3
OCCAM capstone Spring 2015 OCCAM: repository for open-access, collaborative computer architecture research. Too many simulators to test too many parameters with too many configurations and too many input files… See video at http://www.occamportal.org to discover how we are changing the way architecture research is done! • Contacts: [email protected], [email protected]

Upload: owen-ramsey

Post on 29-Dec-2015

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: OCCAM capstone Spring 2015 OCCAM: repository for open-access, collaborative computer architecture research. Too many simulators to test too many parameters

OCCAM capstone Spring 2015• OCCAM: repository for open-access, collaborative computer

architecture research. • Too many simulators to test too many parameters with too

many configurations and too many input files…• See video at http://www.occamportal.org to discover how

we are changing the way architecture research is done! • Contacts: [email protected], [email protected]

Page 2: OCCAM capstone Spring 2015 OCCAM: repository for open-access, collaborative computer architecture research. Too many simulators to test too many parameters

Project Ideas1. Create a novel visualizer for data hosted in the OCCAM

repository.– Learn and apply web programming tools (js, jQuery, d3)– Create your own UI– Instead of boring graphs let’s...

» Visualize the data in several dimensions» UI to animate graphs, including zoom» Give constraints and intuitively select the type of

graphs/charts » Voice interface? Eye gaze? Heatmaps? Clustering?» …

Page 3: OCCAM capstone Spring 2015 OCCAM: repository for open-access, collaborative computer architecture research. Too many simulators to test too many parameters

Project Ideas3. Generate automatic analysis of data from experiment

results hosted in OCCAM.[Machine learning? Statistics? Heavy-duty visualizations? Python? R? Matlab?]

• Automatic reporting of variables that are or are not correlated in the output.

• Find error/bugs (e.g., output is not “natural,” or does not follow a “good” function)