------------------------------------------------------------ revno: 4064 committer: Jerome Duriez <[email protected]> timestamp: Thu 2014-07-10 11:57:20 +0200 message: Improvement of previous commit: there was no extra : but a missing blank line modified: doc/sphinx/user.rst
-- lp:yade https://code.launchpad.net/~yade-pkg/yade/git-trunk Your team Yade developers is subscribed to branch lp:yade. To unsubscribe from this branch go to https://code.launchpad.net/~yade-pkg/yade/git-trunk/+edit-subscription
=== modified file 'doc/sphinx/user.rst' --- doc/sphinx/user.rst 2014-07-10 09:36:35 +0000 +++ doc/sphinx/user.rst 2014-07-10 09:57:20 +0000 @@ -919,7 +919,8 @@ A special engine :yref:`PyRunner` can be used to periodically call python code, specified via the ``command`` parameter. Periodicity can be controlled by specifying computation time (``realPeriod``), virutal time (``virtPeriod``) or iteration number (``iterPeriod``). -For instance, to print kinetic energy (using :yref:`kineticEnergy<yade.utils.kineticEnergy>`) every 5 seconds, this engine will be put to ``O.engines``: +For instance, to print kinetic energy (using :yref:`kineticEnergy<yade.utils.kineticEnergy>`) every 5 seconds, the following engine will be put to ``O.engines``:: + PyRunner(command="print 'kinetic energy',kineticEnergy()",realPeriod=5) For running more complex commands, it is convenient to define an external function and only call it from within the engine. Since the ``command`` is run in the script's namespace, functions defined within scripts can be called. Let us print information on interaction between bodies 0 and 1 periodically::
_______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
