################################################ # To Do ################################ Color issues: • Draggable arrow should exactly match the shade of the corresponding data series UI issues: • Add "Show Platform graphs" check boxes in same place as beetle control. • Improve layout for in-graph readouts, current version overlaps • Better graphics/characters? Beetle will be undesirable for some? Gathering data while time is stopped: • when paused or stopped and hand is manually rotated or rotated by the slider, bugs should update • If time is stopped, update theta for bugs if they are moved by hand Performance • Improve performance 30% app is in HTMLNode update • There is still a performance leak. After about 10-15 minutes it is now crawling. -this is due in part to time series filling up in "live mode", early enough data should be discarded Also, it appears that angular velocity that is labeled platform is actually the ladybug. I can see this when I pick up the bug. Omega platform stops graphing while ladybug keeps graphing. I can’t see this on alpha graph but almost see a change in line color after I put her back down so wonder if you are actually stopping her graph for acceleration also when I pick her up. If this is the case, then the two colors for platform and ladybug for angular acceleration are too similar to distinguish. >>Is this resolved now? The beetle graphs show up when you put him on the platform. He can have been off the entire time and then when I put him on, his data appears. When I take him off, his data disappears. This is odd. I can see why new data won’t graph when he’s off but not why all his data comes on and off depending on when he’s on the platform. This gives the graphs the feeling that they are a physical thing rather than an abstract representation of his motion. >>Perhaps as soon as the user grabs the second character, his graphs should become visible (and his checkbox becomes selected). >>Then to hide the graph, the user unchecks the checkbox. >>The idea is that as soon as the user expresses an interest in the beetle, its graphs become visible >>As opposed to our previous version, which assumed the user only wanted to see data if the bug was on the platform Lower Priority: • Bug: Mouse gets disassociated from ladybug character after trying to drag out of bounds. • Improve correspondence of graph time scale with wall-time clock speed • Shadow projections should be considered after AAPT. • Possible interview question: bug icon at tip of graph to improve conceptual connection • Torque mode: Should be able to "spin" the wheel (i.e. drag, let go, and have it continue to spin, at least in friction mode) • Symbol key should appear near the mouse when "show symbol key" pressed • On graph readouts should have a better (fixed) layout. (numbers could be aligned) • some pswing components are fuzzy -can't reproduce this on development machine • typing in a box without pressing enter should work -can't solve this in general, since we don't know when the user has finished entering input • Reset all doesn't reset Angle readouts -can't reproduce this • Bug: Beetle graph appears empty before beetle is on the platform, why isn't this interpolating like the other graphs? -values for RotationBody's angleSeries aren't set while off platform • Consolidate MovingMan, Forces1D, Ramp, Rotation, Torque into a single codebase. ################################################ # Implementation issues ################################ • Factor MotionBodyState and MotionBodySeries into a single object • Implementation for setting platform angle by setting character angle is fragile • RotationBody should have internal representation for angular velocity and angular acceleration instead of relying on RotationPlatform's instance? • Better inherent support for different units in charts -ControlGraphSeries should have an optional transform object. ################################################ # Questions: ################################ • Got rid of abbreviations like (vx) on charts, do we want to show abbreviations (e.g. symbol for theta) for other series? -wait until interviews • Support for "missing values" in the series data (for when characters are being dragged by the user and don't have values for angular data series) -7-19-2007: No missing values now -Current implementation linearly interpolates between previous and subsequent values -It would be fairly difficult to add a "missing value" feature -We could also consider just computing these values dynamically • There is still a very large delay on the v and a vectors when dragging the bugs around on my machine … it makes it look like the arrows are pointing outwards for acceleration, not inwards when I move in a circle by hand. -Current implementation uses a mix of circular regression and 1-d derivatives with time delay; let me know if this is sufficient. • When you set angular position by hand … currently only lady-bug position affected… should we make similar change in theta to 2nd bug if he is on graph? So if ladybug is at 100 rads and other bug is at 110 rads, then set rads to 0, end up with ladybug at 0 rads and other bug at 10 rads??? NOT sure about this? >>No, I think the settable values should only apply to the ladybug. It will be too confusing/overloaded to make it so you can type in values >>for both characters. ################################################ # Interview: ################################ • how should update mode be set based on typing in text boxes? -current implementation: final edit decides update mode. -For example, if the user wants theta=1, omega=2, alpha=3 and sets them in that order, it will work properly -however, if she enters theta last, then the update mode will be set to "constant position" and therefore omega and alpha will be set to zero -interview on this ################################################ # Postponed: ################################ • Investigate acceleration model from Motion2D simulation as a possibility for replacing the implementation in rotation.