Latest on the software
Please sign changes to this page, so people know who to contact if they have a question.
To sign your edit, put in four tildes, like this: ~~~~
- 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".
- CarlosBrody 11:15, 1 June 2007 (EDT)
- PokesplotDemo protocol
- A very simple dispatcher protocol, basically just demonstrates the pokesplot plugin. Protocols/@PokesplotDemo/
- CarlosBrody 13:59, 1 June 2007 (EDT)
- 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)
RTLSM Linux-side code and @RTLSM Matlab object methods
- This function is not for the user-level, but is intended internally for Dispatcher (and, if desired, the old RPBox.m) to run their update calls faster.
- @RTLSM/GetTimeEventsAndState.m returns, from a single call to the Linux RTLSM kernel, the following four things: (1) current Time, according to the RTLSM; (2) current State the RTLSM is in; (3) current RTLSM Event counter; (4) matrix of latest Events. This combo call replaces the four separate calls that used to be made, one for each of those things. Since each call to the RTLSM kernel takes about 40 ms, useing the old 4 calls took 160 ms; the combo reduces that by 120 ms. The returns are in RTLSM numeric format, not in the disassembled format that Dispatcher reports to users.
- CarlosBrody 13:11, 15 June 2007 (EDT)
- 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?]