5-May-2003 DEMO DAY PRESENTATION INTRODUCTION * About screen * So we it's still web-based, for use at Brown, but can be extended for use at other schools as well * We're hoping to get into the Harvey Project * Successful in that students can experiment with values and see results * We can test effectiveness of program by checking test scores in future BI080 classes * We started simpler, became kinda busy, but you can still see what's going on and not be wondering what does what, not be confused * Our program models A LOT of different factors in the system * Removed external links, in case addresses change * In the end, we still required everybody to program THINGS THAT WE DID * Visualizer - Relation between resistance-blood flow and cardiac output - Histogram of cardiac output - Heart-blood flow relation to stroke volume - Hiliting of animation to tie it to values more - Logging textbox - Help rollovers - text from Prof. Stein - Valve timing - Oxygenation red->blue, deoxygenation blue-red - Sliders - undo/redo, scrollbar-like behavior, control-clicking arrows - Default button - Pause button - Fields: blood pressure, MCFP, RAP, C.O. = H.R. x Stroke Volume - Contractility models correctly now (i.e. strong/weak heart) * Grapher - Grapher: line thickness, labels (which are static, b/c axes don't change) - Flexible in terms of controlling margins, tick marks, functions - Dynamically redraws, very important part of the program and visualization - Show intersection - Show default curves (similar to show default animation) - Vectors weren't too practical * Math - Meaning of math behind it all - "Real" equation has 23 unknowns ... we're only dealing with 5 variables in our program - Constructing the curves - What's wrong with our model * Scenarios - Scenario system: stop, rewind, step back, step forward - 3 scenarios: list of values and text strings - Enabling/disabling of buttons at appropriate times - Graph and animation update for each stage - Scenario textbox * Tutorials - Tutorials - very thorough, should be like an online-manual PROCESS, WHAT WAS DIFFICULT * Director is a little buggy and slow, Java probably would have been better * Too memory intensive with so many cast members and sprites, even on these computers * Animation timing, coordinates, vector drawings, grapher/math/animation slowdown * Scripting got real messy real fast * Dealing with vectors - that was the first big milestone, which was our prototype demo * Vectors like resizing themselves when we don't want them to - hard when we overlay multiple vectors * Linking is messy THINGS WE DIDN'T GET TO * Scenario-editor, which Prof. Stein showed interest in, especially for future work * Different screen sizes, dynamic resizing * Flowchart (abandoned) * Reference (i.e. glossary), but not necessary b/c Prof. Stein didn't require it * Sounds and narration * Math tutorial (math is not as interesting as it could be, because the model is simplified) * Can't change the type of heart RECOMMENDATIONS/REFLECTIONS * Director probably not the best for speed optimization, it tries to do more than we really need * Visualizer looks simple, but underlying code is very complex * Definitely a project worth doing; valuable experience * Interesting future projects may involve porting our code over to Java, adding new scenarios/features, and other neat stuff :)