RELEASE NOTES - 4/20/2011 Contrary to most release notes, this is more a log of the work that has been done on OpenTrack. With the 0.5.10 release, OpenTrack is now quite a lot more mature than for the 0.3.x series. It is now a Firefox extension which means that most users will be able to install it, and dependent on the build, may actually encounter automatic upgrading. (This will, of course, completely bork my Sourceforge statistics, but oh well.) It sports a number of improvements over earlier versions including numerous bug fixes (see below), as well as: 1) Marker layovers on images 2) Vector layovers on images 3) Improved graphing capabilities 4) Improved autotracking 5) A report editor (replete with equation editor) to aid students in preparing work done in OpenTrack. 6) An image analysis tab to enable distance and angular analysis of images in addition to video. 7) An analysis tab to enable users to plot one variable versus another 8) CTRL-SHIFT-K enables the Firefox web console thus exposing any and all variables and functions in OpenTrack to the javascript command line. This can be useful for advanced users. 9) Ability to adjust threshholding of images to better autotrack. 10) Associated physics labs and videos that are downloadable via the Tutorials tab. Thanks to the jsMath folks for the hard work on their equation editor which is included in this release. Likewise, thanks to both the ffmpeg (LGPL licensed) and the Firefogg (GPL v3) folks that turned ffmpeg and ffmpeg2theora into a Firefox extension. Their compiled binaries for Windows and Linux are included in this release. Note that OpenTrack is released as GPL 2 or later (see: http://www.gnu.org/licenses/gpl.html). todo-0.5.10.txt 1) Fix extended velocity/acceleration calcs JSvg/statlib.js: localRegDeriv(): endpoint effects still apparent - adjustment to algorithm needed 2) Fix vector appearance - should happen on clicking, not just on advance 3) On Analysis Tab: enable display of any variable 4) Allow export of all data in ASCII tab delimited format todo-0.5.9.txt 2011-01-18 In image analysis tab links are drawn first, and then image changes in l1_showImage(); - Fixed Loading image project does not seem to load images into thumbnail area - Fixed Thumbnail area is UGLY! - Better 2011-01-13 deal with blocking behavior of addImgLink popup - DONE fix manual tracking errors - DONE add img thumbnails to Image Analysis - in progress - need to find method to show thumbnails (xul button or image with event) - DONE, but not perfect 2010-10-15 1) Fix Main tab: specifically the "context help" doesn't look very good and needs to have a consistent appearance. - Done 2) Fix Main tab: the length of the markers, links and angles boxes is too long. Shorten to improve the appearance and accessiblity. - Push to 0.5.3 - Done 3) Fix Main tab: revisit how links and angles are added - Push to 0.6.0 a) If current scheme is kept, then only a single "Clicking marker/link/angle" radiogroup is needed. - Done b) Alternate scheme is to enable deletion of a link or angle from within the dialog box (this is slower for power users, but perhaps preferable for other types of users). c) If b) is implemented, then perhaps adding links and angles can occur from within the Links and Angles boxes. This entails rewriting how links and angles are updated. 4) Warn users if they are loading a video of too great a width. (In a later version, canvassed scaling can probably be applied). - Push to 0.6.0 5) Add a "Play" button to the viewer (it should automatically cycle). - Push to 0.6.0 6) Add an export video button to the viewer - this should create a video from what is displayed to canvas. This may be an 0.6.0 addition? 2010-10-12 *1) Some MacOSX issues with the editor. It seems that the path delimiter is undefined in some cases. I need to check for this OS. - DONE: 2010-10-14 2) Change default behavior in graphing so that nothing is selected rather than having everything selected. - Under work - can't seem to find it yet. *3) Allow users to find tutorials from any point within the program. Perhaps by using a "help" button. - DONE: Tutorials now have their own tab. 2010-10-14 4) Move some of the graphics options into the main tab where they are more accessible. 5) Find out why the darn fits sometimes plot jagged lines. This almost never happens, but it happens enough that it is noticable. 6) Give options such as precision, ndivs, etc. to users on graphics tab. *7) Possibly allow the report editor to be started directly from the FF "tools" menu. (Duplicate: See 16 for solution) 8) Allow users to select data to plot from the analysis tab. - Push to 0.5.3 9) Allow users to save/read data from analysis tab? (call it .atd [analysis tab data] format and make it ascii tab delimited) - Push to 0.5.3 *10) Reinitialize report editor selection array every time a new plot is created. This is causing untold hardship with students. - DONE 2010-10-14 *11) Fix report editor so that pressing enter on a table does not reload the table deleting all data - DONE 2010-10-14 *12) Fix reportEditor move up move down behavior so that multiple windows do not appear. - DONE 2010-10-14 *13) Allow report editor to open files anywhere on the harddrive. - DONE 2010-10-14 *14) On creating a new report, eliminate alert noise except in debug mode - DONE 2010-10-14. *15) Have report editor save on edit. DONE 2010-10-14 *16) Allow users easier access to loading a report when starting. - DONE 2010-10-14 ("Load Report" button placed on "Main" tab.) *17) Fix report concatenation (unzip first before grabbing images). DONE 2010-10-15 18) Fix load report from Main 19) 2010-09-09 So the guys at Mozilla (God bless 'em) have decided with little notice outside of bugzilla, to rip out XUL support except in the case of content loaded in chrome. This is regardless of allowing permissions via the prefs.js file. There are some hand-wavy explanations regarding security concerns. While I do understand that any web content may be insecure, it's not clear to me why XUL is any less secure than HTML, or why even local access with user granted permissions in an obscure prefs.js file is not secure. It seems to me that when you code for security you look for the URL. If it starts with chrome:// or file://, you're safe and you let the XUL load. If, on the other hand, it starts with http://, https://, ftp://, etc..., you don't let it load. This is a basic case structure. Of course there may be more to it than that, and as I am not a Mozilla developer, these comments are probably a tad unfair. However, considering that I chose to use Firefox instead of a webkit based browser or Qt due the XUL framework, I'm a bit miffed at these guys. The least they could have done was announce the intention publically and prominently a few months before hitting us with a beta (4.0 beta 5) that keeps any XUL from loading unless it is an extension. The bottom line is that although I thought I was at the very end of the development cycle for OpenTrack, it seems that now I am at the beginning of a new one wherein I need to change OT into an extension. There is sure to be breakage of all sorts. And it is likely to take some time to get things back together. On the plus side, if I can figure it all out, and I get lucky, this may may for an easier install for users via the *.xpi format and it may mean that I can rip out the update code which never really worked properly across all platforms. Today was a day that was supposed to be devoted to research, not running down loose ends on a project that was nearly "done". Sigh. More as developments emerge. In the meantime, after much panic and a ton of time (> 6 hours today), I have the basics up and running via the extension mechanism, although I can't seem to add markers. I suspect the same issues will occur with links and angles, although I'm not certain. It is possible that the events are not firing correctly in the beta version of the browser (4b5) or that events need to be triggered differently for extensions (though why, I wouldn't know), or that the onload function in otAddMarker.xul needs an additional timeout in order to see the clicked coordinates. 2010-08-11 otReport editor is basically done. This is a stand-alone or plugin editor that enables users to quickly create an HTML formatted report based on content generated in OpenTrack. What remains today is to: 1) Hook it into OT - Done 2) Allow users to generate a report based on selected graphs. - Done 3) Allow users to include (optionally) the current image on the canvas. - not yet but almost 4) Automatically generate report with a paragraph underneath each graph and a title. - Done 5) (More complicated) allow users to generate all fits to data separately. a) Need to fix JSvg and its legend b) Need to allow JSvg to render average and filled series c) ... 2010-07-27 1) New off-by-one error on manual tracking. The data seems to lead the video by a frame after tracking. In???? (check if frame is changing between act of marking and displaying and saving of data to array u_selectTrackPoint(event)? u_setScrollbar(); u_updateCtxFrame(); // For example, initial display frame is 30, but saved frame is 31. // On review, this looks to be a result of how the p2d file is saved. // This means that we are one short on one end or the other. Sheesh! == FIXED - in manual tracking (and when autoFind is not enabled, the first frame contains pixel data but not calibrated data. This has been changed in u_readMarkerInfo(). 2) Still have the scrolling issue on tracking. SHOW STOPPER BUG for most users. - FIXED 3) Still have the windows update bug. - Possibly fixed when CACHE is cleared. Waiting for feedback from users. 2010-07-09 Laptop hinge broke last week and between shopping for a new production machine, backing up data and some updates to mozilla (that seem to have some issues), everything came to a crashing halt. Still broken: 1) Windows updating - FIXME 2) Possibly Linux updating - FIXME 3) Windows archiving - Fixed! 4) Scrolling in manual tracking when scrollbar is clicked - (only an issue upon going back to tracking?) - FIXME 5) Now that FF has updated, speed on the linux side SUCKS!!!! Changing ipv6 to false and using no proxy may have helped a little But even on a much slower Windows machine, the auto tracking screams compared to my brand new HP laptop running linux. Other stuff to do at this late date 1) Fix installers. It seems that Windows 7 stores profiles in a different place. There are some minor changes to the linux installer too. WINDOWS XP installer seems to be working. It may also work with Windows 7 2) Fix firefogg. It seems to work on Windows or with older versions of FF, but not currently on Linux. This is a show stopper bug. - Mostly FIXED, but need to change for reading videos // Firefogg is not used in its default manner. Rather, its libraries are used instead 3) Fix marker naming so that markers/links with same names don't have collisions. 4) Butterworth filtering is still persistent - maybe fixed 5) Have not investigated why some fits look jagged 6) Need to add animation 7) Need to fix graph legends 8) Others??? - Get rid of gaussian fit centroid unless you do it right. - DONE, no gaussian centroid 9) Clean up directory and release 0.5.0b 2010-07-09 Close to getting downloading updates correct Bill has issues: Naming of markers is still off It seems that filtering of results is persistant somehow (global variable?) 2010-07-06 1) Angles in image analysis - DONE 2) Installer - on Linux and MacOSX, this will still be commandline - Windows installer is complete and partially tested. Extra eye-candy may be necessary for windows users! 3) Why some fits look jagged ????????? 4) Paths options (show every frame vs show every Nth frame) - DONE (fade paths) - DONE 5) Animations in main screen (play button) ??????? 6) Updater - base this on installer for Windows ?????????? 7) Print canvas to PNG ????????????? 8) Convert SVG to CANVAS to PNG ???????????? 9) Icons??????? 10) Butterworth filter - FIXED - mostly it was a dt issue. 11) Intelligent filtering for velocities and accelerations Steps 1) If a directional change persists past some threshhold, filter up to the directional change, and then apply a new filter past this. Otherwise filter across whole array. 2) Calculate derivatives in minor arrays with boundaries at directional changes 12) Integration of curves? Averages of curves? Plot line and show fills. 13) graph legend issues... ????????????? 14) Still some range issues on graphs ???????????? 15) Odd jumping around in manual vs auto tracking on windows. ???????????? 16) Firefogg in setup - DONE 2010-07-01 Added local regression smoothing (seems to be the best algorithm thus far) Added ability to autofind real markers when they are added - option added in setup What's essential next? 1) Off-by-one issue - FIXED 2010-07-02!!!!! 2) Marker/Link appearance via checkbox - DONE 3) Angles in image analysis - In progress 4) Butterworth filter - sometimes it works, and sometimes not. Does it have to do with the # of points (odd/even?) 5) Why some fits look jagged - this has something to do with initialization. It never happens the first time. 6) Add Total Energy Option (KE+PE) 7) Fix cycle analysis for Step test - FIXED 8) Zip/Archive - FIXED 9) Paths/Tracks when markers are checked - DONE 2010-06-29 SHOW markers on autotrack! - DONE Show size of search radius and markers on first screen - fade out after 5 seconds 2010-06-27 gui_editOrDeleteMarker(which,index) { // editing seems to be disabled after tracking! Get rid of name collision problem between checkboxes - This has been dealt with to some extent. However, there still needs to be checking within groups (markers, links, angles) when a new item is added. - DONE (Solved below) In gui_addCheckboxCommands() // problem getting cbM+name as id. Previously cb+name worked Fixed? by changing: u_updateRealMarkers(markers,frame,ctx,redrawButtons,addCheckbox) such that the id of the checkbox added by gui_addColorButton takes M+markerName Todo before release: 1) 2D stuff a) names problem from 6/18 - DONE b) markers, links appearance via checkbox c) off by one error d) lensmap correction - Postpone - with the current camera, this doesn't seem to be an issue 2) Image stuff a) Angle calculations 3) General stuff a) Plugin architecture documentation b) Tutorial updates c) Installer 2010-06-25 Almost finished with the step test calculations. Fix graphics - DONE Fix deltaE calculation 2010-06-21 Interesting and useful additions? 1) Add a calibrator such that a previous calibration can be selected? 2) Allow for recalibration of pixel data 3) Be able to shift static markers easily 4) Archiving data runs into copy and permissions errors in windows 2010-06-18 DO ASAP 1) Get angles to appear when clicked - This was from some checkboxes getting the same name. So long as the user doesn't choose markers/links/angles with the same name, this won't happen. So ~FIXED, sort of. We need to keep users from doing this. 2) Fix fits for multiple graphs - FIXED - 1 problem with global variable, and problem passing xser (which is successively modified on fits) to successive graphs. xser was growing, but yser was not. 3) Allow for multiple types of data to be selected for display - FIXED 4) Prev/Next buttons when more graphs than panes are chosen for display FIXED 5) Get vectors to consistently appear - The manner in which maxPix (the maximum length of the vector) is calculated is incorrect. For the time being, this has been set to 200px. 6) Fix manual tracking post-failed autotrack - It seems that we're off by one frame between the display and the painting of markers and links. 7) Fix legend window in JSvg such that it expands to the correct height. THEN 1) Angle calculation for image analysis 2) Edit of links for image analysis 3) ??? THEN Plan for Cyclic analysis of data 2010-06-17 What's new? The image analysis tab now works to the extent of placing links and measuring distance. What needs to be done on it? 1) A project format for images needs to be decided upon and saves should be done after every link update. - DONE 2) Angles between links need to be calculated - popup or otherwise? 3) Ability to read saved image projects - DONE 4) Currently, the (nonfunctional) angle button only becomes enabled after 3 links are added. This should be changed to two links. 5) Images may need to be scaled to fit. Unlike video, it is possible that the images these days are quite large. With regards to video: 1) Changed code so that on edits, marker types cannot be changed. 2) Still need to ensure that graphs show up when multiple categories of variables are selected. 3) Still need to ensure that graphs show up when multiple graphs are selected and regression curves are fit. 4) Still need to ensure that there is accurate manual tracking after a failed autotrack. 5) Cannot display angles. Are checkboxes not enabled? 6) Vectors are tiny. FIXME! When the above is fixed we need to add: 1) Nancy's cyclic analysis - this should a) Count the number of cycles of any chosen marker (generate new marker list?) b) Calculate energetics per cycle and overall - create output table c) Be able to graph by cycle or by trial marker x,y, vx,vy, ax,ay, px,py, Fx,Fy, KEx,KEy, mgh, other params? 2010-06-16 GOT IT RUNNING ON WINDOWS There were several changes that needed to be made: 1) Load scripts in order to meet dependencies. For some reason loading scripts using