As I promised in the message 
  http://news.povray.org/3be6713e$1@news.povray.org,
I've uploaded a patch for 3D data at
  http://staff.aist.go.jp/r-suzuki/e/povray/iso/df_body.htm

Comments and suggestions are welcome.

R. Suzuki

Post a reply to this message

On Thu, 29 Aug 2002 17:07:54 +0900, "R. Suzuki" <r-s### [at] aistgojp> wrote:
> As I promised in the message 
>   http://news.povray.org/3be6713e$1@news.povray.org,
> I've uploaded a patch for 3D data at
>   http://staff.aist.go.jp/r-suzuki/e/povray/iso/df_body.htm
>
> Comments and suggestions are welcome.

I will add this to http://abx.art.pl/pov/patches/patches.php (with all patches
announced recently) as soon as possible.

ABX

Post a reply to this message

"R. Suzuki" wrote:
> 
> As I promised in the message
>   http://news.povray.org/3be6713e$1@news.povray.org,
> I've uploaded a patch for 3D data at
>   http://staff.aist.go.jp/r-suzuki/e/povray/iso/df_body.htm
> 
> Comments and suggestions are welcome.

Looks interesting and useful, the data file format seems somewhat strange
though, as i understand it you always have two files, the header and the
actual data file.  Wouldn't it be better to merge them, like in the ppm
image file format for example?

A macro for generating a density file from a function (using the file
writing routines) would be a useful addition.

BTW it would be very helpful if you could separate you changes with
'#ifdef DENSITY_PATCH' otherwise one will have to do a lot of searching to
find what you have changed.

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 13 Aug. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

in news:3D6DDF64.1627DB33@gmx.de Christoph Hormann wrote:

> Wouldn't it be better to merge them, like in the ppm
> image file format for example?

Don't think so, it would mean that one has to convert datasets to a format 
readable by POV-Ray, now one can just "describe" the way the dataset is 
put together in the sepparate header file and use it staight away.

Ingo

Post a reply to this message

"Christoph Hormann" <chr### [at] gmxde> wrote in message
news:3D6DDF64.1627DB33@gmx.de...
> Looks interesting and useful, the data file format seems somewhat strange
> though, as i understand it you always have two files, the header and the
> actual data file.  Wouldn't it be better to merge them, like in the ppm
> image file format for example?

It also allows one file if the filename of the data is not specified.
In this case, the data should be after the [data] line of the df file.

> A macro for generating a density file from a function (using the file
> writing routines) would be a useful addition.

It would be useful.

> BTW it would be very helpful if you could separate you changes with
> '#ifdef DENSITY_PATCH' otherwise one will have to do a lot of searching to
> find what you have changed.

OK.  I will add it in the next revision.

R. Suzuki

Post a reply to this message

On Thu, 29 Aug 2002 18:58:20 +0900, "R. Suzuki" <r-s### [at] aistgojp> wrote:
> > A macro for generating a density file from a function (using the file
> > writing routines) would be a useful addition.
>
> It would be useful.

That's what I tried for "really smooth" proximity/blur pattern: sample space,
write samples to file, load it and interpolate between.

ABX

Post a reply to this message

"R. Suzuki" wrote:
> 
> [...]
> 
> It also allows one file if the filename of the data is not specified.
> In this case, the data should be after the [data] line of the df file.
> 

I saw that after looking at the source code.  Some more documentation
about the header fields would be good, what does 'cyclic' mean for
example?

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 13 Aug. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

On Thu, 29 Aug 2002 10:46:28 +0200, Christoph Hormann <chr### [at] gmxde>
wrote:
> A macro for generating a density file from a function (using the file
> writing routines) would be a useful addition.

What about
  function 100,100,100{...}
?

ABX

Post a reply to this message

ABX wrote:
> 
> > A macro for generating a density file from a function (using the file
> > writing routines) would be a useful addition.
> 
> What about
>   function 100,100,100{...}
> ?

Hmm, interesting, you mean for use in:

#declare DATA3D2= function { 
  pattern{
    density_file function 100,100,100{...}
    interpolate 2    
  }
}

But a 'save_file' option would be good (for the 2D version this would be
useful too BTW)

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 13 Aug. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

"ABX" <abx### [at] abxartpl> wrote in message
news:n8mrmusor79q44peol7b0d4f5jse5n4fjf@4ax.com...
> I will add this to http://abx.art.pl/pov/patches/patches.php (with all patches
> announced recently) as soon as possible.

Thanks.  But I am still working on the coding.
The [Endian] option does not work at present.
And binary data formats in various platform should be added.

R. Suzuki

Post a reply to this message