Difference between revisions of "Latest on the software"

From Bcontrol
(RTLSM - Matlab)
Line 5: Line 5:
 
== RTLSM - Matlab ==
 
== RTLSM - Matlab ==
 
* '''<tt>ForceState.m</tt>'''  
 
* '''<tt>ForceState.m</tt>'''  
When '''<tt>ForceState.m</tt>'''  tries to force the FSM to a state that doesn't exist, the FSM returns an error.  (This makes sense).  This error was handled by RTLSM as an error and it would crash dispatcher.  I changed the function to throw a warning instead of an error.  So the user will still see the error returned by the  FSM server, but the code will continue to run on the matlab end.  [Is this desirable or should this be changed in dispatcher?]  
+
:When '''<tt>ForceState.m</tt>'''  tries to force the FSM to a state that doesn't exist, the FSM returns an error.  (This makes sense).  This error was handled by RTLSM as an error and it would crash dispatcher.  I changed the function to throw a warning instead of an error.  So the user will still see the error returned by the  FSM server, but the code will continue to run on the matlab end.  [Is this desirable or should this be changed in dispatcher?]
+
 
 
== Solo ==
 
== Solo ==
  

Revision as of 04:35, 15 June 2007

RTLSM - Matlab

  • GetTimeEventsAndState.m
Calin finished upgrading the way matlab gets updates from the RP box. Now, instead of 4 functions, we can just call 1 . This reduced the update time by 75%. Note, dispatcher and RPBox need to be updated to use the new function. And the RT machines need to grab updated c++ code and then recompile the FSM server for this to work.

RTLSM - Matlab

  • ForceState.m
When ForceState.m tries to force the FSM to a state that doesn't exist, the FSM returns an error. (This makes sense). This error was handled by RTLSM as an error and it would crash dispatcher. I changed the function to throw a warning instead of an error. So the user will still see the error returned by the FSM server, but the code will continue to run on the matlab end. [Is this desirable or should this be changed in dispatcher?]

Solo

  • sp_who.m
Find who owns and has access to SoloParamHandles.
Given a SoloParamHandle, sp_who prints to command line who owns it and who has access to it.
Can also be given search parameters: e.g., sp_who('name', 'gee') will report on all SoloParamHandles whose name contains the string 'gee'. For allowable search paramteres, do "help get_sphandle".
11:15, 1 June 2007 (EDT)

Dispatcher

  • PokesplotDemo protocol
A very simple dispatcher protocol, basically just demonstrates the pokesplot plugin. Protocols/@PokesplotDemo/
CarlosBrody 13:59, 1 June 2007 (EDT)

Plugins

  • antibias plugin
Added complete documentation to the antibias plugin. For help, "help antibias/AntibiasSection." This plugin does not take any information in through SoloParamHandles, it is all parameters in on the function calls made to it, and returns out.
CarlosBrody 14:14, 2 June 2007 (EDT)

SessionModel

RTLSM Matlab-side code; StateMachineAssembler and disassembler

RTLSM Linux-side code