sudo recontrib

Dear Humberto,

Yes, I am trying without "-n 8760" option, as follow:

dctimestep photocells.vmx Film3M_145x1297_9142012_t.xml southest.dmx
Barcelona.smx
fatal - unexpected EOF reading Barcelona.smx

I do not know. Thank you,
Urtza.

Humberto Antunes <[email protected]> escribió:

···

Hi Urtza,
   Are you running dctimestep with the "-n" option? If yes try to run it
without it. use:
   
   dctimestep view.mtx daylight.mtx transmision.xml sky.mtx
   
   For me this solved the problem, no need for the "-n 8760" option.
   
   Hope it helps.
   
   Best regards
   Humberto A.

   2016-03-21 11:16 GMT+00:00 <[email protected]>:

_Dear Andy and Greg,

(I am trying to follow Humberto's issue, as well)
I have added to View Matrix sensor points number (I notice that in
Daylight Matrix I have not had NROWS data and I have added NROWS=145).
To sum up I have; Sky Matrix, 2306x8760; Daylight Matrix, 145x2306; and
View Matrix, 552x145. I launched dctimestep and it scripts the same
error (fatal - unexpected EOF reading Barcelona.smx).

In case, I review the Sky Matrix with "wc" and I get almost the number
that Greg suggested:

wc Barcelona.smx

20202874 60601692 213155298 Barcelona.smx

I do not know what is the problem with Sky Matrix (although it seems a
little estrange 2306x8760 data are in rows).
Thank you in advance,
Urtza.

"Gregory J. Ward" <[email protected]> escribió:_

_Following this up on the general mailing list..._
         _ _
         _The problem was the one Andy pointed out earlier, where the
newer version of dctimestep doesn't want the "-n" option when the sky
matrix has a header._
         _ _
         _Regarding the new question (appearing below), using rmtxop
in this way is indeed the simplest means to convert RGB irradiance to
illuminance in lux._
         _ _
         _Cheers,_
         _-Greg_

_FROM: Humberto Antunes <[email protected]>_
           _SUBJECT: Re: dctimesteps_
           _DATE: March 20, 2016 6:04:36 PM PDT_
           _ _

_I tried to run the command like that and it worked just fine, i got
the same results as you did. _ _ _
            _I was running the dctimestep command with the -n 8760
option, but this is not needed because the sky matrix already
contains that info in the header, running it like you solved the
issue._
            _ _
            _Now there is just one thing remaining, to convert the
RGB values from illum.dat file to illuminance values can i use the
command below or is there a better way?_
            _ _
            _rmtxop -c 47.435 119.93 11.635 results/illum.dat>
results/illum_final.dat_
            _ _
            _Note:_
            _179*0.265=47.436_
            _179*0.670=119.93_
            _179*0.065=11.635_
            _ _
            _Best regards_
            _Humberto A._

            _2016-03-21 0:01 GMT+00:00 Gregory J.
Ward <[email protected]>:_

_Thanks, Humberto. I ran the following command:_
               _ _
               _dctimestep photocells.vmx singleclear.xml south.dmx
lisboa.smx > illum.dat_
               _ _
               _without complaint. I am attaching the result._
               _ _
               _Are you sure you have a recent installation of
dctimestep? What do you see when you run dctimestep with no
arguments? You should get:_
               _ _
                               _Usage: dctimestep [-n nsteps][-o
ospec][-i{f|d|h}][-o{f|d}] DCspec [skyf]_
                _ or: dctimestep [-n nsteps][-o
ospec][-i{f|d|h}][-o{f|d}] Vspec Tbsdf Dmat.dat [skyf]_

               _ _
               _Cheers,_
               _-Greg_
               _ _

_FROM: Greg Ward <[email protected]>_

          _SUBJECT: Re: [Radiance-general] sudo recontrib_

          _DATE: March 20, 2016 2:47:23 PM PDT_

          _ _

_Hi Humberto,_
          _ _
          _Actually, your header and ASCII data look OK. Although
some tools would put all the columns together in one humungous line
with 8760x3, white space has no meaning here and gendaymtx output has
a newline for each column entry with an extra empty line between
rows._
          _ _
          _If you run the "wc" command on your file, you should get
something like:_
          _ _
          _20202873 60601692 xxxxxxxxxxx lisboa.smx_
          _ _
          _I don't know what xxxxxxx will be, but some large number
corresponding to the number of bytes in your file. The first two
values may not be exactly this, but should be reasonably close.
Otherwise, your file really is missing some data at the end._
          _ _
          _If your numbers agree roughly with the above, please send
me a gzip'ped copies of your lisboa.wea and the output (*.smx) file
in a private e-mail and I will see if I can figure out what is going
on._
          _ _
          _Cheers,_
          _-Greg_

_FROM: Humberto Antunes <[email protected]>_

           _SUBJECT: Re: [Radiance-general] sudo recontrib_

           _DATE: March 20, 2016 2:30:23 PM PDT_

           _ _

_Hi Urtza and Andy, _ _ _
            _I am having the same issue as you do Urtza, I have
already checked the headers of my view matrix, daylight matrix and
sky matrix, and that doesn't seem to be the problem, my view matrix
is a 6X145, the daylight matrix a 145X2306, and finally, the sky
matrix is a 2306X8760, and this info is on the headers of each._
            _ _
            _I think the problem is in the sky matrix file itself,
it's not being properly written._
            _ _
            _Mine looks like this:_
                         _#?RADIANCE_
             _gendaymtx -m 4 weather/lisboa.wea_
             _LATLONG= 38.73000000 -9.15000000_
             _NROWS=2306_
             _NCOLS=8760_
             _NCOMP=3_
             _FORMAT=ascii_
             _ _
             _0 0 0_
             _0.477 0.477 0.477_
             _1.85 1.85 1.85_
             _4.85 4.85 4.85_
             _11.6 11.6 11.6_
             _10.5 10.5 10.5_

            _..._
            _ _
            _So it doesn't have the number of columns it should, i
think that each row has the RGB value for one patch of one time step
and it should have the RGB values for all time steps of one patch,
is that it?_
            _ _
            _Best regards_
            _Humberto A._

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

I have read more carefully you e-mail, do you have 552 sensor points? if
yes your number of rows in the view matrix is 552 and not 145, try to
change NROWS=552 in you view matrix.

Best regards
Humberto A.

···

2016-03-21 12:38 GMT+00:00 <[email protected]>:

Dear Humberto,

Yes, I am trying without "-n 8760" option, as follow:

dctimestep photocells.vmx Film3M_145x1297_9142012_t.xml southest.dmx
Barcelona.smx
fatal - unexpected EOF reading Barcelona.smx

I do not know. Thank you,
Urtza.

Humberto Antunes <[email protected]> escribió:

Hi Urtza,

Are you running dctimestep with the "-n" option? If yes try to run it
without it. use:

dctimestep view.mtx daylight.mtx transmision.xml sky.mtx

For me this solved the problem, no need for the "-n 8760" option.

Hope it helps.

Best regards
Humberto A.

2016-03-21 11:16 GMT+00:00 <[email protected]>:

*Dear Andy and Greg, (I am trying to follow Humberto's issue, as well) I
have added to View Matrix sensor points number (I notice that in Daylight
Matrix I have not had NROWS data and I have added NROWS=145). To sum up I
have; Sky Matrix, 2306x8760; Daylight Matrix, 145x2306; and View Matrix,
552x145. I launched dctimestep and it scripts the same error (fatal -
unexpected EOF reading Barcelona.smx). In case, I review the Sky Matrix
with "wc" and I get almost the number that Greg suggested: wc Barcelona.smx
20202874 60601692 213155298 Barcelona.smx I do not know what is the
problem with Sky Matrix (although it seems a little estrange 2306x8760 data
are in rows). Thank you in advance, Urtza. "Gregory J. Ward"
<[email protected] <[email protected]>> escribió:*

*Following this up on the general mailing list...*

*The problem was the one Andy pointed out earlier, where the newer
version of dctimestep doesn't want the "-n" option when the sky matrix has
a header.*

*Regarding the new question (appearing below), using rmtxop in this way
is indeed the simplest means to convert RGB irradiance to illuminance in
lux.*

*Cheers,*
*-Greg*

*From: Humberto Antunes <[email protected]
<[email protected]>>*
*Subject: Re: dctimesteps*
*Date: March 20, 2016 6:04:36 PM PDT*

*I tried to run the command like that and it worked just fine, i got the
same results as you did.*

*I was running the dctimestep command with the -n 8760 option, but this
is not needed because the sky matrix already contains that info in the
header, running it like you solved the issue.*

*Now there is just one thing remaining, to convert the RGB values from
illum.dat file to illuminance values can i use the command below or is
there a better way?*

*rmtxop -c 47.435 119.93 11.635 results/illum.dat>
results/illum_final.dat*

*Note:*
*179*0.265=47.436*
*179*0.670=119.93*
*179*0.065=11.635*

*Best regards*
*Humberto A.*

*2016-03-21 0:01 GMT+00:00 Gregory J. Ward <[email protected]
<[email protected]>>:*

*Thanks, Humberto. I ran the following command:*

*dctimestep photocells.vmx singleclear.xml south.dmx lisboa.smx >
illum.dat*

*without complaint. I am attaching the result.*

*Are you sure you have a recent installation of dctimestep? What do you
see when you run dctimestep with no arguments? You should get:*

*Usage: dctimestep [-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] DCspec
[skyf]*
* or: dctimestep [-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] Vspec Tbsdf
Dmat.dat [skyf]*

*Cheers,*
*-Greg*

*From: Greg Ward <[email protected] <[email protected]>>*

*Subject: Re: [Radiance-general] sudo recontrib*

*Date: March 20, 2016 2:47:23 PM PDT*

*Hi Humberto,*

*Actually, your header and ASCII data look OK. Although some tools would
put all the columns together in one humungous line with 8760x3, white space
has no meaning here and gendaymtx output has a newline for each column
entry with an extra empty line between rows.*

*If you run the "wc" command on your file, you should get something
like:*

*20202873 60601692 xxxxxxxxxxx lisboa.smx*

*I don't know what xxxxxxx will be, but some large number corresponding
to the number of bytes in your file. The first two values may not be
exactly this, but should be reasonably close. Otherwise, your file really
is missing some data at the end.*

*If your numbers agree roughly with the above, please send me a gzip'ped
copies of your lisboa.wea and the output (*.smx) file in a private e-mail
and I will see if I can figure out what is going on.*

*Cheers,*
*-Greg*

*From: Humberto Antunes <[email protected]
<[email protected]>>*

*Subject: Re: [Radiance-general] sudo recontrib*

*Date: March 20, 2016 2:30:23 PM PDT*

*Hi Urtza and Andy,*

*I am having the same issue as you do Urtza, I have already checked the
headers of my view matrix, daylight matrix and sky matrix, and that doesn't
seem to be the problem, my view matrix is a 6X145, the daylight matrix a
145X2306, and finally, the sky matrix is a 2306X8760, and this info is on
the headers of each.*

*I think the problem is in the sky matrix file itself, it's not being
properly written.*

*Mine looks like this:*
*#?RADIANCE*
*gendaymtx -m 4 weather/lisboa.wea*
*LATLONG= 38.73000000 -9.15000000*
*NROWS=2306*
*NCOLS=8760*
*NCOMP=3*
*FORMAT=ascii*

*0 0 0*
*0 0 0*
*0 0 0*
*0 0 0*
*0 0 0*
*0 0 0*
*0 0 0*
*0.477 0.477 0.477*
*1.85 1.85 1.85*
*4.85 4.85 4.85*
*11.6 11.6 11.6*
*10.5 10.5 10.5*
*...*

*So it doesn't have the number of columns it should, i think that each
row has the RGB value for one patch of one time step and it should have the
RGB values for all time steps of one patch, is that it?*

*Best regards*
*Humberto A.*

*_______________________________________________ Radiance-general mailing
list [email protected]
<[email protected]>
http://www.radiance-online.org/mailman/listinfo/radiance-general
<http://www.radiance-online.org/mailman/listinfo/radiance-general&gt;\*

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

Yes, I have in View Matrix NROWS=552 and NCOLS=145 (I think that you have
6 sensor points, so 6x145).
Does it make sense? I think they are 145 Klems patches.

Best regards,
Urtza.

Humberto Antunes <[email protected]> escribió:

I have read more carefully you e-mail, do you have 552 sensor points? if
yes your number of rows in the view matrix is 552 and not 145, try to
change NROWS=552 in you view matrix.
   Best regards
   Humberto A.

_Dear Humberto,

Yes, I am trying without "-n 8760" option, as follow:

dctimestep photocells.vmx Film3M_145x1297_9142012_t.xml southest.dmx
Barcelona.smx
fatal - unexpected EOF reading Barcelona.smx

I do not know. Thank you,
Urtza.

Humberto Antunes <[email protected]> escribió:_

_Hi Urtza, _ _ _
          _Are you running dctimestep with the "-n" option? If yes try
to run it without it. use:_
          _ _
          _dctimestep view.mtx daylight.mtx transmision.xml sky.mtx_
          _ _
          _For me this solved the problem, no need for the "-n 8760"
option._
          _ _
          _Hope it helps._
          _ _
          _Best regards_
          _Humberto A._

          _2016-03-21 11:16 GMT+00:00 <[email protected]>:_

__Dear Andy and Greg,

(I am trying to follow Humberto's issue, as well)
I have added to View Matrix sensor points number (I notice that in
Daylight Matrix I have not had NROWS data and I have added
NROWS=145). To sum up I have; Sky Matrix, 2306x8760; Daylight Matrix,
145x2306; and View Matrix, 552x145. I launched dctimestep and it
scripts the same error (fatal - unexpected EOF reading Barcelona.smx).

In case, I review the Sky Matrix with "wc" and I get almost the
number that Greg suggested:

wc Barcelona.smx

20202874 60601692 213155298 Barcelona.smx

I do not know what is the problem with Sky Matrix (although it seems
a little estrange 2306x8760 data are in rows).
Thank you in advance,
Urtza.

"Gregory J. Ward" <[email protected]> escribió:__

__Following this up on the general mailing list...__
                __ __
                __The problem was the one Andy pointed out earlier,
where the newer version of dctimestep doesn't want the "-n" option
when the sky matrix has a header.__
                __ __
                __Regarding the new question (appearing below),
using rmtxop in this way is indeed the simplest means to convert RGB
irradiance to illuminance in lux.__
                __ __
                __Cheers,__
                __-Greg__

__FROM: Humberto Antunes <[email protected]>__
                  __SUBJECT: Re: dctimesteps__
                  __DATE: March 20, 2016 6:04:36 PM PDT__
                  __ __

__I tried to run the command like that and it worked just fine, i
got the same results as you did._ _
    __ __
                   __I was running the dctimestep command with the
-n 8760 option, but this is not needed because the sky matrix
already contains that info in the header, running it like you
solved the issue.__
                   __ __
                   __Now there is just one thing remaining, to
convert the RGB values from illum.dat file to illuminance values
can i use the command below or is there a better way?__
                   __ __
                   __rmtxop -c 47.435 119.93 11.635
results/illum.dat> results/illum_final.dat__
                   __ __
                   __Note:__
                   __179*0.265=47.436__
                   __179*0.670=119.93__
                   __179*0.065=11.635__
                   __ __
                   __Best regards__
                   __Humberto A.__

                   __2016-03-21 0:01 GMT+00:00 Gregory J.
Ward <[email protected]>:__

__Thanks, Humberto. I ran the following command:__
                      __ __
                      __dctimestep photocells.vmx singleclear.xml
south.dmx lisboa.smx > illum.dat__
                      __ __
                      __without complaint. I am attaching the
result.__
                      __ __
                      __Are you sure you have a recent
installation of dctimestep? What do you see when you run
dctimestep with no arguments? You should get:__
                      __ __
                                             __Usage: dctimestep
[-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] DCspec [skyf]__
                       __ or: dctimestep [-n nsteps][-o
ospec][-i{f|d|h}][-o{f|d}] Vspec Tbsdf Dmat.dat [skyf]__

                      __ __
                      __Cheers,__
                      __-Greg__
                      __ __

__FROM: Greg Ward <[email protected]>__

                 __SUBJECT: Re: [Radiance-general] sudo recontrib__

                 __DATE: March 20, 2016 2:47:23 PM PDT__

                 __ __

__Hi Humberto,__
                 __ __
                 __Actually, your header and ASCII data look OK.
Although some tools would put all the columns together in one
humungous line with 8760x3, white space has no meaning here and
gendaymtx output has a newline for each column entry with an extra
empty line between rows.__
                 __ __
                 __If you run the "wc" command on your file, you
should get something like:__
                 __ __
                 __20202873 60601692 xxxxxxxxxxx lisboa.smx__
                 __ __
                 __I don't know what xxxxxxx will be, but some
large number corresponding to the number of bytes in your file.
The first two values may not be exactly this, but should be
reasonably close. Otherwise, your file really is missing some data
at the end.__
                 __ __
                 __If your numbers agree roughly with the above,
please send me a gzip'ped copies of your lisboa.wea and the output
(*.smx) file in a private e-mail and I will see if I can figure out
what is going on.__
                 __ __
                 __Cheers,__
                 __-Greg__

__FROM: Humberto Antunes <[email protected]>__

                  __SUBJECT: Re: [Radiance-general] sudo

recontrib__

···

   2016-03-21 12:38 GMT+00:00 <[email protected]>:

                  __DATE: March 20, 2016 2:30:23 PM PDT__

                  __ __

__Hi Urtza and Andy,_ _ __ __
                   __I am having the same issue as you do Urtza, I
have already checked the headers of my view matrix, daylight
matrix and sky matrix, and that doesn't seem to be the problem, my
view matrix is a 6X145, the daylight matrix a 145X2306, and
finally, the sky matrix is a 2306X8760, and this info is on the
headers of each.__
                   __ __
                   __I think the problem is in the sky matrix file
itself, it's not being properly written.__
                   __ __
                   __Mine looks like this:__
                                       __#?RADIANCE__
                    __gendaymtx -m 4 weather/lisboa.wea__
                    __LATLONG= 38.73000000 -9.15000000__
                    __NROWS=2306__
                    __NCOLS=8760__
                    __NCOMP=3__
                    __FORMAT=ascii__
                    __ __
                    __0 0 0__
                    __0.477 0.477 0.477__
                    __1.85 1.85 1.85__
                    __4.85 4.85 4.85__
                    __11.6 11.6 11.6__
                    __10.5 10.5 10.5__

                   __...__
                   __ __
                   __So it doesn't have the number of columns it
should, i think that each row has the RGB value for one patch of
one time step and it should have the RGB values for all time steps
of one patch, is that it?__
                   __ __
                   __Best regards__
                   __Humberto A.__

_ _

_________________________________________________
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_

Can you send the output of "getinfo" on your matrix files, i.e.:

  getinfo photocells.vmx southest.dmx Barcelona.smx

Also, send the output of dctimestep executed with no arguments. (It should produce a usage message.)

Thanks,
-Greg

···

From: [email protected]
Subject: Re: [Radiance-general] sudo recontrib
Date: March 21, 2016 6:32:24 AM PDT

Yes, I have in View Matrix NROWS=552 and NCOLS=145 (I think that you have 6 sensor points, so 6x145).
Does it make sense? I think they are 145 Klems patches.

Best regards,
Urtza.

Humberto Antunes <[email protected]> escribió:

I have read more carefully you e-mail, do you have 552 sensor points? if yes your number of rows in the view matrix is 552 and not 145, try to change NROWS=552 in you view matrix.

Best regards
Humberto A.

2016-03-21 12:38 GMT+00:00 <[email protected]>:
Dear Humberto,

Yes, I am trying without "-n 8760" option, as follow:

dctimestep photocells.vmx Film3M_145x1297_9142012_t.xml southest.dmx Barcelona.smx
fatal - unexpected EOF reading Barcelona.smx

I do not know. Thank you,
Urtza.

Humberto Antunes <[email protected]> escribió:

Hi Urtza,

Are you running dctimestep with the "-n" option? If yes try to run it without it. use:

dctimestep view.mtx daylight.mtx transmision.xml sky.mtx

For me this solved the problem, no need for the "-n 8760" option.

Hope it helps.

Best regards
Humberto A.

2016-03-21 11:16 GMT+00:00 <[email protected]>:
Dear Andy and Greg,

(I am trying to follow Humberto's issue, as well)
I have added to View Matrix sensor points number (I notice that in Daylight Matrix I have not had NROWS data and I have added NROWS=145). To sum up I have; Sky Matrix, 2306x8760; Daylight Matrix, 145x2306; and View Matrix, 552x145. I launched dctimestep and it scripts the same error (fatal - unexpected EOF reading Barcelona.smx).

In case, I review the Sky Matrix with "wc" and I get almost the number that Greg suggested:

wc Barcelona.smx

20202874 60601692 213155298 Barcelona.smx

I do not know what is the problem with Sky Matrix (although it seems a little estrange 2306x8760 data are in rows).
Thank you in advance,
Urtza.

"Gregory J. Ward" <[email protected]> escribió:

Following this up on the general mailing list...

The problem was the one Andy pointed out earlier, where the newer version of dctimestep doesn't want the "-n" option when the sky matrix has a header.

Regarding the new question (appearing below), using rmtxop in this way is indeed the simplest means to convert RGB irradiance to illuminance in lux.

Cheers,
-Greg

From: Humberto Antunes <[email protected]>
Subject: Re: dctimesteps
Date: March 20, 2016 6:04:36 PM PDT

I tried to run the command like that and it worked just fine, i got the same results as you did.

I was running the dctimestep command with the -n 8760 option, but this is not needed because the sky matrix already contains that info in the header, running it like you solved the issue.

Now there is just one thing remaining, to convert the RGB values from illum.dat file to illuminance values can i use the command below or is there a better way?

rmtxop -c 47.435 119.93 11.635 results/illum.dat> results/illum_final.dat

Note:
179*0.265=47.436
179*0.670=119.93
179*0.065=11.635

Best regards
Humberto A.

2016-03-21 0:01 GMT+00:00 Gregory J. Ward <[email protected]>:
Thanks, Humberto. I ran the following command:

dctimestep photocells.vmx singleclear.xml south.dmx lisboa.smx > illum.dat

without complaint. I am attaching the result.

Are you sure you have a recent installation of dctimestep? What do you see when you run dctimestep with no arguments? You should get:

Usage: dctimestep [-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] DCspec [skyf]
   or: dctimestep [-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] Vspec Tbsdf Dmat.dat [skyf]

Cheers,
-Greg

From: Greg Ward <[email protected]>
Subject: Re: [Radiance-general] sudo recontrib
Date: March 20, 2016 2:47:23 PM PDT

Hi Humberto,

Actually, your header and ASCII data look OK. Although some tools would put all the columns together in one humungous line with 8760x3, white space has no meaning here and gendaymtx output has a newline for each column entry with an extra empty line between rows.

If you run the "wc" command on your file, you should get something like:

20202873 60601692 xxxxxxxxxxx lisboa.smx

I don't know what xxxxxxx will be, but some large number corresponding to the number of bytes in your file. The first two values may not be exactly this, but should be reasonably close. Otherwise, your file really is missing some data at the end.

If your numbers agree roughly with the above, please send me a gzip'ped copies of your lisboa.wea and the output (*.smx) file in a private e-mail and I will see if I can figure out what is going on.

Cheers,
-Greg

From: Humberto Antunes <[email protected]>
Subject: Re: [Radiance-general] sudo recontrib
Date: March 20, 2016 2:30:23 PM PDT

Hi Urtza and Andy,

I am having the same issue as you do Urtza, I have already checked the headers of my view matrix, daylight matrix and sky matrix, and that doesn't seem to be the problem, my view matrix is a 6X145, the daylight matrix a 145X2306, and finally, the sky matrix is a 2306X8760, and this info is on the headers of each.

I think the problem is in the sky matrix file itself, it's not being properly written.

Mine looks like this:
#?RADIANCE
gendaymtx -m 4 weather/lisboa.wea
LATLONG= 38.73000000 -9.15000000
NROWS=2306
NCOLS=8760
NCOMP=3
FORMAT=ascii

0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0.477 0.477 0.477
1.85 1.85 1.85
4.85 4.85 4.85
11.6 11.6 11.6
10.5 10.5 10.5
...

So it doesn't have the number of columns it should, i think that each row has the RGB value for one patch of one time step and it should have the RGB values for all time steps of one patch, is that it?

Best regards
Humberto A.

_______________________________________________
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

Dear Greg,
That are the output of getinfo:
  photocells.vmx:
  #?RADIANCE
  oconv material.rad sc-vi3Mphase.rad window.rad
  rcontrib -f /usr/share/radiance/klems_int.cal -b
kbin(-sqrt(.5),sqrt(.5),0,0,0,1) -bn Nkbins -m windowglow -I+ -ab 2 -ad
1000 -lw 2e-5 -y 552
  SOFTWARE= RADIANCE 5.0a (NREL build 5.0.a.2) lastmod Fri Apr 24 15:04:00
MDT 2015 by googs on lu040t-001
  CAPDATE= 2016:03:21 10:54:51
  GMT= 2016:03:21 09:54:51
  NCOMP=3
  NROWS=552
  NCOLS=145
  FORMAT=ascii
  
  southest.dmx:
  #?RADIANCE
  oconv material.rad sc-vi3Mphase.rad sky_overcast.rad
  rcontrib -c 1000 -e MF:4 -f reinhart.cal -b rbin -bn Nrbins -m sky_glow
  SOFTWARE= RADIANCE 5.0a (NREL build 5.0.a.2) lastmod Fri Apr 24 15:04:00
MDT 2015 by googs on lu040t-001
  CAPDATE= 2016:03:22 09:22:32
  GMT= 2016:03:22 08:22:32
  NCOMP=3
  NCOLS=2306
  FORMAT=ascii
  
  Barcelona.smx:
  #?RADIANCE
  gendaymtx -m 4 Barcelona.wea
  LATLONG= 41.28000000 2.07000000
  NROWS=2306
  NCOLS=8760
  NCOMP=3
  FORMAT=ascii

(In the southest.dmx I add NROWS=145 with test editor after. I have
launched with that data but it scripts the same error)

And If I am understanding well, the output of dctimestep is this script (It
does not script nothing more):
fatal - unexpected EOF reading Barcelona.smx

Thank you very much in advance.
Best regards,
Urtza.

Greg Ward <[email protected]> escribió:

Can you send the output of "getinfo" on your matrix files, i.e.:
  getinfo photocells.vmx southest.dmx Barcelona.smx
  
  Also, send the output of dctimestep executed with no arguments. (It
should produce a usage message.)

  Thanks,
  -Greg

FROM: [email protected]

    SUBJECT: Re: [Radiance-general] sudo recontrib

    DATE: March 21, 2016 6:32:24 AM PDT

    

  Yes, I have in View Matrix NROWS=552 and NCOLS=145 (I think that you have
6 sensor points, so 6x145).
Does it make sense? I think they are 145 Klems patches.

Best regards,
Urtza.

Humberto Antunes <[email protected]> escribió:

I have read more carefully you e-mail, do you have 552 sensor points? if
yes your number of rows in the view matrix is 552 and not 145, try to
change NROWS=552 in you view matrix.
   Best regards
   Humberto A.

_Dear Humberto,

Yes, I am trying without "-n 8760" option, as follow:

dctimestep photocells.vmx Film3M_145x1297_9142012_t.xml southest.dmx
Barcelona.smx
fatal - unexpected EOF reading Barcelona.smx

I do not know. Thank you,
Urtza.

Humberto Antunes <[email protected]> escribió:_

_Hi Urtza,_ _ _
          _Are you running dctimestep with the "-n" option? If yes try
to run it without it. use:_
          _ _
          _dctimestep view.mtx daylight.mtx transmision.xml sky.mtx_
          _ _
          _For me this solved the problem, no need for the "-n 8760"
option._
          _ _
          _Hope it helps._
          _ _
          _Best regards_
          _Humberto A._

          _2016-03-21 11:16 GMT+00:00 <[email protected]>:_

__Dear Andy and Greg,

(I am trying to follow Humberto's issue, as well)
I have added to View Matrix sensor points number (I notice that in
Daylight Matrix I have not had NROWS data and I have added
NROWS=145). To sum up I have; Sky Matrix, 2306x8760; Daylight Matrix,
145x2306; and View Matrix, 552x145. I launched dctimestep and it
scripts the same error (fatal - unexpected EOF reading Barcelona.smx).

In case, I review the Sky Matrix with "wc" and I get almost the
number that Greg suggested:

wc Barcelona.smx

20202874 60601692 213155298 Barcelona.smx

I do not know what is the problem with Sky Matrix (although it seems
a little estrange 2306x8760 data are in rows).
Thank you in advance,
Urtza.

"Gregory J. Ward" <[email protected]> escribió:__

__Following this up on the general mailing list...__
                __ __
                __The problem was the one Andy pointed out earlier,
where the newer version of dctimestep doesn't want the "-n" option
when the sky matrix has a header.__
                __ __
                __Regarding the new question (appearing below),
using rmtxop in this way is indeed the simplest means to convert RGB
irradiance to illuminance in lux.__
                __ __
                __Cheers,__
                __-Greg__

__FROM: Humberto Antunes <[email protected]>__
                  __SUBJECT: Re: dctimesteps__
                  __DATE: March 20, 2016 6:04:36 PM PDT__
                  __ __

__I tried to run the command like that and it worked just fine, i
got the same results as you did.__
   __ __
                   __I was running the dctimestep command with the
-n 8760 option, but this is not needed because the sky matrix
already contains that info in the header, running it like you
solved the issue.__
                   __ __
                   __Now there is just one thing remaining, to
convert the RGB values from illum.dat file to illuminance values
can i use the command below or is there a better way?__
                   __ __
                   __rmtxop -c 47.435 119.93 11.635
results/illum.dat> results/illum_final.dat__
                   __ __
                   __Note:__
                   __179*0.265=47.436__
                   __179*0.670=119.93__
                   __179*0.065=11.635__
                   __ __
                   __Best regards__
                   __Humberto A.__

                   __2016-03-21 0:01 GMT+00:00 Gregory J.
Ward <[email protected]>:__

__Thanks, Humberto. I ran the following command:__
                      __ __
                      __dctimestep photocells.vmx singleclear.xml
south.dmx lisboa.smx > illum.dat__
                      __ __
                      __without complaint. I am attaching the
result.__
                      __ __
                      __Are you sure you have a recent
installation of dctimestep? What do you see when you run
dctimestep with no arguments? You should get:__
                      __ __
                                             __Usage: dctimestep
[-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] DCspec [skyf]__
                       __ or: dctimestep [-n nsteps][-o
ospec][-i{f|d|h}][-o{f|d}] Vspec Tbsdf Dmat.dat [skyf]__

                      __ __
                      __Cheers,__
                      __-Greg__
                      __ __

__FROM: Greg Ward <[email protected]>__

                 __SUBJECT: Re: [Radiance-general] sudo recontrib__

                 __DATE: March 20, 2016 2:47:23 PM PDT__

                 __ __

__Hi Humberto,__
                 __ __
                 __Actually, your header and ASCII data look OK.
Although some tools would put all the columns together in one
humungous line with 8760x3, white space has no meaning here and
gendaymtx output has a newline for each column entry with an extra
empty line between rows.__
                 __ __
                 __If you run the "wc" command on your file, you
should get something like:__
                 __ __
                 __20202873 60601692 xxxxxxxxxxx lisboa.smx__
                 __ __
                 __I don't know what xxxxxxx will be, but some
large number corresponding to the number of bytes in your file.
The first two values may not be exactly this, but should be
reasonably close. Otherwise, your file really is missing some data
at the end.__
                 __ __
                 __If your numbers agree roughly with the above,
please send me a gzip'ped copies of your lisboa.wea and the output
(*.smx) file in a private e-mail and I will see if I can figure out
what is going on.__
                 __ __
                 __Cheers,__
                 __-Greg__

__FROM: Humberto Antunes <[email protected]>__

                  __SUBJECT: Re: [Radiance-general] sudo

recontrib__

···

   2016-03-21 12:38 GMT+00:00 <[email protected]>:

                  __DATE: March 20, 2016 2:30:23 PM PDT__

                  __ __

__Hi Urtza and Andy,__ __ __
                   __I am having the same issue as you do Urtza, I
have already checked the headers of my view matrix, daylight
matrix and sky matrix, and that doesn't seem to be the problem, my
view matrix is a 6X145, the daylight matrix a 145X2306, and
finally, the sky matrix is a 2306X8760, and this info is on the
headers of each.__
                   __ __
                   __I think the problem is in the sky matrix file
itself, it's not being properly written.__
                   __ __
                   __Mine looks like this:__
                                       __#?RADIANCE__
                    __gendaymtx -m 4 weather/lisboa.wea__
                    __LATLONG= 38.73000000 -9.15000000__
                    __NROWS=2306__
                    __NCOLS=8760__
                    __NCOMP=3__
                    __FORMAT=ascii__
                    __ __
                    __0 0 0__
                    __0.477 0.477 0.477__
                    __1.85 1.85 1.85__
                    __4.85 4.85 4.85__
                    __11.6 11.6 11.6__
                    __10.5 10.5 10.5__

                   __...__
                   __ __
                   __So it doesn't have the number of columns it
should, i think that each row has the RGB value for one patch of
one time step and it should have the RGB values for all time steps
of one patch, is that it?__
                   __ __
                   __Best regards__
                   __Humberto A.__

_ _

_________________________________________________
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

Hi Urtza,

You need not bother sending the gzip'ped file. You have an outdated installation of dctimestep, and I believe this is your problem.

I don't know which version you have, exactly, but you should go to the NREL page and get the latest version of Radiance before working on this further.

Cheers,
-Greg

···

From: [email protected]
Subject: Re: [Radiance-general] sudo recontrib
Date: March 22, 2016 9:36:46 AM PDT
Dear Greg,
Thank you.
If I have understood well the output of "dctimestep" is:

Usage: dctimestep DCspec [tregvec]
   or: dctimestep Vspec Tbsdf.xml Dmat.dat [tregvec]

I am going to send you the gzip'ped Barcelona.smx by WeTransfer (Excuse me ziped file has 40MB).
Thank you very much in advance,
Urtza.

Greg Ward <[email protected]> escribió:

Hi Urtza,

Well, I don't see anything wrong with the headers, except for southest.dmx, which you say you corrected. In any case, the error you are seeing occurs before that file is even accessed by dctimestep, so it must be something else going wrong.

Can you e-mail me your gzip'ped Barcelona.smx file, so I can test it on my machine? Also, will you send me the output of "dctimestep" executed with no arguments on your machine? This will help me determine if you have the correct version.

Cheers,
-Greg

From: [email protected]
Subject: Re: [Radiance-general] sudo recontrib
Date: March 22, 2016 1:46:01 AM PDT

Dear Greg,
That are the output of getinfo:

photocells.vmx:
#?RADIANCE
oconv material.rad sc-vi3Mphase.rad window.rad
rcontrib -f /usr/share/radiance/klems_int.cal -b kbin(-sqrt(.5),sqrt(.5),0,0,0,1) -bn Nkbins -m windowglow -I+ -ab 2 -ad 1000 -lw 2e-5 -y 552
SOFTWARE= RADIANCE 5.0a (NREL build 5.0.a.2) lastmod Fri Apr 24 15:04:00 MDT 2015 by googs on lu040t-001
CAPDATE= 2016:03:21 10:54:51
GMT= 2016:03:21 09:54:51
NCOMP=3
NROWS=552
NCOLS=145
FORMAT=ascii

southest.dmx:
#?RADIANCE
oconv material.rad sc-vi3Mphase.rad sky_overcast.rad
rcontrib -c 1000 -e MF:4 -f reinhart.cal -b rbin -bn Nrbins -m sky_glow
SOFTWARE= RADIANCE 5.0a (NREL build 5.0.a.2) lastmod Fri Apr 24 15:04:00 MDT 2015 by googs on lu040t-001
CAPDATE= 2016:03:22 09:22:32
GMT= 2016:03:22 08:22:32
NCOMP=3
NCOLS=2306
FORMAT=ascii

Barcelona.smx:
#?RADIANCE
gendaymtx -m 4 Barcelona.wea
LATLONG= 41.28000000 2.07000000
NROWS=2306
NCOLS=8760
NCOMP=3
FORMAT=ascii

(In the southest.dmx I add NROWS=145 with test editor after. I have launched with that data but it scripts the same error)

And If I am understanding well, the output of dctimestep is this script (It does not script nothing more):
fatal - unexpected EOF reading Barcelona.smx

Thank you very much in advance.
Best regards,
Urtza.

Greg Ward <[email protected]> escribió:

Can you send the output of "getinfo" on your matrix files, i.e.:

getinfo photocells.vmx southest.dmx Barcelona.smx

Also, send the output of dctimestep executed with no arguments. (It should produce a usage message.)

Thanks,
-Greg

From: [email protected]
Subject: Re: [Radiance-general] sudo recontrib
Date: March 21, 2016 6:32:24 AM PDT

Yes, I have in View Matrix NROWS=552 and NCOLS=145 (I think that you have 6 sensor points, so 6x145).
Does it make sense? I think they are 145 Klems patches.

Best regards,
Urtza.

Humberto Antunes <[email protected]> escribió:

I have read more carefully you e-mail, do you have 552 sensor points? if yes your number of rows in the view matrix is 552 and not 145, try to change NROWS=552 in you view matrix.

Best regards
Humberto A.

2016-03-21 12:38 GMT+00:00 <[email protected]>:
Dear Humberto,

Yes, I am trying without "-n 8760" option, as follow:

dctimestep photocells.vmx Film3M_145x1297_9142012_t.xml southest.dmx Barcelona.smx
fatal - unexpected EOF reading Barcelona.smx

I do not know. Thank you,
Urtza.

Humberto Antunes <[email protected]> escribió:

Hi Urtza,

Are you running dctimestep with the "-n" option? If yes try to run it without it. use:

dctimestep view.mtx daylight.mtx transmision.xml sky.mtx

For me this solved the problem, no need for the "-n 8760" option.

Hope it helps.

Best regards
Humberto A.

2016-03-21 11:16 GMT+00:00 <[email protected]>:
Dear Andy and Greg,

(I am trying to follow Humberto's issue, as well)
I have added to View Matrix sensor points number (I notice that in Daylight Matrix I have not had NROWS data and I have added NROWS=145). To sum up I have; Sky Matrix, 2306x8760; Daylight Matrix, 145x2306; and View Matrix, 552x145. I launched dctimestep and it scripts the same error (fatal - unexpected EOF reading Barcelona.smx).

In case, I review the Sky Matrix with "wc" and I get almost the number that Greg suggested:

wc Barcelona.smx

20202874 60601692 213155298 Barcelona.smx

I do not know what is the problem with Sky Matrix (although it seems a little estrange 2306x8760 data are in rows).
Thank you in advance,
Urtza.

"Gregory J. Ward" <[email protected]> escribió:

Following this up on the general mailing list...

The problem was the one Andy pointed out earlier, where the newer version of dctimestep doesn't want the "-n" option when the sky matrix has a header.

Regarding the new question (appearing below), using rmtxop in this way is indeed the simplest means to convert RGB irradiance to illuminance in lux.

Cheers,
-Greg

From: Humberto Antunes <[email protected]>
Subject: Re: dctimesteps
Date: March 20, 2016 6:04:36 PM PDT

I tried to run the command like that and it worked just fine, i got the same results as you did.

I was running the dctimestep command with the -n 8760 option, but this is not needed because the sky matrix already contains that info in the header, running it like you solved the issue.

Now there is just one thing remaining, to convert the RGB values from illum.dat file to illuminance values can i use the command below or is there a better way?

rmtxop -c 47.435 119.93 11.635 results/illum.dat> results/illum_final.dat

Note:
179*0.265=47.436
179*0.670=119.93
179*0.065=11.635

Best regards
Humberto A.

2016-03-21 0:01 GMT+00:00 Gregory J. Ward <[email protected]>:
Thanks, Humberto. I ran the following command:

dctimestep photocells.vmx singleclear.xml south.dmx lisboa.smx > illum.dat

without complaint. I am attaching the result.

Are you sure you have a recent installation of dctimestep? What do you see when you run dctimestep with no arguments? You should get:

Usage: dctimestep [-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] DCspec [skyf]
   or: dctimestep [-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] Vspec Tbsdf Dmat.dat [skyf]

Cheers,
-Greg

From: Greg Ward <[email protected]>
Subject: Re: [Radiance-general] sudo recontrib
Date: March 20, 2016 2:47:23 PM PDT

Hi Humberto,

Actually, your header and ASCII data look OK. Although some tools would put all the columns together in one humungous line with 8760x3, white space has no meaning here and gendaymtx output has a newline for each column entry with an extra empty line between rows.

If you run the "wc" command on your file, you should get something like:

20202873 60601692 xxxxxxxxxxx lisboa.smx

I don't know what xxxxxxx will be, but some large number corresponding to the number of bytes in your file. The first two values may not be exactly this, but should be reasonably close. Otherwise, your file really is missing some data at the end.

If your numbers agree roughly with the above, please send me a gzip'ped copies of your lisboa.wea and the output (*.smx) file in a private e-mail and I will see if I can figure out what is going on.

Cheers,
-Greg

From: Humberto Antunes <[email protected]>
Subject: Re: [Radiance-general] sudo recontrib
Date: March 20, 2016 2:30:23 PM PDT

Hi Urtza and Andy,

I am having the same issue as you do Urtza, I have already checked the headers of my view matrix, daylight matrix and sky matrix, and that doesn't seem to be the problem, my view matrix is a 6X145, the daylight matrix a 145X2306, and finally, the sky matrix is a 2306X8760, and this info is on the headers of each.

I think the problem is in the sky matrix file itself, it's not being properly written.

Mine looks like this:
#?RADIANCE
gendaymtx -m 4 weather/lisboa.wea
LATLONG= 38.73000000 -9.15000000
NROWS=2306
NCOLS=8760
NCOMP=3
FORMAT=ascii

0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0.477 0.477 0.477
1.85 1.85 1.85
4.85 4.85 4.85
11.6 11.6 11.6
10.5 10.5 10.5
...

So it doesn't have the number of columns it should, i think that each row has the RGB value for one patch of one time step and it should have the RGB values for all time steps of one patch, is that it?

Best regards
Humberto A.

Dear Greg,
Thank you very much. I will install the latest Radiance version.
Best regards for you,
Urtza.

"Gregory J. Ward" <[email protected]> escribió:

Hi Urtza,
  
  You need not bother sending the gzip'ped file. You have an outdated
installation of dctimestep, and I believe this is your problem.
  
  I don't know which version you have, exactly, but you should go to the
NREL page and get the latest version of Radiance before working on this
further.
  
  Cheers,
  -Greg

FROM: [email protected]

   SUBJECT: Re: [Radiance-general] sudo recontrib

   DATE: March 22, 2016 9:36:46 AM PDT

  Dear Greg,
Thank you.
If I have understood well the output of "dctimestep" is:
  Usage: dctimestep DCspec [tregvec]
   or: dctimestep Vspec Tbsdf.xml Dmat.dat [tregvec]

I am going to send you the gzip'ped Barcelona.smx by WeTransfer (Excuse me
ziped file has 40MB).
Thank you very much in advance,
Urtza.

Greg Ward <[email protected]> escribió:

Hi Urtza,
  
  Well, I don't see anything wrong with the headers, except for
southest.dmx, which you say you corrected. In any case, the error you
are seeing occurs before that file is even accessed by dctimestep, so it
must be something else going wrong.
  
  Can you e-mail me your gzip'ped Barcelona.smx file, so I can test it
on my machine? Also, will you send me the output of "dctimestep"
executed with no arguments on your machine? This will help me determine
if you have the correct version.
  
  Cheers,
  -Greg

FROM: [email protected]

   SUBJECT: Re: [Radiance-general] sudo recontrib

   DATE: March 22, 2016 1:46:01 AM PDT

  Dear Greg,
That are the output of getinfo:
  photocells.vmx:
  #?RADIANCE
  oconv material.rad sc-vi3Mphase.rad window.rad
  rcontrib -f /usr/share/radiance/klems_int.cal -b
kbin(-sqrt(.5),sqrt(.5),0,0,0,1) -bn Nkbins -m windowglow -I+ -ab 2 -ad
1000 -lw 2e-5 -y 552
  SOFTWARE= RADIANCE 5.0a (NREL build 5.0.a.2) lastmod Fri Apr 24 15:04:00
MDT 2015 by googs on lu040t-001
  CAPDATE= 2016:03:21 10:54:51
  GMT= 2016:03:21 09:54:51
  NCOMP=3
  NROWS=552
  NCOLS=145
  FORMAT=ascii
  
  southest.dmx:
  #?RADIANCE
  oconv material.rad sc-vi3Mphase.rad sky_overcast.rad
  rcontrib -c 1000 -e MF:4 -f reinhart.cal -b rbin -bn Nrbins -m sky_glow
  SOFTWARE= RADIANCE 5.0a (NREL build 5.0.a.2) lastmod Fri Apr 24 15:04:00
MDT 2015 by googs on lu040t-001
  CAPDATE= 2016:03:22 09:22:32
  GMT= 2016:03:22 08:22:32
  NCOMP=3
  NCOLS=2306
  FORMAT=ascii
  
  Barcelona.smx:
  #?RADIANCE
  gendaymtx -m 4 Barcelona.wea
  LATLONG= 41.28000000 2.07000000
  NROWS=2306
  NCOLS=8760
  NCOMP=3
  FORMAT=ascii

(In the southest.dmx I add NROWS=145 with test editor after. I have
launched with that data but it scripts the same error)

And If I am understanding well, the output of dctimestep is this script (It
does not script nothing more):
fatal - unexpected EOF reading Barcelona.smx

Thank you very much in advance.
Best regards,
Urtza.

Greg Ward <[email protected]> escribió:

Can you send the output of "getinfo" on your matrix files, i.e.:
  
  getinfo photocells.vmx southest.dmx Barcelona.smx
  
  Also, send the output of dctimestep executed with no arguments. (It
should produce a usage message.)

  Thanks,
  -Greg

FROM: [email protected]

    SUBJECT: Re: [Radiance-general] sudo recontrib

    DATE: March 21, 2016 6:32:24 AM PDT

    

  Yes, I have in View Matrix NROWS=552 and NCOLS=145 (I think that you have
6 sensor points, so 6x145).
Does it make sense? I think they are 145 Klems patches.

Best regards,
Urtza.

Humberto Antunes <[email protected]> escribió:

I have read more carefully you e-mail, do you have 552 sensor points? if
yes your number of rows in the view matrix is 552 and not 145, try to
change NROWS=552 in you view matrix.
   Best regards
   Humberto A.

_Dear Humberto,

Yes, I am trying without "-n 8760" option, as follow:

dctimestep photocells.vmx Film3M_145x1297_9142012_t.xml southest.dmx
Barcelona.smx
fatal - unexpected EOF reading Barcelona.smx

I do not know. Thank you,
Urtza.

Humberto Antunes <[email protected]> escribió:_

_Hi Urtza,_ _ _
          _Are you running dctimestep with the "-n" option? If yes try
to run it without it. use:_
          _ _
          _dctimestep view.mtx daylight.mtx transmision.xml sky.mtx_
          _ _
          _For me this solved the problem, no need for the "-n 8760"
option._
          _ _
          _Hope it helps._
          _ _
          _Best regards_
          _Humberto A._

          _2016-03-21 11:16 GMT+00:00 <[email protected]>:_

__Dear Andy and Greg,

(I am trying to follow Humberto's issue, as well)
I have added to View Matrix sensor points number (I notice that in
Daylight Matrix I have not had NROWS data and I have added
NROWS=145). To sum up I have; Sky Matrix, 2306x8760; Daylight Matrix,
145x2306; and View Matrix, 552x145. I launched dctimestep and it
scripts the same error (fatal - unexpected EOF reading Barcelona.smx).

In case, I review the Sky Matrix with "wc" and I get almost the
number that Greg suggested:

wc Barcelona.smx

20202874 60601692 213155298 Barcelona.smx

I do not know what is the problem with Sky Matrix (although it seems
a little estrange 2306x8760 data are in rows).
Thank you in advance,
Urtza.

"Gregory J. Ward" <[email protected]> escribió:__

__Following this up on the general mailing list...__
                __ __
                __The problem was the one Andy pointed out earlier,
where the newer version of dctimestep doesn't want the "-n" option
when the sky matrix has a header.__
                __ __
                __Regarding the new question (appearing below),
using rmtxop in this way is indeed the simplest means to convert RGB
irradiance to illuminance in lux.__
                __ __
                __Cheers,__
                __-Greg__

__FROM: Humberto Antunes <[email protected]>__
                  __SUBJECT: Re: dctimesteps__
                  __DATE: March 20, 2016 6:04:36 PM PDT__
                  __ __

__I tried to run the command like that and it worked just fine, i
got the same results as you did.__
   __ __
                   __I was running the dctimestep command with the
-n 8760 option, but this is not needed because the sky matrix
already contains that info in the header, running it like you
solved the issue.__
                   __ __
                   __Now there is just one thing remaining, to
convert the RGB values from illum.dat file to illuminance values
can i use the command below or is there a better way?__
                   __ __
                   __rmtxop -c 47.435 119.93 11.635
results/illum.dat> results/illum_final.dat__
                   __ __
                   __Note:__
                   __179*0.265=47.436__
                   __179*0.670=119.93__
                   __179*0.065=11.635__
                   __ __
                   __Best regards__
                   __Humberto A.__

                   __2016-03-21 0:01 GMT+00:00 Gregory J.
Ward <[email protected]>:__

__Thanks, Humberto. I ran the following command:__
                      __ __
                      __dctimestep photocells.vmx singleclear.xml
south.dmx lisboa.smx > illum.dat__
                      __ __
                      __without complaint. I am attaching the
result.__
                      __ __
                      __Are you sure you have a recent
installation of dctimestep? What do you see when you run
dctimestep with no arguments? You should get:__
                      __ __
                                             __Usage: dctimestep
[-n nsteps][-o ospec][-i{f|d|h}][-o{f|d}] DCspec [skyf]__
                       __ or: dctimestep [-n nsteps][-o
ospec][-i{f|d|h}][-o{f|d}] Vspec Tbsdf Dmat.dat [skyf]__

                      __ __
                      __Cheers,__
                      __-Greg__
                      __ __

__FROM: Greg Ward <[email protected]>__

                 __SUBJECT: Re: [Radiance-general] sudo recontrib__

                 __DATE: March 20, 2016 2:47:23 PM PDT__

                 __ __

__Hi Humberto,__
                 __ __
                 __Actually, your header and ASCII data look OK.
Although some tools would put all the columns together in one
humungous line with 8760x3, white space has no meaning here and
gendaymtx output has a newline for each column entry with an extra
empty line between rows.__
                 __ __
                 __If you run the "wc" command on your file, you
should get something like:__
                 __ __
                 __20202873 60601692 xxxxxxxxxxx lisboa.smx__
                 __ __
                 __I don't know what xxxxxxx will be, but some
large number corresponding to the number of bytes in your file.
The first two values may not be exactly this, but should be
reasonably close. Otherwise, your file really is missing some data
at the end.__
                 __ __
                 __If your numbers agree roughly with the above,
please send me a gzip'ped copies of your lisboa.wea and the output
(*.smx) file in a private e-mail and I will see if I can figure out
what is going on.__
                 __ __
                 __Cheers,__
                 __-Greg__

__FROM: Humberto Antunes <[email protected]>__

                  __SUBJECT: Re: [Radiance-general] sudo

recontrib__

···

   2016-03-21 12:38 GMT+00:00 <[email protected]>:

                  __DATE: March 20, 2016 2:30:23 PM PDT__

                  __ __

__Hi Urtza and Andy,__ __ __
                   __I am having the same issue as you do Urtza, I
have already checked the headers of my view matrix, daylight
matrix and sky matrix, and that doesn't seem to be the problem, my
view matrix is a 6X145, the daylight matrix a 145X2306, and
finally, the sky matrix is a 2306X8760, and this info is on the
headers of each.__
                   __ __
                   __I think the problem is in the sky matrix file
itself, it's not being properly written.__
                   __ __
                   __Mine looks like this:__
                                       __#?RADIANCE__
                    __gendaymtx -m 4 weather/lisboa.wea__
                    __LATLONG= 38.73000000 -9.15000000__
                    __NROWS=2306__
                    __NCOLS=8760__
                    __NCOMP=3__
                    __FORMAT=ascii__
                    __ __
                    __0 0 0__
                    __0.477 0.477 0.477__
                    __1.85 1.85 1.85__
                    __4.85 4.85 4.85__
                    __11.6 11.6 11.6__
                    __10.5 10.5 10.5__

                   __...__
                   __ __
                   __So it doesn't have the number of columns it
should, i think that each row has the RGB value for one patch of
one time step and it should have the RGB values for all time steps
of one patch, is that it?__
                   __ __
                   __Best regards__
                   __Humberto A.__