Candidates for Future Releases

Back to Main Page

Future Candidate Features

    L2 Engine

  • Optimizing for min-progress doesn't handle commands in clauses
  • tentative observations -- handle variant monitor bining
  • Diagnosis Checker (reduce number of spurious diagnoses under min progress)
  • Progress handles multiple commands
  • Multiple initial states
  • Disjunctive assignment

    L2 Engine X-37 only

  • No use of inline keyword in flight code
  • No pointer arithmetic (iterators) in flight code
  • No operator overloading in flight code
  • No strings in flight code
  • Array bounds checking in flight code

    Stanley

  • None.

    Skunkworks

  • None.

Older Release Descriptions Follow

L2Skunk 2.7.2 -- Release 05/22/02

    L2 Engine

  • Integrated recovery and respond to bug reports

    Stanley

  • Respond to bug reports

    Skunkworks

  • Respond to bug reports

L2Skunk 2.7 -- Release 11/19/01

    L2 Engine

  • SUA: Royalty free use for non-commercial applications
  • Fixed a resource leak
  • Fixed a bug that caused Livingstone to crash
  • Added more documentation

    Stanley

  • SUA: Royalty free use for non-commercial applications
  • Port to Windows
  • Respond to bug reports

    Skunkworks

  • SUA: Royalty free use for non-commercial applications
  • Add exogenous/inferred tags to History Table values
  • Respond to bug reports

L2Skunk 2.6 -- Release 10/04/01

    L2 Engine

  • Debugger mapping of optimized variables
  • Less pointer arithmetic
  • No recursion in flight code

    Notes

  • No anonymous unions - done in release 2.5
  • No C++ exception handling - done in release 2.5
  • No X-37 branch at this time

    Stanley

  • Respond to bug reports

    Skunkworks

  • Respond to bug reports

L2Skunk 2.5 -- Release 7/27/01

    L2 Engine

  • search termination API
  • no dynamic memory allocation
  • no io in flight code
  • documentation from July code review

    Stanley

  • Respond to bug reports

    Skunkworks

  • Respond to bug reports

L2Skunk 2.4 -- Release 6/13/01

    L2 Engine

  • output API (current modes, trajectories/candidates)
  • checkpointing
  • non-integerated recovery - not integerated with diagnosis
  • Memory handling for arrays

    Stanley

  • Respond to bug reports

    Skunkworks

  • Respond to bug reports

L2Skunk 2.3 -- Release 5/14/01

Overview

In this release, we will continue to attack known performance bottlenecks and incrementally improve L2.

L2 Engine

  • Binary loader (Benoit)
  • General API cleanup (Jim, Benoit)
  • Memory handling for link lists (Benoit)
  • Remove domain class (Benoit)

Stanley

  • Respond to bug reports (Will)

Skunkworks

  • Respond to bug reports (Will)

L2Skunk 2.2 -- Release 4/05/01

Overview

This release will correct the problem of "unknown" mode states generated by L2 progressing and because of history cutoff, truncating an inconsistent state caused by assigns being applied without a find-candidates being done first.

L2 Engine

  • Assigns are not entered into the truth maintenance system until find-candidates is to be executed (Benoit)

Stanley

  • Respond to bug reports (Will)

Skunkworks

  • Respond to bug reports (Will)

L2Skunk 2.1 -- Release 3/26/01

Overview

In this release, we will continue to attack known performance bottlenecks and incrementally improve L2, Stanley, and Skunkworks.

L2 Engine

  • Memory usage report - Benoit
  • Optimizer to get rid of equivalent variables (Jim, Will)
  • Memory handling, except for link lists and arrays (Benoit)
  • RTI: utilizing new variable IDS; modifying 'observe' to allow assigning unknown; and updating api_gen, api_scr, the RTI library, and the sample code to work with the 2.0 engine (Shirley)
  • Discrepant observations (Jim)
  • l2test and l2run will have the ability to specify whether calls to progress are "min" or "full" (Benoit)
  • Debugging info for "state=s0" variables (Benoit)
  • Respond to bug reports (Jim & Benoit)

Stanley

  • Handle fc preference, with options being "prune&search", "find-fresh", and "extend" (Will)
  • Respond to bug reports (Will)

Skunkworks

  • Fix JMPL to XMPL compiler to correctly generate warnings messages for unreferenced variables (Andrew)
  • Add fc preference, with options being "prune&search", "find-fresh", and "extend" -- the default will be "prune&search", the current behavior (Will)
  • Model Browser, which displays model JMPL code, callable from SKunkworks command line (Will)
  • Documentation of History Table and Justification tools (Mark S)
  • Respond to bug reports (Will)

L2Skunk 2.0 -- Beta on 2/26/01, Release 3/05/01

Overview

This release adds the major L2 capabilities of "minimal progress" and model "optimization". It also makes significant progress in resolving L2 performance bottlenecks, incrementally improves Stanley, and fixes many bugs in the Skunkworks History Table.

L2 Engine

  • Model optimizer - Jim
  • Optimizer to allow minimal progress (Andrew, Jim)
  • Minimal progress - Jim
  • Progress documentation - Jim
  • New reader architecture - Benoit
  • Listeners - Benoit
  • Regression fix - Benoit and Jim
  • Continuing memory fixes - Scott C

Stanley

  • Bug fixes - Will

Skunkworks

  • Bug fixes - Steve

L2Skunk 1.5 -- Beta on 1/16/01, Release 1/22/01

Overview

In this release, we will continue to attack known performance bottlenecks and incrementally improve Stanley and Skunkworks.

L2 Engine

  • Optimization of progress() - Jim
  • Cleanup of Conflict_db API - Jim
  • Ability to assign mode variables for testing purposes - Jim
  • Multiple simultaneous assignments (ie "assign v1=val1 v2=val2") in debugger - Jim
  • Add ability to create clauses for disjunctive observations (ie "assign v1=val1 or val2") - Jim
  • Better observability of theory size, memory usage, CPU usage - Jim and Benoit
  • Reclaiming truncated history and fix truncated conflicts - Benoit
  • Mapping from clause that's read in to component - Benoit
  • Static memory allocation - Benoit and Scott Christa
  • Fix memory leaks in L2 engine - Scott Christa
  • Continue work in VxWorks support - Scott Christa, Sandra
  • Convert max candidate cost from compile-time to run-time parameter - Shirley
  • RTI API for multiple simultaneous assignments - Shirley, Bill
  • Continue work on RTI - Shirley, Bill

Stanley

  • Separation of component display state from model - Will
  • Multiple assignments (ie assign v1=val1 v2=val2) in scripts
  • starting and initializing Stanley with L2 model state - Andrew, Will

Skunkworks

  • Begin work on equivalent variable collapser - Andrew
  • Deallocation of L2 engine upon engine exit - Steve
  • Documentation of Candidate Manager, History Table and Justification tools - Steve

L2Skunk 1.4 -- Beta on 12/04/00, Release 12/06/00

Overview

In this release, the focus will be to bring L2's memory and cpu performance close to that we expect to see in flight, by attacking known performance bottlenecks. We will also move toward a Skunkworks control panel that will support multiple Stanley windows

L2 Engine

  • better observability of theory size, memory usage, CPU usage - Jim
  • general optimization of memory and cpu usage - Jim
  • clean up of transition system, incl. reclaiming truncated history - Jim
  • Clean up of progress/fc and their variations (eg PRs and docs) Jim
  • Ability to write out current state of L2 - Jim
  • Mapping from clause that's read in to component - Benoit
  • Static memory allocation - Scott Christa, Benoit
  • Fix memory leaks in L2 engine - Scott Christa
  • Continue work in VxWorks support (Sandra, Scott Christa)
  • Continue work on RTI - Shirley, Bill

Stanley

  • Shutdown message between Stanley/Skunworks to enable Stanley to only kill its skunkworks - Will, Steve
  • Work toward multiple panels or bringing up a panel with a particular component in it - Will
  • assign L2 parameters to be set by a) user preferences, b) workspace preferences, or c) L2 compiler preferences - Will + Mark

Skunkworks

  • Deallocation of L2 engine upon engine exit - Steve
  • Ground Station GUI Frame - Andrew, Steve
  • starting and initializing Stanley with L2 model state - Will
  • Explanation tool & Command Line command explain -- text and lattice
    This should be working, but needs to be documented so users can test it out. See below.
  • Documentation of Candidate Manager, History Table and Justification tools - Steve

L2Skunk 1.3 Candidate Features (10/16/00)

    L2

  • Binary Load/Save (Benoit)

    Skunkworks

  • Event distribution architecture (Andrew, Steve)
  • Complete Timeline Viewer tool (Steve, Mark Shirley)
Enable history = 1 step (Jim)

Skunkworks

  • Improved Stanley Scenario Manager -- single stepping, editing (Will)
  • Compiler support for explanation (Andrew)

    L2Skunk 1.2.3 Candidate Features (10/02/00)

    • L2

    • RT API (Shirley)

    L2Skunk 1.2.2 Candidate Features (09/21/00)

      L2

    • Initial Constraints in .ini (Jim)

    L2Skunk 1.2.1 Candidate Features (09/01/00)

    • All Livingstone debugger commands added to Skunkworks by implementing "pass-through" command processing in Skunkworks (Jim, Will)
    • Stanley Step and Run buttons seem to more appropriately reside in the Scenario Window. For scenarios being generated on the fly, the Scenario Window would help show what's there as the user is generating it. (Will)

    L2Skunk 1.2 Candidate Features (08/21/00)

    • The history truncation will be fully functional for both cover and cbfs search engines (Jim)
    • Candidate Manager shows multiple failures (Steve)
    • Attributes whose constraint sets are all false, are returned as "unknown" (Steve, Will)

    L2Skunk 1.1 Candidate Features (07/27/00)

    • Cut off old variables representing old time steps (Jim)
    • Put skunkworks and mba under a common directory where we can store files such as this one (All)
    • Allow user to specify which candidate they want installed (eg install 0) then reinstall it after each diagnosis. [Note: This assumes the numbering scheme is stable. It is in the cover search. Not sure about cbfs] (Jim)

    L2Skunk 1.0.2 Candidate Features (06/29/00)

    • Exceptions in L2 are passed via Skunkworks to Stanley where the user is notified and the command processing is blocked, rather than killing L2. (Steve, Will)

    Top Back to Main Page

    		•