Soooo, my previous question has been answered. You may recall I was asking
why my Ruby script was not parsing the rtcontrib command to write out the
146 tregenza patch images. All the variables were being passed and expanded
out correctly. Problem was the view file I was handing it was bogus, and
*this* error message does not make it back to the STDERR. Lesson learned.
That resolved, I am testing further, and am finding that for a given
rtcontrib run, I don't always get 146 image files. Some views yield 142,
some 144. Any ideas on that?
Hi Rob,
Glad you found the error in your script.
rtcontrib outputs an image or value for each bin starting at 0 up to the last bin that has a value. So it could be that a the last few bins don't contribute to your scene so no image is created. You can force rtcontrib to write all images/values using the -bn option. Try setting -bn 146 if you're using tregenza.cal or -bn Nrbins if you're using reinhart.cal
Also, for the next step you may want the new (since July 1) version of dctimestep. It allows you to combine daylight coefficient images like so:
gendaylit [options] | genskyvec -m 1 | dctimestep myimage_%03d.hdr > output.hdr
where the "myimage" bit matches the -o output specification used in rtcontrib.
Best,
Andy
···
On Aug 31, 2010, at 1:59 PM, Guglielmetti, Robert wrote:
Soooo, my previous question has been answered. You may recall I was asking
why my Ruby script was not parsing the rtcontrib command to write out the
146 tregenza patch images. All the variables were being passed and expanded
out correctly. Problem was the view file I was handing it was bogus, and
*this* error message does not make it back to the STDERR. Lesson learned.
That resolved, I am testing further, and am finding that for a given
rtcontrib run, I don't always get 146 image files. Some views yield 142,
some 144. Any ideas on that?
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
Hi Andy,
Yeah, for some reason, that "no view in file" error was never making it to
the command line when called from within a script.
Thanks very much for these tips! I initially thought that it was that there
no values found so no images were created for certain patches, but there are
definitely some "black" images being created, so I ruled that out. Good to
know about the -bn option. Thank you.
This new option to dctimestep is awesome!!! Definitely makes quick work of
what I'm currently trying to do in bash and it's giving me a headache. I'll
check it out now. Thanks to you and Greg I assume?
=8-)
Did I say thank you?
- Rob
P.S. Thank you. A beer for you and a root beer for Greg.
···
On 8/31/10 4:19 PM, "Andy McNeil" <[email protected]> wrote:
Hi Rob,
Glad you found the error in your script.
rtcontrib outputs an image or value for each bin starting at 0 up to the last
bin that has a value. So it could be that a the last few bins don't
contribute to your scene so no image is created. You can force rtcontrib to
write all images/values using the -bn option. Try setting -bn 146 if you're
using tregenza.cal or -bn Nrbins if you're using reinhart.cal
Also, for the next step you may want the new (since July 1) version of
dctimestep. It allows you to combine daylight coefficient images like so:
gendaylit [options] | genskyvec -m 1 | dctimestep myimage_%03d.hdr >
output.hdr
where the "myimage" bit matches the -o output specification used in rtcontrib.
Best,
Andy
On Aug 31, 2010, at 1:59 PM, Guglielmetti, Robert wrote:
Soooo, my previous question has been answered. You may recall I was asking
why my Ruby script was not parsing the rtcontrib command to write out the
146 tregenza patch images. All the variables were being passed and expanded
out correctly. Problem was the view file I was handing it was bogus, and
*this* error message does not make it back to the STDERR. Lesson learned.
That resolved, I am testing further, and am finding that for a given
rtcontrib run, I don't always get 146 image files. Some views yield 142,
some 144. Any ideas on that?
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
Hmmm, grabbed the HEAD release, compiled, and tried:
gensky 03 21 12 +s -a 40 -o 115 -m 115 | genskyvec -m 1 | dctimestep
./filename%03d.hdr > combined.hdr
But it just prints the usage/help line and produces a zero byte image. The
files exist, and there are noe 146 of them (-bn 146). Not sure what's wrong.
?
- Rob
···
On 8/31/10 4:19 PM, "Andy McNeil" <[email protected]> wrote:
Hi Rob,
Glad you found the error in your script.
rtcontrib outputs an image or value for each bin starting at 0 up to the last
bin that has a value. So it could be that a the last few bins don't
contribute to your scene so no image is created. You can force rtcontrib to
write all images/values using the -bn option. Try setting -bn 146 if you're
using tregenza.cal or -bn Nrbins if you're using reinhart.cal
Also, for the next step you may want the new (since July 1) version of
dctimestep. It allows you to combine daylight coefficient images like so:
gendaylit [options] | genskyvec -m 1 | dctimestep myimage_%03d.hdr >
output.hdr
where the "myimage" bit matches the -o output specification used in rtcontrib.
Best,
Andy
On Aug 31, 2010, at 1:59 PM, Guglielmetti, Robert wrote:
Soooo, my previous question has been answered. You may recall I was asking
why my Ruby script was not parsing the rtcontrib command to write out the
146 tregenza patch images. All the variables were being passed and expanded
out correctly. Problem was the view file I was handing it was bogus, and
*this* error message does not make it back to the STDERR. Lesson learned.
That resolved, I am testing further, and am finding that for a given
rtcontrib run, I don't always get 146 image files. Some views yield 142,
some 144. Any ideas on that?
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
Hi Rob,
does the usage say this:
Usage: dctimestep DCspec [tregvec]
or: dctimestep Vspec Tbsdf.xml Dmat.dat [tregvec]
or just this:
Usage: dctimestep Vspec Tbsdf.xml Dmat.dat [tregvec]
Could the problem be that dctimestep didn't get installed properly?
Andy
···
On Aug 31, 2010, at 4:04 PM, Guglielmetti, Robert wrote:
Hmmm, grabbed the HEAD release, compiled, and tried:
gensky 03 21 12 +s -a 40 -o 115 -m 115 | genskyvec -m 1 | dctimestep
./filename%03d.hdr > combined.hdr
But it just prints the usage/help line and produces a zero byte image. The
files exist, and there are noe 146 of them (-bn 146). Not sure what's wrong.
?
- Rob
On 8/31/10 4:19 PM, "Andy McNeil" <[email protected]> wrote:
Hi Rob,
Glad you found the error in your script.
rtcontrib outputs an image or value for each bin starting at 0 up to the last
bin that has a value. So it could be that a the last few bins don't
contribute to your scene so no image is created. You can force rtcontrib to
write all images/values using the -bn option. Try setting -bn 146 if you're
using tregenza.cal or -bn Nrbins if you're using reinhart.cal
Also, for the next step you may want the new (since July 1) version of
dctimestep. It allows you to combine daylight coefficient images like so:
gendaylit [options] | genskyvec -m 1 | dctimestep myimage_%03d.hdr >
output.hdr
where the "myimage" bit matches the -o output specification used in rtcontrib.
Best,
Andy
On Aug 31, 2010, at 1:59 PM, Guglielmetti, Robert wrote:
Soooo, my previous question has been answered. You may recall I was asking
why my Ruby script was not parsing the rtcontrib command to write out the
146 tregenza patch images. All the variables were being passed and expanded
out correctly. Problem was the view file I was handing it was bogus, and
*this* error message does not make it back to the STDERR. Lesson learned.
That resolved, I am testing further, and am finding that for a given
rtcontrib run, I don't always get 146 image files. Some views yield 142,
some 144. Any ideas on that?
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
You guessed it Andy, I compiled the new code to the wrong directory, in my haste. Now it works. (!) Big thanks.
- Rob
Hi Rob,
does the usage say this:
Usage: dctimestep DCspec [tregvec]
or: dctimestep Vspec Tbsdf.xml Dmat.dat [tregvec]
or just this:
Usage: dctimestep Vspec Tbsdf.xml Dmat.dat [tregvec]
Could the problem be that dctimestep didn't get installed properly?
Andy
···
On 8/31/10 5:42 PM, "Andy McNeil" <[email protected]> wrote:
On Aug 31, 2010, at 4:04 PM, Guglielmetti, Robert wrote:
Hmmm, grabbed the HEAD release, compiled, and tried:
gensky 03 21 12 +s -a 40 -o 115 -m 115 | genskyvec -m 1 | dctimestep
./filename%03d.hdr > combined.hdr
But it just prints the usage/help line and produces a zero byte image. The
files exist, and there are noe 146 of them (-bn 146). Not sure what's wrong.
?
- Rob
On 8/31/10 4:19 PM, "Andy McNeil" <[email protected]> wrote:
Hi Rob,
Glad you found the error in your script.
rtcontrib outputs an image or value for each bin starting at 0 up to the last
bin that has a value. So it could be that a the last few bins don't
contribute to your scene so no image is created. You can force rtcontrib to
write all images/values using the -bn option. Try setting -bn 146 if you're
using tregenza.cal or -bn Nrbins if you're using reinhart.cal
Also, for the next step you may want the new (since July 1) version of
dctimestep. It allows you to combine daylight coefficient images like so:
gendaylit [options] | genskyvec -m 1 | dctimestep myimage_%03d.hdr >
output.hdr
where the "myimage" bit matches the -o output specification used in rtcontrib.
Best,
Andy
On Aug 31, 2010, at 1:59 PM, Guglielmetti, Robert wrote:
Soooo, my previous question has been answered. You may recall I was asking
why my Ruby script was not parsing the rtcontrib command to write out the
146 tregenza patch images. All the variables were being passed and expanded
out correctly. Problem was the view file I was handing it was bogus, and
*this* error message does not make it back to the STDERR. Lesson learned.
That resolved, I am testing further, and am finding that for a given
rtcontrib run, I don't always get 146 image files. Some views yield 142,
some 144. Any ideas on that?
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general