[Bf-committers] Patch #6161 updated
dfelinto at gmail.com
Wed Sep 17 22:14:34 CEST 2008
It looks very usefull.
I'm currently writing a Python script to be used as a ScriptLink that
report by email the current status of an animation, particles baking,
fluid baking, ...
The goal is to let the computer thinking as you go work in other
computers or go to the beach and let the iphone tells you when it is
time to work again :)
Therefore I have some thoughts related to this:
1) I didn't look to the patch, but I saw the Patch Tracker comments
. Do you think it would be possible to enable a progression output
to Particles Baking as well ?
2) In your code there is a Python API to access the output log from Blender?
3) I'm having troubles in using ScriptLink to report a progression.
Right now I'm using FrameChanged since it works the same way with
almost  all of the hard-stuff.
Is it possible/hard to enable a ScriptLink that is raised after the
frame change+Redraw, or after the render is finished? Something like:
1 - https://projects.blender.org/tracker/index.php?func=detail&aid=6161&group_id=9&atid=127
2 - https://projects.blender.org/tracker/index.php?func=detail&aid=17644&group_id=9&atid=125
2008/9/17 Early Ehlinger <earlye at gmail.com>:
> I finally had some time to re-synch the ResPower blender tracing patch with
> the latest SVN. This is the patch that ResPower uses to provide progress
> information in its render logs, since viewing render nodes' desktops is
> expensive compared to sending a few lines of text to a customer's web
> The way it works is that it exposes a new python API whereby a script can
> request that Blender send trace messages to a python function. On the
> ResPower farm, the python function simply prints the output to the console,
> and the farm management software reads the console and saves the output to
> the log.
> The instrumentation here is mainly rendering-centric, but the patch can be
> extended to support other portions of the code as well. This would be
> useful, for example, to have end-users generate a log file to track down
> difficult-to-reproduce bugs. (e.g., "run this script, email me the log file
> when the bug occurs!" )
> I would really like to get this patch into the trunk so that we can start to
> provide support for the official releases of Blender more quickly (download
> and deploy, as opposed to download, patch, build, and deploy), and also so
> we can add support for the svn version of Blender for our more advanced
> users. We can't do this now as patching the files every day would be a
> major hassle.
> The default behavior should be indisginquishable from not having the patch,
> i.e., you should only notice a difference if you turn on the functionality
> from python. See /source/tools/test-blender-trace.py for an example of
> using it.
> -- Early Ehlinger, President, ResPower, Inc.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers