rcontrib: warning - partial accumulaton in final record

What's the STDOUT look like from that rfluxmtx command? I hit this issue once, when I had a '-c (n)' somewhere in my command pipeline and it wasn't consistent.

···

On 8/5/16, 8:48 AM, "Germán Molina Larrain" <[email protected]<mailto:[email protected]>> wrote:

Hello everyone,

I have a question that I could not solve using Google, so I brought it to you guys. I have been playing a bit with RFLUXMTX with the purpose of implementing multi-phase methods for Tubular Daylight Devices, but I am getting the error shown in the title of this e-mail.

"RCONTRIB: Warning - partial accumulation in final record"

I am using the command:

rfluxmtx -ab 3 -ad 512 -lw 1e-3 ./TDDs/4-TDD.top ./Skies/white_sky.rad ./Materials/materials.mat ./scene.rad ./Windows/windows.rad > ./DC/4-TDD-sky.mtx

The content of the files is specified below my signature.

Any idea what might be happening? I have seen that this happens "sometimes" (even for the same command)... is it a memory issue? user error? should this be in the developers list?

I AM USING NREL's x64 WINDOWS BINARIES

Thanks in advance to all!

Germán

================================================

where 4-TDD.top file is

#@rfluxmtx h=kf u=Y
void light lens_mat 0 0 3 1 1 1

lens_mat polygon 4370_4
0
0
72 1.45 1.3414213562373087 3.34
    1.49 1.373205080756887 3.34
    1.54 1.3 3.34
    1.59 1.39 3.34
...

and white_sky.rad is

#@rfluxmtx h=u u=Y
void glow ground_glow
0 0 4 1 1 1 0

ground_glow source ground
0 0 4 0 0 -1 180

#@rfluxmtx h=r1 u=Y
void glow sky_glow
0 0 4 1 1 1 0

sky_glow source sky
0 0 4 0 0 1 180

Hello Rob,

I thought RFLUXMTX managed all those options for us! It looks like this...
I am not sure how many rays are getting into it through the STDIN, though

The STDOUT looks like this:

#?RADIANCE
oconv -f ./Materials/materials.mat ./scene.rad ./Windows/windows.rad
./Skies/white_sky.rad
rcontrib -fo+ -ab 3 -ad 512 -lw 1e-3 -fda -c 10000 -bn 1 -b
if(-Dx*0-Dy*0-Dz*1,0,-1) -m ground_glow -f reinhartb.cal -p
MF=1,rNx=0,rNy=0,rNz=-1,Ux=0,Uy=1,Uz=0,RHS=+1 -bn Nrbins -b rbin -m
sky_glow -y 145
SOFTWARE= NREL 5.0.a.11 (by googs 2016.05.24) based on RADIANCE 5.0
Official Release by G. Ward
CAPDATE= 2016:08:05 10:45:38
GMT= 2016:08:05 13:45:38
NCOMP=3
NROWS=145
NCOLS=146
FORMAT=ascii

···

2016-08-05 12:03 GMT-03:00 Guglielmetti, Robert < [email protected]>:

What's the STDOUT look like from that rfluxmtx command? I hit this issue
once, when I had a '-c (n)' somewhere in my command pipeline and it wasn't
consistent.

On 8/5/16, 8:48 AM, "Germán Molina Larrain" <[email protected]<mailto:g > [email protected]>> wrote:

Hello everyone,

I have a question that I could not solve using Google, so I brought it to
you guys. I have been playing a bit with RFLUXMTX with the purpose of
implementing multi-phase methods for Tubular Daylight Devices, but I am
getting the error shown in the title of this e-mail.

"RCONTRIB: Warning - partial accumulation in final record"

I am using the command:

rfluxmtx -ab 3 -ad 512 -lw 1e-3 ./TDDs/4-TDD.top ./Skies/white_sky.rad
./Materials/materials.mat ./scene.rad ./Windows/windows.rad >
./DC/4-TDD-sky.mtx

The content of the files is specified below my signature.

Any idea what might be happening? I have seen that this happens
"sometimes" (even for the same command)... is it a memory issue? user
error? should this be in the developers list?

I AM USING NREL's x64 WINDOWS BINARIES

Thanks in advance to all!

Germán

================================================

where 4-TDD.top file is

#@rfluxmtx h=kf u=Y
void light lens_mat 0 0 3 1 1 1

lens_mat polygon 4370_4
0
0
72 1.45 1.3414213562373087 3.34
    1.49 1.373205080756887 3.34
    1.54 1.3 3.34
    1.59 1.39 3.34
...

and white_sky.rad is

#@rfluxmtx h=u u=Y
void glow ground_glow
0 0 4 1 1 1 0

ground_glow source ground
0 0 4 0 0 -1 180

#@rfluxmtx h=r1 u=Y
void glow sky_glow
0 0 4 1 1 1 0

sky_glow source sky
0 0 4 0 0 1 180

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

It does, but you can still slip in default overrides in some of your setup files (which it does not look like you've done here). Your sky looks good, with the ground first and then the sky. Not sure what's going on.

···

On 8/5/16, 9:11 AM, "Germán Molina Larrain" <[email protected]<mailto:[email protected]>> wrote:

Hello Rob,

I thought RFLUXMTX managed all those options for us! It looks like this... I am not sure how many rays are getting into it through the STDIN, though

The STDOUT looks like this:

#?RADIANCE
oconv -f ./Materials/materials.mat ./scene.rad ./Windows/windows.rad ./Skies/white_sky.rad
rcontrib -fo+ -ab 3 -ad 512 -lw 1e-3 -fda -c 10000 -bn 1 -b if(-Dx*0-Dy*0-Dz*1,0,-1) -m ground_glow -f reinhartb.cal -p MF=1,rNx=0,rNy=0,rNz=-1,Ux=0,Uy=1,Uz=0,RHS=+1 -bn Nrbins -b rbin -m sky_glow -y 145
SOFTWARE= NREL 5.0.a.11 (by googs 2016.05.24) based on RADIANCE 5.0 Official Release by G. Ward
CAPDATE= 2016:08:05 10:45:38
GMT= 2016:08:05 13:45:38
NCOMP=3
NROWS=145
NCOLS=146
FORMAT=ascii

2016-08-05 12:03 GMT-03:00 Guglielmetti, Robert <[email protected]<mailto:[email protected]>>:
What's the STDOUT look like from that rfluxmtx command? I hit this issue once, when I had a '-c (n)' somewhere in my command pipeline and it wasn't consistent.

On 8/5/16, 8:48 AM, "Germán Molina Larrain" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote:

Hello everyone,

I have a question that I could not solve using Google, so I brought it to you guys. I have been playing a bit with RFLUXMTX with the purpose of implementing multi-phase methods for Tubular Daylight Devices, but I am getting the error shown in the title of this e-mail.

"RCONTRIB: Warning - partial accumulation in final record"

I am using the command:

rfluxmtx -ab 3 -ad 512 -lw 1e-3 ./TDDs/4-TDD.top ./Skies/white_sky.rad ./Materials/materials.mat ./scene.rad ./Windows/windows.rad > ./DC/4-TDD-sky.mtx

The content of the files is specified below my signature.

Any idea what might be happening? I have seen that this happens "sometimes" (even for the same command)... is it a memory issue? user error? should this be in the developers list?

I AM USING NREL's x64 WINDOWS BINARIES

Thanks in advance to all!

Germán

================================================

where 4-TDD.top file is

#@rfluxmtx h=kf u=Y
void light lens_mat 0 0 3 1 1 1

lens_mat polygon 4370_4
0
0
72 1.45 1.3414213562373087 3.34
    1.49 1.373205080756887 3.34
    1.54 1.3 3.34
    1.59 1.39 3.34
...

and white_sky.rad is

#@rfluxmtx h=u u=Y
void glow ground_glow
0 0 4 1 1 1 0

ground_glow source ground
0 0 4 0 0 -1 180

#@rfluxmtx h=r1 u=Y
void glow sky_glow
0 0 4 1 1 1 0

sky_glow source sky
0 0 4 0 0 1 180

_______________________________________________
Radiance-general mailing list
[email protected]<mailto:[email protected]>
http://www.radiance-online.org/mailman/listinfo/radiance-general

Oh, crap I missed that one, and forgot German's on Windows. Let's hope this is not that bug, since the binaries german's using include those fixes...

···

On 8/5/16, 9:36 AM, "Greg Ward" <[email protected]<mailto:[email protected]>> wrote:

Hi Germán,

As you can see, rcontrib is passed binary data from rfluxmtx (-fda), and we have seen issues with this on Windows in the past, but I've been told it's no longer a problem. The best way to test is to temporarily replace the rcontrib command with something that captures the input to a file, so we can check that it's the right length. In Unix, you would do this with an executable shell script like the following and call it "rcontrib":

:
cat > /tmp/saved_data.bin

On Windows, you might need to write a Perl program. Just make sure it's something that correctly captures binary data without doing anything to it. Then, make sure the file contains 145*10000*6*8 bytes in it.

-Greg

From: Germán Molina Larrain <[email protected]<mailto:[email protected]>>

Date: August 5, 2016 8:11:09 AM PDT

Hello Rob,

I thought RFLUXMTX managed all those options for us! It looks like this... I am not sure how many rays are getting into it through the STDIN, though

The STDOUT looks like this:

#?RADIANCE
oconv -f ./Materials/materials.mat ./scene.rad ./Windows/windows.rad ./Skies/white_sky.rad
rcontrib -fo+ -ab 3 -ad 512 -lw 1e-3 -fda -c 10000 -bn 1 -b if(-Dx*0-Dy*0-Dz*1,0,-1) -m ground_glow -f reinhartb.cal -p MF=1,rNx=0,rNy=0,rNz=-1,Ux=0,Uy=1,Uz=0,RHS=+1 -bn Nrbins -b rbin -m sky_glow -y 145
SOFTWARE= NREL 5.0.a.11 (by googs 2016.05.24) based on RADIANCE 5.0 Official Release by G. Ward
CAPDATE= 2016:08:05 10:45:38
GMT= 2016:08:05 13:45:38
NCOMP=3
NROWS=145
NCOLS=146
FORMAT=ascii

2016-08-05 12:03 GMT-03:00 Guglielmetti, Robert <[email protected]<mailto:[email protected]>>:
What's the STDOUT look like from that rfluxmtx command? I hit this issue once, when I had a '-c (n)' somewhere in my command pipeline and it wasn't consistent.

On 8/5/16, 8:48 AM, "Germán Molina Larrain" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote:

Hello everyone,

I have a question that I could not solve using Google, so I brought it to you guys. I have been playing a bit with RFLUXMTX with the purpose of implementing multi-phase methods for Tubular Daylight Devices, but I am getting the error shown in the title of this e-mail.

"RCONTRIB: Warning - partial accumulation in final record"

I am using the command:

rfluxmtx -ab 3 -ad 512 -lw 1e-3 ./TDDs/4-TDD.top ./Skies/white_sky.rad ./Materials/materials.mat ./scene.rad ./Windows/windows.rad > ./DC/4-TDD-sky.mtx

The content of the files is specified below my signature.

Any idea what might be happening? I have seen that this happens "sometimes" (even for the same command)... is it a memory issue? user error? should this be in the developers list?

I AM USING NREL's x64 WINDOWS BINARIES

Thanks in advance to all!

Germán

================================================

where 4-TDD.top file is

#@rfluxmtx h=kf u=Y
void light lens_mat 0 0 3 1 1 1

lens_mat polygon 4370_4
0
0
72 1.45 1.3414213562373087 3.34
    1.49 1.373205080756887 3.34
    1.54 1.3 3.34
    1.59 1.39 3.34
...

and white_sky.rad is

#@rfluxmtx h=u u=Y
void glow ground_glow
0 0 4 1 1 1 0

ground_glow source ground
0 0 4 0 0 -1 180

#@rfluxmtx h=r1 u=Y
void glow sky_glow
0 0 4 1 1 1 0

sky_glow source sky
0 0 4 0 0 1 180

_______________________________________________
Radiance-general mailing list
[email protected]<mailto:[email protected]>
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]<mailto:[email protected]>
http://www.radiance-online.org/mailman/listinfo/radiance-general

Hello everyone,

I have a question that I could not solve using Google, so I brought it to
you guys. I have been playing a bit with RFLUXMTX with the purpose of
implementing multi-phase methods for Tubular Daylight Devices, but I am
getting the error shown in the title of this e-mail.

"RCONTRIB: Warning - partial accumulation in final record"

I am using the command:

rfluxmtx -ab 3 -ad 512 -lw 1e-3 ./TDDs/4-TDD.top ./Skies/white_sky.rad
./Materials/materials.mat ./scene.rad ./Windows/windows.rad >
./DC/4-TDD-sky.mtx

The content of the files is specified below my signature.

Any idea what might be happening? I have seen that this happens "sometimes"
(even for the same command)... is it a memory issue? user error? should
this be in the developers list?

*I AM USING NREL's x64 WINDOWS BINARIES*
Thanks in advance to all!

Germán

···

================================================

where 4-TDD.top file is

#@rfluxmtx h=kf u=Y
void light lens_mat 0 0 3 1 1 1

lens_mat polygon 4370_4
0
0
72 1.45 1.3414213562373087 3.34
    1.49 1.373205080756887 3.34
    1.54 1.3 3.34
    1.59 1.39 3.34
...

and white_sky.rad is

#@rfluxmtx h=u u=Y
void glow ground_glow
0 0 4 1 1 1 0

ground_glow source ground
0 0 4 0 0 -1 180

#@rfluxmtx h=r1 u=Y
void glow sky_glow
0 0 4 1 1 1 0

sky_glow source sky
0 0 4 0 0 1 180

Hi Germán,

As you can see, rcontrib is passed binary data from rfluxmtx (-fda), and we have seen issues with this on Windows in the past, but I've been told it's no longer a problem. The best way to test is to temporarily replace the rcontrib command with something that captures the input to a file, so we can check that it's the right length. In Unix, you would do this with an executable shell script like the following and call it "rcontrib":

:
cat > /tmp/saved_data.bin

On Windows, you might need to write a Perl program. Just make sure it's something that correctly captures binary data without doing anything to it. Then, make sure the file contains 145*10000*6*8 bytes in it.

-Greg

···

From: Germán Molina Larrain <[email protected]>
Date: August 5, 2016 8:11:09 AM PDT

Hello Rob,

I thought RFLUXMTX managed all those options for us! It looks like this... I am not sure how many rays are getting into it through the STDIN, though

The STDOUT looks like this:

#?RADIANCE
oconv -f ./Materials/materials.mat ./scene.rad ./Windows/windows.rad ./Skies/white_sky.rad
rcontrib -fo+ -ab 3 -ad 512 -lw 1e-3 -fda -c 10000 -bn 1 -b if(-Dx*0-Dy*0-Dz*1,0,-1) -m ground_glow -f reinhartb.cal -p MF=1,rNx=0,rNy=0,rNz=-1,Ux=0,Uy=1,Uz=0,RHS=+1 -bn Nrbins -b rbin -m sky_glow -y 145
SOFTWARE= NREL 5.0.a.11 (by googs 2016.05.24) based on RADIANCE 5.0 Official Release by G. Ward
CAPDATE= 2016:08:05 10:45:38
GMT= 2016:08:05 13:45:38
NCOMP=3
NROWS=145
NCOLS=146
FORMAT=ascii

2016-08-05 12:03 GMT-03:00 Guglielmetti, Robert <[email protected]>:
What's the STDOUT look like from that rfluxmtx command? I hit this issue once, when I had a '-c (n)' somewhere in my command pipeline and it wasn't consistent.

On 8/5/16, 8:48 AM, "Germán Molina Larrain" <[email protected]<mailto:[email protected]>> wrote:

Hello everyone,

I have a question that I could not solve using Google, so I brought it to you guys. I have been playing a bit with RFLUXMTX with the purpose of implementing multi-phase methods for Tubular Daylight Devices, but I am getting the error shown in the title of this e-mail.

"RCONTRIB: Warning - partial accumulation in final record"

I am using the command:

rfluxmtx -ab 3 -ad 512 -lw 1e-3 ./TDDs/4-TDD.top ./Skies/white_sky.rad ./Materials/materials.mat ./scene.rad ./Windows/windows.rad > ./DC/4-TDD-sky.mtx

The content of the files is specified below my signature.

Any idea what might be happening? I have seen that this happens "sometimes" (even for the same command)... is it a memory issue? user error? should this be in the developers list?

I AM USING NREL's x64 WINDOWS BINARIES

Thanks in advance to all!

Germán

================================================

where 4-TDD.top file is

#@rfluxmtx h=kf u=Y
void light lens_mat 0 0 3 1 1 1

lens_mat polygon 4370_4
0
0
72 1.45 1.3414213562373087 3.34
    1.49 1.373205080756887 3.34
    1.54 1.3 3.34
    1.59 1.39 3.34
...

and white_sky.rad is

#@rfluxmtx h=u u=Y
void glow ground_glow
0 0 4 1 1 1 0

ground_glow source ground
0 0 4 0 0 -1 180

#@rfluxmtx h=r1 u=Y
void glow sky_glow
0 0 4 1 1 1 0

sky_glow source sky
0 0 4 0 0 1 180

_______________________________________________
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