Hi Devon, Most Unix programs (Radiance tools included) treat tabs and spaces the same on input.
There is a new program called rcollate that allows you to change the record length for any input, i.e. change where newlines are placed. What is the problem you are trying to resolve, exactly? -Greg > From: Devon Sparks <devon.spa...@arup.com> > Subject: [Radiance-dev] Radiance ASCII format specification > Date: April 7, 2014 5:20:15 PM PDT > > Does Radiance specify[1] a standard ASCII format for RGB output? I've > observed two "defaults": > > * rtrace, rcalc - RGB fields separated by tabs. Sensor records separated by > newlines. > $ vwrays -vf myview.vf | head -n 1 | rtrace -ab 0 -h model.oct > $ 0.000000e+00<TAB>0.000000e+00<TAB>0.000000e+00<TAB><CR> > > * dctimestep - RGB fields separated by spaces. Time-series records separated > by tabs. Sensor records separated by newlines. > $ gendaymtx -m 4 city.wea | dctimestep -n 8760 model.dc | head -n 1 > $ > 0.000000e+00<SP>0.000000e+00<SP>0.000000e+00<TAB>0.000000e+00<SP>0.000000e+00<SP>0.000000e+00<TAB>... > > Is there any reason to think that these two format specifications should be > unified in the standard distribution (e.g. fields separated by spaces, > time-based records separated by tabs, spatial records separated by newlines)? > How many tools would be broken in the process? > > Thanks in advance — Devon > > [1] http://radsite.lbl.gov/radiance/refer/filefmts.pdf > > Devon Sparks > Consultant | Lighting Group > > Arup > 560 Mission Street Seventh Floor San Francisco CA 94105 United States > t +1 415 957 9445 d +1 415 946 0240 > f +1 415 957 9096
_______________________________________________ Radiance-dev mailing list Radiance-dev@radiance-online.org http://www.radiance-online.org/mailman/listinfo/radiance-dev
