Using own weather files in PAT tool

asked 2019-12-26 14:43:37 -0500

y.tanaka
213 ●1 ●6

I would like to run PAT tool analysis on project_singlefamilydetached using TMY2 and TMY weather files for one region only (Alpena, Michigan).

Going through the tutorial on the ResStock "readthedocs", I have done the following:

Downloaded and zipped both the .ddy and .epw file of the TMY2 weather data for the area I want. The zipped folder is located on my machine, NOT in an S3 bucket, called USA_MI_Alpena.726390_TMY2. The two files contained are:

a. USA_MI_Alpena.County.Rgnl.AP.726390_TMY2.ddy

b. USA_MI_Alpena.County.Rgnl.AP.726390_TMY2.epw

The contents are shown: image description

Changed the following cells in the "Location Weather Filename" and "Location Weather Year" tsv files:

Location Weather Filename image description

Location Weather Year image description

Changed the Worker Initialization Script argument to the absolute path of my zipped folder containing my desired weather files.

image description

Despite the above changes, running the analysis ultimately results in datapoint failure. I compared the log files for building ID:1, one after running PAT tool with my own weather files, and one after running PAT tool with the default weather files (i.e. using project_national_resstock, referencing from the S3 bucket, etc.). I've observed the error occurs approximately here:

image description

The error states as follows:

Cannot find file /mnt/openstudio/analysis_3d4139f0-c511-41b9-9d2a-3c729da19d05/lib/housing_characteristics/buildstock.csv.

What am I doing incorrectly in this process of using my own weather files? Do I have to reference an S3 bucket in PAT tool since I'm using AWS to run simulations?

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2019-12-26 14:49:32 -0500

Eric Wilson

1853 ●12 ●8 https://resstock.nrel.gov/

I believe you need to upload the weather file zip somewhere (dropbox, google drive, etc.) and paste the url in that Script Arguments field (it can't be a local drive location).

edit flag offensive delete link

Comments

Thank you! Yes, uploading the zipped weather files into Dropbox, and using the download link to the respective files, seemed to do the trick for me. However, I needed to relabel the corresponding TMY2 and TMY files as if they were TMY3, otherwise, PAT tool would not work.

y.tanaka ( 2020-01-10 13:23:23 -0500 )edit

Hello all, I tried following the instructions in this question and I am using one drive currently to host the weather zip file I obtained. The weather zip file being used is "Buildstock_TMY3_FIPS.zip" from an NREL website. However I see the error below whenever I run the PAT resstock on AWS (In the following comment):

Vishak ( 2021-03-28 06:48:39 -0500 )edit

[04:59:02.827408 DEBUG] Script returned with exit code 1 of class Fixnum [04:59:02.827593 ERROR] Script /mnt/openstudio/analysis_ed8fe1b8-0495-4396-b2de-eb537a9e1f5e/scripts/data_point/initialize.sh resulted in error Script file /mnt/openstudio/analysis_ed8fe1b8-0495-4396-b2de-eb537a9e1f5e/scripts/data_point/initialize.sh returned with non-zero exit code. See /mnt/openstudio/analysis_ed8fe1b8-0495-4396-b2de-eb537a9e1f5e/data_point_7741ed2f-d9e3-4aa0-8150-cda22e86a1a4/initialize.log (Next Comment)

Vishak ( 2021-03-28 06:49:14 -0500 )edit

My link to the host weather zip file looks similar to: https://my.sharepoint.com/:u:/r/perso... It does not end in "TMY3.zip" as in the example. Is that the problem?

Vishak ( 2021-03-28 06:49:23 -0500 )edit

One possibility is that the server where the simulations are running cannot access that URL. The other is that there was a bugfix to allow URLs that use redirects to work, which you might not have depending on which version of resstock you're using.

shorowit ( 2021-03-28 10:54:21 -0500 )edit

see more comments

answered 2020-01-10 13:26:22 -0500

y.tanaka
213 ●1 ●6

Using weather file zip locally will not work (i.e. from your own machine). What I found worked was taking the desired zipped weather files, uploading them into Dropbox/Google Drive, then using the download link to those respective files into the Script Argument section for Worker Initialization Script.

However, I made sure to relabel the TMY2/TMY zipped file as if they were TMY3. And I changed the location-weather-filename and location-weather-year back to default. For some reason, it won't work otherwise. To sum it up, I was still able to use different weather files, but they're just labeled as if they were TMY3.