atomium paper

atomium paper

Description

test pysical paper model + fabrics
Two test on this one :
- physical for sheet of paper (\"like\")
- fabrics material with transparency
Full size for light details
Use Blender Logo -> not commercial.

Message boards : Comments and discussion : 570

Author Message
Fischer-Kerli
Project donor
Send message
Joined: 24 Mar 05
Posts: 70
Credit: 78,553
RAC: 0
Message 6523 - Posted: 2 Aug 2007, 12:37:55 UTC

This is computed in two rounds on my system (WinXP SP2, AMD dual core, BOINC 5.10.13): after reaching some 98%, progress goes back - mostly to negative percent values ... wonder how they are calculated - and then climbing up again. Seems to be a cosmetical issue only, all results have validated OK so far if the quorum was there.

Achim
Send message
Joined: 17 May 05
Posts: 182
Credit: 2,520,073
RAC: 951
Message 6525 - Posted: 2 Aug 2007, 18:34:46 UTC

Same for me.
At least some of the WU\'s. E.g. this one

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4478
Credit: 2,094,806
RAC: 0
Message 6527 - Posted: 2 Aug 2007, 19:08:21 UTC

Noted.

Fischer-Kerli
Project donor
Send message
Joined: 24 Mar 05
Posts: 70
Credit: 78,553
RAC: 0
Message 6528 - Posted: 2 Aug 2007, 20:18:28 UTC

Janus - how can a progress of -x% come about? Just curious ...

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4478
Credit: 2,094,806
RAC: 0
Message 6531 - Posted: 2 Aug 2007, 23:33:24 UTC - in response to Message 6528.
Last modified: 2 Aug 2007, 23:36:29 UTC

Janus - how can a progress of -x% come about? Just curious ...

The client uses interpolation between the progress updates it gets from Blender to predict the actual progress. It does this to be able to display progress smoothly in BOINC (it updates the estimate almost every second).

In other words, Blender says:

.
10%
.
40%
.
80%
.
100%

At the first 10% the client knows how long time it took to calculate the 10% and will then be able to estimate how long the next 10% are going to take. So it will do like:

.
10%
28%
40%
60%
80%
90%
100%

But if Blender reports the progress as split into more than one pass (which could very well be the case for an effect such as subsurface scattering) it will go from 0 to 100% and then do another run from 0 to 100%. At the point where Blender switches from 100 to 0 the client sees a negative progress with the time between 100 and 0 as the delta timing value. It will try to figure out how long before you reach -200% and use that to make it\'s next progress estimates...
Now after a while Blender reports the next progress update (which should then be slightly more than 0) and the progress estimates from the client then become sane again (positive).

The current code in the Blender status system is a bit of a mess, meaning that there\'s no consistent way to get the total number of passes (since a pass can include another pass etc). So basically I\'ll have to make the Blender patchset know about all the weird ways you can combine effects, fields, layers, compositing and scene inclusions in order to completely avoid this problem. Not an easy task, but not impossible either.
I\'ve chosen to simply add support for new effects etc. as we go along and people start to use them.

At the moment the Blender patchset supports correct progress reporting for fields and for motionblur but not for sss, layers, postprocessing effects and scene inclusions.

Fischer-Kerli
Project donor
Send message
Joined: 24 Mar 05
Posts: 70
Credit: 78,553
RAC: 0
Message 6532 - Posted: 3 Aug 2007, 0:08:35 UTC

Thank you!

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4478
Credit: 2,094,806
RAC: 0
Message 11082 - Posted: 5 Nov 2011, 11:11:46 UTC
Last modified: 5 Nov 2011, 11:12:20 UTC

Finally it seems that we will have a fix for this. This will hopefully be included in the next version of the normal (non-Sunflower) clients.

funkydude
Send message
Joined: 23 Dec 13
Posts: 275
Credit: 2,478,281
RAC: 0
Message 12216 - Posted: 6 Jan 2014, 1:19:23 UTC - in response to Message 11082.

Finally it seems that we will have a fix for this. This will hopefully be included in the next version of the normal (non-Sunflower) clients.


2 years later... Noticing this happening with units from project 1896. It just jumped to 98.021% after ~12 seconds. Should I leave it running?

Profile David
Send message
Joined: 1 Jan 14
Posts: 8
Credit: 42,160
RAC: 0
Message 12217 - Posted: 6 Jan 2014, 8:03:39 UTC - in response to Message 12216.

I have same problem got WU 1981190 stop at 98.021%, working for 11h already.... remind time is 12 min 44 for now about 4h ...

Profile David
Send message
Joined: 1 Jan 14
Posts: 8
Credit: 42,160
RAC: 0
Message 12218 - Posted: 6 Jan 2014, 8:48:41 UTC - in response to Message 12217.

I closed BOINC client, and I get an error from Blender that was not able to close...

My task restarted from 0% ...

Profile David
Send message
Joined: 1 Jan 14
Posts: 8
Credit: 42,160
RAC: 0
Message 12219 - Posted: 6 Jan 2014, 10:24:01 UTC - in response to Message 12218.
Last modified: 6 Jan 2014, 10:24:11 UTC

My task stopped again 98.021%

Blender_4.79_windows_x86_64.exe has stopped working....

OK I stop request task from BURP at the moment.

funkydude
Send message
Joined: 23 Dec 13
Posts: 275
Credit: 2,478,281
RAC: 0
Message 12220 - Posted: 6 Jan 2014, 14:02:38 UTC - in response to Message 12219.

If I exit BOINC nothing crashes, BUT, when I load it up it starts from 0% for me also. :( I had to manually abort several work units because it wasn't going to make the seriously strict deadline they've been assigned. (What's that all about anyway? You can't give ~16hrs for a unit that's taking 10+hrs to render.)

I decided to just leave one running anyway, and it actually completed after about 10hrs 40min. The entire time the percentage, remaining time, etc, was completely broken.

I believe the work unit was this: http://burp.renderfarming.net/workunit.php?wuid=1980482 though this seems to be from a different project so I guess this percentage issue is affecting multiple projects at the moment.

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4478
Credit: 2,094,806
RAC: 0
Message 12221 - Posted: 6 Jan 2014, 16:29:46 UTC

You are probably talking about a cycles-based session. Those are highly experimental at the moment for the exact reasons that you describe.

Profile David
Send message
Joined: 1 Jan 14
Posts: 8
Credit: 42,160
RAC: 0
Message 12222 - Posted: 6 Jan 2014, 16:41:03 UTC - in response to Message 12221.

ok but on my 2nd host I have 4 tasks at 98.021%
what I do, leave them running or stop them ?

(https://dl.dropboxusercontent.com/u/50661130/BURP.jpg)

one of my tasks already late

funkydude
Send message
Joined: 23 Dec 13
Posts: 275
Credit: 2,478,281
RAC: 0
Message 12223 - Posted: 6 Jan 2014, 17:10:49 UTC - in response to Message 12222.
Last modified: 6 Jan 2014, 17:11:15 UTC

You are probably talking about a cycles-based session. Those are highly experimental at the moment for the exact reasons that you describe.


Actually I was talking about the percentage issue which is what this thread was about. It was meant to be fixed 2 years ago, no?

It seems the latest workunits I've been getting have a much more sane deadline of over a day. I guess you fixed that internally.

ok but on my 2nd host I have 4 tasks at 98.021%
what I do, leave them running or stop them ?


Let them run, the percentage display is broken, but it should finished in 10/11 hrs.

one of my tasks already late


Abandon the late task. The newer tasks seems to have better deadlines.


Post to thread

Message boards : Comments and discussion : 570