POV-Ray : Newsgroups : povray.binaries.images : TBTFH 2018 status Server Time: 14 Dec 2018 11:26:29 GMT
  TBTFH 2018 status (Message 1 to 10 of 25)  
Goto Latest 10 Messages Next 10 Messages >>>
From: BGimeno
Subject: TBTFH 2018 status
Date: 22 Aug 2018 15:28:25
Message: <5b7d8119@news.povray.org>
I followed the advice of subdividing the mesh in small triangles and 
launched this test in high quality to show how it is. Hope you like. I 
will show images at the rate of one every 7-10 days in this same thread 
as I update the code.

Yes, I will share the documented source with examples as soon as it is 
legible.
Greetings.
BGimeno


Post a reply to this message


Attachments:
Download 'tbtsfh2.png' (726 KB)

Preview of image 'tbtsfh2.png'
tbtsfh2.png


 

From: Bald Eagle
Subject: Re: TBTFH 2018 status
Date: 22 Aug 2018 22:25:00
Message: <web.5b7de1a5abd6e8db458c7afe0@news.povray.org>
BGimeno <bru### [at] gmailcom> wrote:
> I followed the advice of subdividing the mesh in small triangles and
> launched this test in high quality to show how it is. Hope you like.

Yes, this is excellent   :)
I like the way the plane turned out, and the focal blur is a good choice.

TBTFH is nicely sculpted - though perhaps the white on white with a white "sky"
and whitish plane with white reflections is a bit washed out.
Sprinkle some Irish freckles in there.  :D

> I
> will show images at the rate of one every 7-10 days in this same thread
> as I update the code.

Thanks!   It's always nice to have a few new things to look forward to.

> Yes, I will share the documented source with examples as soon as it is
> legible.

I wholly understand.   I have large swaths of code that are Jackson Pollack in
nature, and others where I look open the file, look at the code, wonder what it
all is, and what it's for, ... and then realize that I'm the one who wrote it.

:D


Post a reply to this message

From: Stephen
Subject: Re: TBTFH 2018 status
Date: 23 Aug 2018 05:51:10
Message: <5b7e4b4e$1@news.povray.org>
On 22/08/2018 23:20, Bald Eagle wrote:
>> Yes, I will share the documented source with examples as soon as it is
>> legible.
 >
> I wholly understand.   I have large swaths of code that are Jackson Pollack in
> nature, 

:D
Love the thought. :)

> and others where I look open the file, look at the code, wonder what it
> all is, and what it's for, ... and then realize that I'm the one who wrote it.

I am looking at an animation I made 10 years ago, wondering what I was 
thinking of with the mechanics.


-- 

Regards
     Stephen


Post a reply to this message

From: BGimeno
Subject: Re: TBTFH 2018 status
Date: 7 Sep 2018 07:36:47
Message: <5b922a8f@news.povray.org>
The code is in povray.text.scene-files. Take this as a work in progress. 
I think some parameters need readjustments.

Intel® Core⢠i7-3770 CPU @ 3.40GHz à 8
RAM 7,7 GiB
OS Ubuntu 18.04.1 LTS

Render Time:
   Photon Time:      No photons
   Radiosity Time:   0 hours 24 minutes  1 seconds (1441.334 seconds)
               using 8 thread(s) with 11340.966 CPU-seconds total
   Trace Time:       6 hours  1 minutes 38 seconds (21698.912 seconds)
               using 8 thread(s) with 172774.191 CPU-seconds total

Regards
BGimeno


Post a reply to this message


Attachments:
Download 'test6.png' (1426 KB)

Preview of image 'test6.png'
test6.png


 

From: Bald Eagle
Subject: Re: TBTFH 2018 status
Date: 7 Sep 2018 19:10:04
Message: <web.5b92cc92abd6e8dbc437ac910@news.povray.org>
BGimeno <bru### [at] gmailcom> wrote:
> The code is in povray.text.scene-files. Take this as a work in progress.
> I think some parameters need readjustments.
>
> Intel® Core⢠i7-3770 CPU @ 3.40GHz à 8
> RAM 7,7 GiB
> OS Ubuntu 18.04.1 LTS
>
> Render Time:
>    Photon Time:      No photons
>    Radiosity Time:   0 hours 24 minutes  1 seconds (1441.334 seconds)
>                using 8 thread(s) with 11340.966 CPU-seconds total
>    Trace Time:       6 hours  1 minutes 38 seconds (21698.912 seconds)
>                using 8 thread(s) with 172774.191 CPU-seconds total
>
> Regards
> BGimeno

This looks good - but I'm confused.
I haven't had a chance to look through your code and see what you're doing.

Is that "stripe" supposed to be missing?
(I like the effect anyway  :) )
This took about 13 min to parse on my tower at work, and not very long to render
for me - what are those huge times you're posting?

The torus that I'm working on doesn't take nearly that much time to parse on my
laptop.

I'll send you an email and maybe we can compare notes.


Post a reply to this message

From: jr
Subject: Re: TBTFH 2018 status
Date: 7 Sep 2018 20:15:06
Message: <web.5b92dbaeabd6e8db1500b2fd0@news.povray.org>
hi,

"Bald Eagle" <cre### [at] netscapenet> wrote:
> BGimeno <bru### [at] gmailcom> wrote:
> > The code is in povray.text.scene-files. Take this as a work in progress.

it is a beautiful object.

> > I think some parameters need readjustments.
> >
> > Intel® Core⢠i7-3770 CPU @ 3.40GHz à 8
> > RAM 7,7 GiB
> > OS Ubuntu 18.04.1 LTS
> >
> > Render Time:
> >    Photon Time:      No photons
> >    Radiosity Time:   0 hours 24 minutes  1 seconds (1441.334 seconds)
> >                using 8 thread(s) with 11340.966 CPU-seconds total
> >    Trace Time:       6 hours  1 minutes 38 seconds (21698.912 seconds)
> >                using 8 thread(s) with 172774.191 CPU-seconds total
> >
> > Regards
> > BGimeno
>
> This looks good - but I'm confused.
> ...
> This took about 13 min to parse on my tower at work, and not very long to render
> for me - what are those huge times you're posting?

your reply to BGimeno encouraged me to try on my machine (lowly I3), and now I'm
confused.  run with:

  $ povray +w1024 +h768 +a0.05 +am2 +ag1 -j +q11 +itorus-test6.pov

parsing is well under a minute, and (4 threads) radiosity + trace total up to
under 20 minutes.

BGimeno: looks like your system would benefit from some tlc + admin.  ;-)


regards, jr.


Post a reply to this message

From: jr
Subject: Re: TBTFH 2018 status
Date: 7 Sep 2018 20:30:05
Message: <web.5b92df5fabd6e8db1500b2fd0@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:
> parsing is well under a minute, and (4 threads) radiosity + trace total up to
> under 20 minutes.

just over 20 mins.  </sighs>

parse: 52.5 s.
bounding: .05 s.
radiosity: 130.6 s.
trace: 1157.2 s.


regards, jr.


Post a reply to this message

From: Bald Eagle
Subject: Re: TBTFH 2018 status
Date: 7 Sep 2018 22:25:01
Message: <web.5b92fab5abd6e8db458c7afe0@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:

> > parsing is well under a minute, and (4 threads) radiosity ....

So, I'm triply confused.
a)  There's a quality 11?    (Throws horns, bangs head)

b) I don't see a radiosity block in this scene...

c) I copied your settings and pasted it into QTPOV-Ray like so:

+w1024 +h768 +a0.05 +am2 +ag1 -j +q11 +ITBTFH_2018-09-07.pov

Parser Time
  Parse Time:       0 hours  0 minutes 49 seconds (49.470 seconds)
              using 1 thread(s) with 0.-01 CPU-seconds total
  Bounding Time:    0 hours  0 minutes  0 seconds (0.063 seconds)
              using 1 thread(s) with 0.-01 CPU-seconds total
Render Time:
  Photon Time:      No photons
  Radiosity Time:   No radiosity
  Trace Time:       0 hours  0 minutes 33 seconds (33.499 seconds)
              using 4 thread(s) with 0.-04 CPU-seconds total

 It took 1:24.

so, actually, quadruply confused - since it took over 13 min to do at work on
what I believe is an i5.

and this is my laptop at home:

System:    Host: oem-Inspiron-N5110 Kernel: 4.10.0-38-generic x86_64 (64 bit
gcc: 5.4.0)
           Desktop: Xfce 4.12.3 (Gtk 2.24.28) Distro: Linux Mint 18.3 Sylvia
Machine:   System: Dell (portable) product: Inspiron N5110
           Mobo: Dell model: 034W60 v: A07 Bios: Dell v: A07 date: 07/18/2011
CPU:       Dual core Intel Core i5-2410M (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9179
           clock speeds: max: 2900 MHz 1: 983 MHz 2: 818 MHz 3: 827 MHz
           4: 833 MHz


Post a reply to this message

From: jr
Subject: Re: TBTFH 2018 status
Date: 7 Sep 2018 22:45:01
Message: <web.5b92feffabd6e8db1500b2fd0@news.povray.org>
hi,

"Bald Eagle" <cre### [at] netscapenet> wrote:
> "jr" <cre### [at] gmailcom> wrote:
>
> > > parsing is well under a minute, and (4 threads) radiosity ....
>
> So, I'm triply confused.
> a)  There's a quality 11?    (Throws horns, bangs head)

:-)  section (docs v3.8, section 3.2.8.3)


> b) I don't see a radiosity block in this scene...

immediately below the '#include' lines, the (second) global_settings block.

> c) I copied your settings and pasted it into QTPOV-Ray like so:
>
> +w1024 +h768 +a0.05 +am2 +ag1 -j +q11 +ITBTFH_2018-09-07.pov
>
> Parser Time
>   Parse Time:       0 hours  0 minutes 49 seconds (49.470 seconds)
>               using 1 thread(s) with 0.-01 CPU-seconds total
>   Bounding Time:    0 hours  0 minutes  0 seconds (0.063 seconds)
>               using 1 thread(s) with 0.-01 CPU-seconds total

that's roughly en par.


> Render Time:
>   Photon Time:      No photons
>   Radiosity Time:   No radiosity
>   Trace Time:       0 hours  0 minutes 33 seconds (33.499 seconds)
>               using 4 thread(s) with 0.-04 CPU-seconds total

and that is *fast*.


>  It took 1:24.
>
> so, actually, quadruply confused - since it took over 13 min to do at work on
> what I believe is an i5.

the work machine a Linux box too?


> and this is my laptop at home:
>
> System:    Host: oem-Inspiron-N5110 Kernel: 4.10.0-38-generic x86_64 (64 bit
> gcc: 5.4.0)
>            Desktop: Xfce 4.12.3 (Gtk 2.24.28) Distro: Linux Mint 18.3 Sylvia
> Machine:   System: Dell (portable) product: Inspiron N5110
>            Mobo: Dell model: 034W60 v: A07 Bios: Dell v: A07 date: 07/18/2011
> CPU:       Dual core Intel Core i5-2410M (-HT-MCP-) cache: 3072 KB
>            flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9179
>            clock speeds: max: 2900 MHz 1: 983 MHz 2: 818 MHz 3: 827 MHz
>            4: 833 MHz

mine says 'Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz.  os is Slackware 14.1.

did you compile POV-Ray or installed a pre-built binary?  fwiw, I compile + add
"-march=native -mtune=native" to the compiler flags.


regards, jr.


Post a reply to this message

From: Bald Eagle
Subject: Re: TBTFH 2018 status
Date: 8 Sep 2018 00:20:00
Message: <web.5b931549abd6e8db458c7afe0@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:

> > a)  There's a quality 11?    (Throws horns, bangs head)
>
> :-)  section (docs v3.8, section 3.2.8.3)

I see.
For some reason the page I went to specified that section as I/O no
restrictions, but I found quality 9, 10, 11.
My message pane window displays the lower redundant value of 9.

> > b) I don't see a radiosity block in this scene...
>
> immediately below the '#include' lines, the (second) global_settings block.

Oh THAT radiosity "block".
First of all, that's a radiosity LINE, son.
And second of all, these damned dried frog pills that I imported from Scotland
send up a cloud of dust every time I bite into them, so I missed that sections
when I was scrolling down...


> > Render Time:
> >   Photon Time:      No photons
> >   Radiosity Time:   No radiosity
> >   Trace Time:       0 hours  0 minutes 33 seconds (33.499 seconds)
> >               using 4 thread(s) with 0.-04 CPU-seconds total
>
> and that is *fast*.

Well YEAH - WITHOUT radiosity.
I enable that commented line, and it took 27:40.   I thought I was doing ok when
it was at 3:30 and started actually rendering a visible scene, but then it hit
that BTFH....  :|


> the work machine a Linux box too?

Nope.
And now that you mention it, it's a 32-bit Win 7 box that has some
network-linked account......   I wonder what else that's slowing down....
That would explain a LOT about some of my spreadsheet woes.



> did you compile POV-Ray or installed a pre-built binary?  fwiw, I compile + add
> "-march=native -mtune=native" to the compiler flags.

I installed it as per Dick Balaska's instructions, so I'm just hoping he knows
what he's doing   :D


Parser Time
  Parse Time:       0 hours  0 minutes 47 seconds (47.337 seconds)
              using 1 thread(s) with 0.-01 CPU-seconds total
  Bounding Time:    0 hours  0 minutes  0 seconds (0.059 seconds)
              using 1 thread(s) with 0.-01 CPU-seconds total

Render Time:
  Photon Time:      No photons
  Radiosity Time:   0 hours  2 minutes 40 seconds (160.610 seconds)
              using 4 thread(s) with 0.-04 CPU-seconds total
  Trace Time:       0 hours 24 minutes 10 seconds (1450.793 seconds)
              using 4 thread(s) with 0.-04 CPU-seconds total

So it seems that your i3 is doing just fine   :)


Post a reply to this message

Goto Latest 10 Messages Next 10 Messages >>>

Copyright 2003-2008 Persistence of Vision Raytracer Pty. Ltd.