Revision history [back]

I've never looked into nor have need of the DLL, but these two functions do sound like the batch processing way of running the weather converter which is the only way I use the program because I'm working with thousands of weather files. I believe this feature is minimally described in the documentation as processing by List where you create an ASCII *.lst file with two columns giving the input and output file names, like this:

AB_CALGARY-IAP_718770_17.CSV AB_CALGARY-IAP_718770_17.epw AB_COLD-LAKE_711200_17.CSV AB_COLD-LAKE_711200_17.epw AB_EDMONTON-IAP_711230_17.CSV AB_EDMONTON-IAP_711230_17.epw AB_EDMONTON-NAMAO-AP_711210_17.CSV AB_EDMONTON-NAMAO-AP_711210_17.epw ...

Then, when you run the WeatherConverter, just enter the name of this *.lst file to run. Caution: if the input files are of a format that the converter does not recognize (like what 's in the sample list above), WeatherConverter will expect a *.def definition file for each file.

enter code hereI've never looked into nor have need of the DLL, but these two functions do sound like the batch processing way of running the weather converter which is the only way I use the program because I'm working with thousands of weather files. I believe this feature is minimally described in the documentation as processing by List where you create an ASCII *.lst file with two columns giving the input and output file names, like this:

AB_CALGARY-IAP_718770_17.CSV                     AB_CALGARY-IAP_718770_17.epw
AB_COLD-LAKE_711200_17.CSV                       AB_COLD-LAKE_711200_17.epw
AB_EDMONTON-IAP_711230_17.CSV                    AB_EDMONTON-IAP_711230_17.epw
AB_EDMONTON-NAMAO-AP_711210_17.CSV               AB_EDMONTON-NAMAO-AP_711210_17.epw
...
...

enter code hereI've never looked into nor have need of the DLL, but these two functions do sound like the batch processing way of running the weather converter which is the only way I use the program because I'm working with thousands of weather files. I believe this feature is minimally described in the documentation as processing by List where you create an ASCII *.lst file with two columns giving the input and output file names, like this:

AB_CALGARY-IAP_718770_17.CSV                     AB_CALGARY-IAP_718770_17.epw
AB_COLD-LAKE_711200_17.CSV                       AB_COLD-LAKE_711200_17.epw
AB_EDMONTON-IAP_711230_17.CSV                    AB_EDMONTON-IAP_711230_17.epw
AB_EDMONTON-NAMAO-AP_711210_17.CSV               AB_EDMONTON-NAMAO-AP_711210_17.epw
...

Then, when you run the WeatherConverter, just enter the name of this *.lst file to run. Caution: if the input files are of a format that the converter does not recognize (like what 's in the sample list above), WeatherConverter will expect a *.def definition file for each file.

enter code hereI've never looked into nor have need of the DLL, but these two functions do sound like the batch processing way of running the weather converter which is the only way I use the program because I'm working with thousands of weather files. I believe this feature is minimally described in the documentation as processing by List where you create an ASCII *.lst file with two columns giving the input and output file names, like this:

AB_CALGARY-IAP_718770_17.CSV                     AB_CALGARY-IAP_718770_17.epw
AB_COLD-LAKE_711200_17.CSV                       AB_COLD-LAKE_711200_17.epw
AB_EDMONTON-IAP_711230_17.CSV                    AB_EDMONTON-IAP_711230_17.epw
AB_EDMONTON-NAMAO-AP_711210_17.CSV               AB_EDMONTON-NAMAO-AP_711210_17.epw
...

Then, when you run the WeatherConverter, just enter the name of this *.lst file to run. Caution: if the input files are of a format that the converter does not recognize (like what 's in the sample list above), WeatherConverter will expect a *.def definition file for each file.