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