POV-Ray : Newsgroups : povray.general : Shortest Code Contest Server Time
7 Aug 2024 05:21:42 EDT (-0400)
  Shortest Code Contest (Message 4 to 13 of 33)  
<<< Previous 3 Messages Goto Latest 10 Messages Next 10 Messages >>>
From:
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 10:15:53
Message: <b3eg4u0dkeatvgk5p28e8qquf4rfim241m@4ax.com>
On Fri, 18 Jan 2002 09:55:40 -0500, "Greg M. Johnson" <gregj:-)565### [at] aolcom>
wrote:
> > >    b) Make it compatible with povray 3.5.
> >
> > with specification or reality ?
>
> Comments anyone?

Some examples:
- camera behaviour was changed but documentation not updated yet.
- something with isosurfaces'll change afaik
  (I don't know how changes influence appearance).
- sphere sweeps differ from behaviour described in documentation.
- radiosity has bugs
- splines has bugs
- there are a few of blob bugs
- and many others from Known Bugs lists

There is a chance someone can discover nice 500 bytes long scene unfortunatelly
based on bug (without his knowledge), send it , and next beta can destroy his
effort.

ABX


Post a reply to this message

From: Ron Parker
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 10:20:29
Message: <slrna4gf9v.6ds.ron.parker@fwi.com>
On Fri, 18 Jan 2002 09:44:34 -0500, Greg M. Johnson wrote:
>     d) MAX size: 500 bytes (arbitrarily chosen as twice the size of one very
> competent sig file posted to p.g.)

sig files already have a max size: 320 bytes.  Any longer and they're not
sig files.  So if you limited participants to, say, 300 bytes (to make up for
word wrap issues) then they'd be making sig files.

Wow!  500 bytes.  Whatever will I do with all that space?

Seriously, though, no theme or anything?  It's easy to come up with an 
attractive-looking pseudo-abstract image in a small number of bytes.  An
image that actually has a point - like "neon" or "uses bicubic patches to
draw letters" or the below-included "spectrum" - is a lot more difficult. 

--
#macro R(L P)sphere{L __}cylinder{L P __}#end#macro P(_1)union{R(z+_ z)R(-z _-z)
R(_-z*3_+z)torus{1__ clipped_by{plane{_ 0}}}translate z+_1}#end#macro S(_)9-(_1-
_)*(_1-_)#end#macro Z(_1 _ __)union{P(_)P(-_)R(y-z-1_)translate.1*_1-y*8pigment{
rgb<S(7)S(5)S(3)>}}#if(_1)Z(_1-__,_,__)#end#end Z(10x*-2,.2)camera{rotate x*90}


Post a reply to this message

From: Jan Walzer
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 10:59:36
Message: <3c484668@news.povray.org>
I think the sourcecodes should also be shown to the pics, to enable the
voters
to judge by "quality" ...


BTW: How 'bout Mutiple Entries per person?


--
[Talking about cardriving]
"People are opstacles?
Oh...I always treat them as bonus points..." [Ian Burgmyer in p.o-t]
// Jan Walzer <jan### [at] lzernet>


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 11:14:35
Message: <3c4849eb$1@news.povray.org>
"Jan Walzer" <jan### [at] lzernet> wrote in message
news:3c484668@news.povray.org...
> I think the sourcecodes should also be shown to the pics, to enable the
> voters to judge by "quality" ...

Well, that's what makes it all the more interesting.  It's a raw judge of
"quality" without knowing how small.  If some bloke decides to do a fractal,
well maybe that's cool to some, and crap to others.


> BTW: How 'bout Mutiple Entries per person?

2 raised to the power of a relatively small integer.


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 11:15:43
Message: <3c484a2f$1@news.povray.org>

news:b3eg4u0dkeatvgk5p28e8qquf4rfim241m@4ax.com...
> There is a chance someone can discover nice 500 bytes long scene
unfortunatelly
> based on bug (without his knowledge), send it , and next beta can destroy
his
> effort.

Fair enough.  COmments?
Should some just have to face the consequences if they take this risk?


Post a reply to this message

From: Ron Parker
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 11:30:05
Message: <slrna4gjcg.6eq.ron.parker@fwi.com>
On Fri, 18 Jan 2002 09:44:34 -0500, Greg M. Johnson wrote:
>     b) Make it compatible with povray 3.5.

rons_really_cool_signature_file //RLP

Works with the next beta of version 3.5.  Outputs the Mona Lisa.  What do I
win? :)

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 14:18:01
Message: <3c4874e9$1@news.povray.org>
"Ron Parker" <ron### [at] povrayorg> wrote in message
news:slr### [at] fwicom...
> rons_really_cool_signature_file //RLP
>

Judges reserve right to reject entries using features never mentioned in the
docs.


Post a reply to this message

From: Anders K 
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 15:36:17
Message: <3c488741$1@news.povray.org>
> sig files already have a max size: 320 bytes.  Any longer and they're not
> sig files.

According to who? Mine is just over 400 bytes.

Anders

--
light_source{6#local D#macro B(E)#macro A(D)#declare#declare C=mod(E
D);E=(E-C)/D;C#end#while(E)#if(A(8)=7)#declare D=D+2.8;#else#if(C<3)
}cylinder{0(C=<1 2>).2translate<D+C*A(2)A(4)#else}intersection{torus
{1 .2}box{-2y}rotate<1 0C>*90translate<D+1A(2)*2+1#end-2 13>pigment{
rgb x}finish{specular 1}#end#end#end=-8;1B(445000298)B(519053970)B(
483402386)B(1445571258)B(77778740)B(541684549)B(42677491)B(70)}


Post a reply to this message

From: Bill DeWitt
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 15:37:59
Message: <3c4887a7$1@news.povray.org>
"Anders K." <and### [at] prostard2gcom> wrote in message
news:3c488741$1@news.povray.org...
> > sig files already have a max size: 320 bytes.  Any longer and they're
not
> > sig files.
>
> According to who?

    According to the convention of four lines of eighty characters.


Post a reply to this message

From: Warp
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 16:39:18
Message: <3c489606@news.povray.org>
Bill DeWitt <bde### [at] cflrrcom> wrote:
:     According to the convention of four lines of eighty characters.

  In fact, it's better to use well less than 80 characters in order to avoid
line wrapping in quotes (I think that the recommendation is something like
72 characters in a line).

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -


Post a reply to this message

<<< Previous 3 Messages Goto Latest 10 Messages Next 10 Messages >>>

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