While TK-MIP rigidly adheres to most Windows’ Key and Menu Option standards, as prescribed by Microsoft, a single exception is in how TK-MIP handles the USER activity history/check-off log" by merely reporting user progress (without the user ever directly or explicitly clicking anything on this list itself) since TK-MIP reports and updates this list automatically as the USER accomplishes the various intermediate processing goals. A passive “User activity history/check-off log” (handled here as a detailed menu drop down list) maintains continuity of operations by passively summarizing at-a-glance what operations have already been completed (by no longer being grayed) and what remains to be done (as signified by still being grayed) before the particular task is fully complete. In this way, the USER will not loose their place if frequently interrupted for long periods of time (examples being a need to take a telephone call, attend a meeting, go to: a technical conference, go to a parent teacher's meeting, a bathroom break, going home for the weekend, taking a holiday, a vacation, etc.). It is crucial to aid the USER in this way so that long processing runs can be easily handled despite any hiatus in the USER's attention so that the USER never looses track of what steps have already been completed and what remains to be done. TK-MIP prevents processing collisions or unintended redundant retracing of previously activated steps by visually notifying the USER via the feedback of a red light being present in the center of the screen’s status bar at the bottom of the screen (as a situation when both mouse and keyboard inputs are locked out) until it turns green again as the signal that it is again receptive to further USER requests (using keyboard or mouse actions). We have other convenient USER cross-checks throughout TK-MIP.
In the above MAIN MENU Screen, please notice that for items #9, #10, and #11, that the particular panel in which these activities appear is enclosed or encircled by a thin red line about these potential USER activities. The label at the top explains that these three activities are "Accessible ONLY when system is Linear Time-Invariant and Synchronous (measurements are periodic)". These three activities are "frozen out" unless USER has already performed ALL the correct precursor activities that make these three activities available to the USER. By design, TeK Associates has intentionally made the option of further pursuing any of these 3 activities inaccessible unless the USER has done the proper things (in preparation) to get there. ONLY when ALL required precursor steps have been taken and completed, will it be unlocked for the USER to further pursue at their volition. In this way, TeK Associates "prevents the USERs from shooting themselves in the foot" so to speak.
Within the MAIN MENU of our TK-MIP GUI, colorization of system blocks appearing in the left margin (it appears on the right on some screens) serves as a gentle visual reminder of which models have already been defined by the USER, corresponding to: System (S), Kalman Filter (KF) or approximate linear ESTIMATOR still reminiscent of the structure of a KF [such as an Extended Kalman Filter (EKF)], and/or representative Control Gain (M) (if control is indeed present in the application). If control is absent, the corresponding block has no color within the small block diagram in the left (or right) margin. Similarly, each block lacks color until it is completely defined enough to proceed in further processing. Such subtle reminders appear on many of our TK-MIP screens throughout to aid the USER.
In the above, TVP (Time-Varying Parameters) is a linear system with either time-varying “System matrix”, “Obsevation matrix”, “System Noise Gain matrix”, or “System Control Gain matrix”. To be TVP, one or more of the previously mentioned matrices is time-varying in a manner that is known and has been specified beforehand.
For situations involving time stamps used in data logging of actual data, let the time step delta: Δ = t(j+1) - t(j).
Please do not confuse the above froggy character in the top left hand corner with a different proprietary Kermit here: https://youtu.be/wljPHtQ3dXM
Microsoft Word™ is to WordPerfect™ as TK-MIP™ is to ... everything else that claims to perform comparably!
USER can provide a specific name for each project in order to easily distinguish it from other likely projects and furthermore to unambiguously associate with it both the intermediate and final output files for the particular project at hand (with history of activity log stored in a concise “header” to each intermediate and major output file that automatically reloads and refreshes TK-MIP whenever the USER resumes processing right at the same point where the USER last left off (even after project has been closed and TK-MIP has been exited or the computer has been completely shut down or powered off). Otherwise, if USER has a sufficiently long block of time without any interruptions interfering before completion of the tasks at hand, USER can just perform the processing functions in one sitting without such project identifiers and TK-MIP will remember all pertinent activity history without a specific project name being assigned yet as long as TK-MIP is not exited and there is only one USER performing only one project at a time. Even in seeking to follow the latter case (described last as not designating a particular project name) and an unanticipated interruption occurs, If processing outputs and models already specified are SAVED and given a name after the fact, then the existing activity/history log residing within TK-MIP up to this point will be correctly associated with and assigned to the project and automatically appended by TK-MIP as a header (or preamble to the file, as occurs with JTIDS and GPS messages) for later USER resumption of tasks in pursuit of the final processing goals. The header (or preamble) mentioned above (as being at the start of a file) summarizes the activity log, which preserves the story of conditions utilized in computing results by tripping the appropriate "flags" and storing this information for posterity. This information is conveyed with the particular project as a short reminder of the particulars utilized in obtaining the current results of interest.
By invoking a particular project and then “Save Project as...” with a name change, all files associated with the original project name will inherit the same new name change except SAVE_ALL files which will retain their previous name. Of course once saved, SAVE_ALL can then be invoked with the new replacement project name and a SAVE_ALL will then be associated with the new project name in case USER later seeks to RESURECT_ALL with this new project name. USER may want to just change a few parameter values in the models and then recalculate results in this easy way to keep things properly sorted out. See the obvious parallel with how easily USER can handle and manipulate subsequent document versions within Microsoft Word®!
Our TK-MIP™ software is yet another masterpiece of engineering implementation by properly anticipating our users’ needs.
TeK Associates' Motto: "We work hard to make your job easier!"