Try changing line 74 in epw2wea.c from:
fprintf(WEA_FILE,"time_zone %.0f\n",-15.0*atoi(time_zone));
to:
fprintf(WEA_FILE,"time_zone %.0f\n",-15.0*atof(time_zone));
Does this fix the problem?
-Greg
> From: "Guglielmetti, Robert" <[email protected]>
> Date: December 16, 2013 1:56:58 PM PST
>
> Yeah, we have our contract engineer to thank for that; we needed the epw2wea
> functionality in OpenStudio -- for all platforms -- and he made it happen.
> Christoph was nice enough to share it in the Radiance trunk a few months ago,
> so yeah there it is. I would prefer to keep the c version too, the thing is I
> don't know how to implement your meridian fix either. I can ask our
> contractor how much of a deal it would be for him to implement it, using your
> perl version as a template.
>
> -----Original Message-----
> From: Axel Jacobs [mailto:[email protected]]
> Sent: Monday, December 16, 2013 12:48 PM
> To: code development
> Subject: Re: [Radiance-dev] epw2wea in Perl
>
> Hi Rob,
>
> I've just downloaded the latest HEAD, and found that there is now an
> epw2wea.c Well done. When did this happen? This kinda makes my Perl version
> superfluous. Might be better to fix the meridian bug (time zones that are not
> offset from GMT by a full hour), and forget about the CSV output. I'ts
> probably trivial to implement, but my C coding skills are non-existent.
>
> Best
>
> Axel
>
>
> On 16 December 2013 18:59, Guglielmetti, Robert
> <[email protected]> wrote:
>> --------
>> WARNING: At least one of the links in the message below goes to an
>> .exe file, which could be malicious. To learn how to protect yourself,
>> please go here:
>> https://commons.lbl.gov/x/_591B
>> --------
>>
>> Hi Axel,
>>
>> Epw2wea was forked from the Daysim project and with Christoph Reinhart's
>> consent was added -- along with proper changes to make and CMake build files
>> -- to the Radiance cvs. NREL did this because with the addition of
>> gendaymtx, and its expected weather data input format, we felt it was almost
>> a necessity for the general Radiance user. If a user grabs any of the NREL
>> packages, or builds Radiance from source using the makeall script or
>> standard tools, they will have a copy of epw2wea(.exe) in their Radiance
>> build.
>>
>> I considered it a bonus that this util was now available to all users, and
>> that it was deployed as a c program and not another script. On the other
>> hand, your additions make epw2wea even more useful and I think it makes
>> sense to replace epw2wea.c with epw2wea.pl. My free opinion. Worth every
>> penny.
>>
>> Should we go this route, we'd need an update for the skeletal manpage.
>>
>> - Rob
>>
>> -----Original Message-----
>> From: Axel Jacobs [mailto:[email protected]]
>> Sent: Sunday, December 15, 2013 4:26 PM
>> To: [email protected]
>> Subject: [Radiance-dev] epw2wea in Perl
>>
>> --------
>> WARNING: At least one of the links in the message below goes to an .exe
>> file, which could be malicious. To learn how to protect yourself, please go
>> here:
>> https://commons.lbl.gov/x/_591B
>> --------
>>
>> Dear devs,
>>
>> I have put up a work-in-progress version of epw2wea:
>>
>> http://www.jaloxa.eu/pickup/epw2wea.exe
>> http://www.jaloxa.eu/pickup/epw2wea.pl
>>
>> The output is almost identical to the Windows version of epw2wea.exe. I am
>> not entirely sure where this is from, but it is in the NREL version of
>> Radiance for Windows.
>>
>> There are three minor differences to the original Windows version:
>>
>> a) there is a -c (as in 'CSV') option that simply dumps the entire file as a
>> text spreadsheet with header. The delimiter defaults to ' '
>> (space), but can selected with the -d option. Please note that if you wish
>> to have a tab-sep output, then '\t' won't do. Still working out how to do
>> this. For now, you'll need to give it -c 'CTRL-v TAB' to actually insert a
>> tab on the command line.
>>
>> I would like to think that a CSV dump of the EPW weather data will make it a
>> little easier to do a bit of QA on the data. Hence this extra option.
>>
>> b) the 'meridian' bug of the original epw2wea is fixed. Places such as Delhi
>> (GMT + 5:30 hrs) or Kathmandu (GMT +5:45 hrs) are correctly represented in
>> the time_zone row of the wea header.
>>
>> c) input can be from STDIN
>>
>> epw2wea.pl is tested on LINUX and Windows Vista.
>>
>> Any feedback is very much appreciated. Particularly, I'd love to know your
>> preferred naming convention for the columns in the CSV output. The radiation
>> stuff tends to follow CIE conventions. For instance, global horizontal
>> irradiance is headed as Eeg. I kinda improvised with others, but tended to
>> be rather verbose with those column headers that I would consider a little
>> obscure, for the simple reason that I don't tend to use them. Please do get
>> in touch if there are any other de-facto naming convention that should be
>> adapted.
>>
>> dev site:
>> http://www.jaloxa.eu/devel/csh2perl/
>>
>> Good night to you all
>>
>> Axel
_______________________________________________
Radiance-dev mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-dev
