Re: [python-control-discuss] [TuLiP discuss] SF.net SVN: tulip-control:[164] trunk

[Richard M. <mu...@cd...>]

A couple of quick comments on Yuchen's log message:

* At some point we should think about function naming conventions in TuLiP.  It looks like we have gone with a C/C++ mixed case style.  PEP 8 suggests functions of the form write_states_to_file rather than mixedCase.

* For the representation of automatons: we should talk about this at some upcoming meeting.  Obviously being able to use standard libraries to do useful computations is a good way to go.

* Is there a tutorial for using the gephi functions?  I took a quick look but didn't see it in any of the obvious places.  

-richard

On 17 Aug 2011, at 15:16 , yuc...@us... wrote:

> Revision: 164
>          http://tulip-control.svn.sourceforge.net/tulip-control/?rev=164&view=rev
> Author:   yuchennil
> Date:     2011-08-17 22:16:46 +0000 (Wed, 17 Aug 2011)
> 
> Log Message:
> -----------
> Merging the graph-tulip branch back into trunk. All examples should be able to run with or without graph visualization (which requires Gephi to be installed). \n\n -- Read the instructions given in trunk/tulip/gephi to install the Gephi plugin I have written. (These directions should be moved to trunk/docs, but I don't know how to change the documentation.) \n\n -- 'grsim' and 'writeStatesToFile' in 'grsim.py' have been refactored with new arguments, and are now *incompatible* with TuLiP 0.1b. Read their docstrings or look at the examples to see how they are now used. \n\n -- 'automaton.py' has a few new methods: 'writeFile' writes a rudimentary '.aut' file from the current automaton. 'trimDeadStates' removes dead-end states. 'trimUnconnectedStates' removes all states that are inaccessible from a given automaton state. 'createPygraphRepr' creates a python-graph representation of the current automaton, and 'loadPygraphRepr' replaces the current list of states with what is curr
> ently in the python-graph representation. \n\n -- trunk/tools now contains a short script to trim states from a '.aut' file. \n\n Should we consider changing the underlying representation of Automatons to python-graph digraphs? Doing so would eliminate some Automaton indexing issues and provide access to many of the graph manipulation tools in python-graph.