POV-Ray : Newsgroups : povray.binaries.utilities : Wood design program test version Server Time
6 Oct 2022 19:05:22 EDT (-0400)
  Wood design program test version (Message 27 to 36 of 38)  
<<< Previous 10 Messages Goto Latest 10 Messages Next 2 Messages >>>
From: Thomas de Groot
Subject: Re: Wood design program test version
Date: 6 Jul 2022 02:18:09
Message: <62c52921$1@news.povray.org>
Op 05/07/2022 om 09:29 schreef And:

> I'm not clear this time. POV-Ray cannot use a number contains commas as you
> said, why I need add commas between every step of 10^3. I attach a picture, this
> picture is what I saw on my output data. Is the same format on your output data?
> 

This looks ok to me and is what I expected.

-- 
Thomas


Post a reply to this message

From: And
Subject: Re: Wood design program test version
Date: 6 Jul 2022 10:20:00
Message: <web.62c598e34b788a9817241155aa81652d@news.povray.org>
Thomas de Groot <tho### [at] degrootorg> wrote:
> Op 05/07/2022 om 09:29 schreef And:
>
> > I'm not clear this time. POV-Ray cannot use a number contains commas as you
> > said, why I need add commas between every step of 10^3. I attach a picture, this
> > picture is what I saw on my output data. Is the same format on your output data?
> >
>
> This looks ok to me and is what I expected.
>
> --
> Thomas

That's great.


Post a reply to this message

From: Thomas de Groot
Subject: Re: Wood design program test version
Date: 7 Jul 2022 11:42:49
Message: <62c6fef9$1@news.povray.org>
Almost error-free! :-)

In output file: example1_bumps_pattern_detail.inc  there are still five 
instances of offensive comma's that need to be replaced by dots. I show 
them here below with an arrow:

//----start code----
#include "bumps_detail_pattern_macros.inc"
#declare f_height_for_bumps_extent =
generate_bump_follow_height_trend_f(20.0);

// ------------ fiber ------------
#declare f_thin_fiber_mockup0 =
generate_thin_circled_pattern_f_input_t_theta_h(
10.0, 60.0, 3.0, 3.0, 0.015, 5,
0.007, 0,32,                      <=== 0,32 should be 0.32
0.00, 2.50, 0.14, 0.15,
seed(44),
0.014, 20.00
);

#declare f_thin_fiber_mockup1 =
generate_thin_circled_pattern_f_input_t_theta_h(
10.0, 60.0, 3.0, 3.0, 0.017, 4,
0.011, 0,32,                      <=== 0,32 should be 0.32
0.00, 2.50, 0.14, 0.15,
seed(45),
0.014, 20.00
);


#declare f_thin_fiber =
function(x, y, z, time_value) {
+0,50*f_thin_fiber_mockup0(           <=== 0,50 should be 0.50
     time_value,
     f_theta(x,y),
     f_height_for_bumps_extent(x, y, z)
)
+0,50*f_thin_fiber_mockup1(           <=== 0,50 should be 0.50
     time_value,
     f_theta(x,y),
     f_height_for_bumps_extent(x, y, z)
)
}

// ------------- large color ---------------------------

#declare f_large_color_block_mockup =
generate_thin_circled_pattern_f_input_t_theta_h(
10.0, 60.0, 3.0, 3.0, 2.32, 4,
0.144, 0,32,                      <=== 0,32 should be 0.32
0.00, 2.50, 0.14, 0.15,
seed(25),
0.014, 20.00
);

#declare f_large_color_block =
function(x, y, z, time_value) {
f_adjust_sharp_distribution(
     x, y, z,
     f_large_color_block_mockup(
         time_value,
         f_theta(x,y),
         f_height_for_bumps_extent(x, y, z)
     )
)
}
//----end code----

With these corrected, the application works!

I guess that those numbers may change with the input by the user (I did 
not see that happen, though). You know best where those particular 
numbers come from.

Next, I shall try to give my views/ideas on the layout, comprehensive 
use, etc, of the application.

-- 
Thomas


Post a reply to this message

From: Thomas de Groot
Subject: Re: Wood design program test version
Date: 7 Jul 2022 11:50:14
Message: <62c700b6$1@news.povray.org>
Forgot to mention, I used your version WoodDesignProgram alpha ver20220705.

-- 
Thomas


Post a reply to this message

From: And
Subject: Re: Wood design program test version
Date: 8 Jul 2022 03:30:00
Message: <web.62c7da1c4b788a98e660d035aa81652d@news.povray.org>
Thomas de Groot <tho### [at] degrootorg> wrote:
> Almost error-free! :-)
>
> In output file: example1_bumps_pattern_detail.inc  there are still five
> instances of offensive comma's that need to be replaced by dots. I show
> them here below with an arrow:
>
> //----start code----
> #include "bumps_detail_pattern_macros.inc"
> #declare f_height_for_bumps_extent =
> generate_bump_follow_height_trend_f(20.0);
>
> // ------------ fiber ------------
> #declare f_thin_fiber_mockup0 =
> generate_thin_circled_pattern_f_input_t_theta_h(
> 10.0, 60.0, 3.0, 3.0, 0.015, 5,
> 0.007, 0,32,                      <=== 0,32 should be 0.32
> 0.00, 2.50, 0.14, 0.15,
> seed(44),
> 0.014, 20.00
> );
>
> #declare f_thin_fiber_mockup1 =
> generate_thin_circled_pattern_f_input_t_theta_h(
> 10.0, 60.0, 3.0, 3.0, 0.017, 4,
> 0.011, 0,32,                      <=== 0,32 should be 0.32
> 0.00, 2.50, 0.14, 0.15,
> seed(45),
> 0.014, 20.00
> );
>
>
> #declare f_thin_fiber =
> function(x, y, z, time_value) {
> +0,50*f_thin_fiber_mockup0(           <=== 0,50 should be 0.50
>      time_value,
>      f_theta(x,y),
>      f_height_for_bumps_extent(x, y, z)
> )
> +0,50*f_thin_fiber_mockup1(           <=== 0,50 should be 0.50
>      time_value,
>      f_theta(x,y),
>      f_height_for_bumps_extent(x, y, z)
> )
> }
>
> // ------------- large color ---------------------------
>
> #declare f_large_color_block_mockup =
> generate_thin_circled_pattern_f_input_t_theta_h(
> 10.0, 60.0, 3.0, 3.0, 2.32, 4,
> 0.144, 0,32,                      <=== 0,32 should be 0.32
> 0.00, 2.50, 0.14, 0.15,
> seed(25),
> 0.014, 20.00
> );
>
> #declare f_large_color_block =
> function(x, y, z, time_value) {
> f_adjust_sharp_distribution(
>      x, y, z,
>      f_large_color_block_mockup(
>          time_value,
>          f_theta(x,y),
>          f_height_for_bumps_extent(x, y, z)
>      )
> )
> }
> //----end code----
>
> With these corrected, the application works!


Yes, I correct it now..
I correct another problem for ...maybe non-windows system cannot output files
when click that "output" button. But need to be tried.

And I add an "exit" function in a menu.


Post a reply to this message


Attachments:
Download 'wooddesignprogram alpha ver20220708.rar.dat' (967 KB)

From: And
Subject: Re: Wood design program test version
Date: 8 Jul 2022 03:45:00
Message: <web.62c7df654b788a98e660d035aa81652d@news.povray.org>
Thomas de Groot <tho### [at] degrootorg> wrote:
>
> I guess that those numbers may change with the input by the user (I did
> not see that happen, though). You know best where those particular
> numbers come from.
>

I have not finished that scheme yet. In fact, the GUI for controlling the
detailed pattern doesn't start to be designed.
You can change that part (..._bumps_pattern_detail.inc) yourself. If my memory
serves me right, the functions produced here is prepare for the
"tree_colormap_temp_file.inc" only. I will try different combines, too.


> Next, I shall try to give my views/ideas on the layout, comprehensive
> use, etc, of the application.
>
> --
> Thomas


:)


Post a reply to this message


Attachments:
Download 'wooddesignprogram alpha ver20220708.zip' (981 KB)

From: jr
Subject: Re: Wood design program test version
Date: 12 Jul 2022 07:35:00
Message: <web.62cd5afe4b788a981be3cd4b6cde94f1@news.povray.org>
hi,

(it is a day for "bugs", it seems :-))


"And" <49341109@ntnu.edu.tw> wrote:
> Thomas de Groot <tho### [at] degrootorg> wrote:
> > ...
> > Next, I shall try to give my views/ideas on the layout, comprehensive
> > use, etc, of the application.

tells me it works on MS Windows, but not (for me) on Linux (like 'rtr' </sigh>).

after exiting the program and changing into the 'example1' directory, POV-Ray
does not like the spaces in the file name, so when:

  $ povparse +i"show tree function.pov"

Problem with option setting
/usr/local/bin/povray-3.8.0-beta.2 +w32 +h32 -d -f -p -gr -gs +ishow tree
function.pov
Failed to parse command-line option

another error occurs because the 'pretrace_*' settings depend on image size, eg
with the (small) WxH settings above.

however, file renamed and using a large enough WxH, I get another error.  not
even sure what the problem is supposed to be (since the code looks kosher (to
the untutored eye)):

File 'functions.inc' line 9: Parse Warning: Scene language version changed after
 a 'default' statement. The changes in defaults normally associated with the
 language version change are not applied.
File 'example1_angular_shape_factor.inc' line 10: Possible Parse Error:
 Suspicious identifier found in function! If you want to call a function make
 sure the function you call has been declared. If you call an internal function,
 make sure you have included 'functions.inc'.
File 'example1_angular_shape_factor.inc' line 10: Parse Error: Expected
 'operator', ( found instead
Fatal error in parser: Cannot parse input.
Render failed


regards, jr.


Post a reply to this message

From: And
Subject: Re: Wood design program test version
Date: 13 Jul 2022 03:20:00
Message: <web.62ce71f44b788a989ac997d1aa81652d@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> (it is a day for "bugs", it seems :-))
>
>
> "And" <49341109@ntnu.edu.tw> wrote:
> > Thomas de Groot <tho### [at] degrootorg> wrote:
> > > ...
> > > Next, I shall try to give my views/ideas on the layout, comprehensive
> > > use, etc, of the application.
>
> tells me it works on MS Windows, but not (for me) on Linux (like 'rtr' </sigh>).
>
> after exiting the program and changing into the 'example1' directory, POV-Ray
> does not like the spaces in the file name, so when:
>
>   $ povparse +i"show tree function.pov"
>
> Problem with option setting
> /usr/local/bin/povray-3.8.0-beta.2 +w32 +h32 -d -f -p -gr -gs +ishow tree
> function.pov
> Failed to parse command-line option
>
> another error occurs because the 'pretrace_*' settings depend on image size, eg
> with the (small) WxH settings above.
>
> however, file renamed and using a large enough WxH, I get another error.  not
> even sure what the problem is supposed to be (since the code looks kosher (to
> the untutored eye)):
>
> File 'functions.inc' line 9: Parse Warning: Scene language version changed after
>  a 'default' statement. The changes in defaults normally associated with the
>  language version change are not applied.
> File 'example1_angular_shape_factor.inc' line 10: Possible Parse Error:
>  Suspicious identifier found in function! If you want to call a function make
>  sure the function you call has been declared. If you call an internal function,
>  make sure you have included 'functions.inc'.
> File 'example1_angular_shape_factor.inc' line 10: Parse Error: Expected
>  'operator', ( found instead
> Fatal error in parser: Cannot parse input.
> Render failed
>
>
> regards, jr.


Thanks.
It should copy some text but it didn't.
(I should use \ not // for the file path connect)

I fix it and attach a new version.
No any other change, besides adding axis on the angular-shape-editor for
identify the direction.


Post a reply to this message


Attachments:
Download 'wooddesignprogram alpha ver20220713.zip' (982 KB)

From: jr
Subject: Re: Wood design program test version
Date: 13 Jul 2022 04:35:00
Message: <web.62ce83224b788a981be3cd4b6cde94f1@news.povray.org>
hi,

"And" <49341109@ntnu.edu.tw> wrote:
> I fix it and attach a new version.
> No any other change, besides adding axis on the angular-shape-editor for
> identify the direction.

works, thanks.  now need to find time to play.  cheers.


regards, jr.


Post a reply to this message

From: And
Subject: Re: Wood design program test version
Date: 14 Jul 2022 02:55:00
Message: <web.62cfbd8f4b788a989ac997d1aa81652d@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "And" <49341109@ntnu.edu.tw> wrote:
> > I fix it and attach a new version.
> > No any other change, besides adding axis on the angular-shape-editor for
> > identify the direction.
>
> works, thanks.  now need to find time to play.  cheers.
>
>
> regards, jr.

Glad to hear that works.


Post a reply to this message

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

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