[Bf-committers] Patch #6161 updated

[Dalai Felinto]

Hi Early.

I finish the notification system I was doing.
http://blenderecia.orgfree.com/index.php/blender/blender-notifier/

My solution, however, is much more simple/low level than yours. The
user just need Blender and Python. No console batching.
But let me give some feedback from my perspective to your patch:

> Getting an email with progress info would be very easy to do with this patch
> - simply have the callback function send an email (or not) to let you know
> how things are progressing.  On the farm, we do something very similar - we
> store the progress info into a file that is later handed off to the end
> user.

I'm not sure of that. For that the callback function itself should be
a ScriptLink type (e.g. instead of FrameChanged).
What currently (AFAIK) is not possible.


> "As of 4:00 pm, Frame 5 has processed 5,432,124 of 6,000,000 particles.  In
> the last 1 hr, 3 frames and 23,432,124 particles have been processed.  Total
> frames left to complete process after frame 5: 64"

I like this idea (very specific use though, agree with ton).

> I'm not familiar with ScriptLink at all, but if I understand your goal
> correctly, it should be very easy to accomplish with this patch - simply
> watch for the right sMessage in your rpBlenderCallbackSvn, and send an email
> to your iPhone when that message arrives.


With this I think I can do something. I could run my script as a
ScriptLink. Then every frame that I want to trace, I check the
sMessage in my Callback and send the message by email. Every frame I
don't wanna trace I cleanup the messages. (or something like that).

It looks a bit too complex (and slow) for me. I would rather a "print
debug" options in BlenderMenu, and an easy way to access then by
Python referring to their frame or time range (e.g. Blender.getLog(10)
or Blender.getLog(125,250)). I'm not sure how would be the better way
to implement that.


Well, just my 2 cents :)
Dalai


>> Dalai Felinto
>> http://blenderecia.orgfree.com
>>
>> 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
>> > browser.
>> >
>> > 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
>> > http://lists.blender.org/mailman/listinfo/bf-committers
>> >
>> >
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>
>