firstly, thank you so much for your help! Iv been working on that for a
while now and that really moved me forwards..
Just one more quick question, the .dat file I get outputs just a list
of lux levels, how do you export this into a tst file? or at least
seperate the values by a comma as then I could import it into excel..as
when i just change the file name to txt the list of numbers converts to
just a long string of numbers which aren't separated in any way..
Thank you in advance!
Sasa.
Can you please be more specific about your problem?
In which context are you creating these *.dat files, which application
are you using and what is the command you use to create the files (if
you know that).
If the *.dat files contain only a single value per line (lux level)
then there should be another file that contains coordinates. Usually
this has the form "x y z dx dy dz" (no comma!). Excel can import these
files even if there is no comma in the line. You just have to set the
field separator correctly.
Regards,
Thomas
On Tue, Feb 16, 2010 at 10:36 AM, [email protected] <[email protected]> wrote:
firstly, thank you so much for your help! Iv been working on that for a
while now and that really moved me forwards..Just one more quick question, the .dat file I get outputs just a list
of lux levels, how do you export this into a tst file? or at least
seperate the values by a comma as then I could import it into excel..as
when i just change the file name to txt the list of numbers converts to
just a long string of numbers which aren't separated in any way..Thank you in advance!
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
I usually find that for some reason if you assign the *.dat files to open with Excel, they open correctly without changing the extension (tabs are interpreted as column breaks). On the other hand, if you change the extension to .txt and force it to open with Excel, it doesn't do the formatting as you'd like it. For correct display of the text files in Excel 2007 try the Data menu tab, Text To Columns function. I forget what it's called in Excel 2003 and older, but I believe still in the data menu.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected]
Sent: Tuesday, February 16, 2010 5:37 AM
To: [email protected]
Subject: [Radiance-general] thank you!
firstly, thank you so much for your help! Iv been working on that for a while now and that really moved me forwards..
Just one more quick question, the .dat file I get outputs just a list of lux levels, how do you export this into a tst file? or at least seperate the values by a comma as then I could import it into excel..as when i just change the file name to txt the list of numbers converts to just a long string of numbers which aren't separated in any way..
Thank you in advance!
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
____________________________________________________________
Electronic mail messages entering and leaving Arup business
systems are scanned for acceptability of content and viruses
Thank you! thats very helpful..
From: [email protected]
Date: 16/02/2010 15:00
To: "Radiance general discussion"<radiance-general@radiance-online.Subj: RE: [Radiance-general] thank you!
I usually find that for some reason if you assign the *.dat files to
open with Excel, they open correctly without changing the extension
(tabs are interpreted as column breaks). On the other hand, if you
change the extension to .txt and force it to open with Excel, it
doesn't do the formatting as you'd like it. For correct display of the
text files in Excel 2007 try the Data menu tab, Text To Columns
function. I forget what it's called in Excel 2003 and older, but I
believe still in the data menu.
From: [email protected] [mailto:radiance-
[email protected]] On Behalf Of sasa.cemesova@tiscali.
co.uk
Sent: Tuesday, February 16, 2010 5:37 AM
To: [email protected]
Subject: [Radiance-general] thank you!firstly, thank you so much for your help! Iv been working on that for
a while now and that really moved me forwards..
Just one more quick question, the .dat file I get outputs just a list
of lux levels, how do you export this into a tst file? or at least
seperate the values by a comma as then I could import it into excel..as
when i just change the file name to txt the list of numbers converts to
just a long string of numbers which aren't separated in any way..
----Original Message----
-----Original Message-----Thank you in advance!
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
____________________________________________________________
Electronic mail messages entering and leaving Arup business
systems are scanned for acceptability of content and viruses
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
You can simply use the first bit of the command to generate the x,y,z file:
cnt 20 20 | rcalc -e '$1=1.3+0.470*$1;$2=1.300+0.470*$2;$3=1;' > coords.dat
Then use coords.dat and output.dat separately.
Alternatively, change the command so it writes the coords into the
output.dat file:
cnt 20 20 | rcalc -e '$1=1.3+0.470*$1;$2=1.300+0.
470*$2;$3=1;$4=0;$5=0;$6=1'\
rtrace -I -h -oov -ab 2 phfinalwithshelf.oct\
rcalc -e '$1=$1;$2=$2;$3=$3;$4=179*(.265*$4+.670*$5+.065*$6)'>output.dat
Mind the additional "-oov" and the use of $1 through $6.
The "output.dat" file will not contain "x y z lux" per line with tabs
between them. Excel should not have a problem with that.
Regards,
Thomas
That obviously should read "... will now contain ..."
Cheers,
Thomas
On Tue, Feb 16, 2010 at 5:00 PM, Thomas Bleicher <[email protected]> wrote:
The "output.dat" file will not contain "x y z lux" per line with tabs
between them. Excel should not have a problem with that.