-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PAT RUNS FOR EVER #252
Comments
From @DavidGoldwasser on July 26, 2017 19:42 @tabuimara What is the status in the green bar? Does it show "Analysis Started" or is it something else? Also have you seen this on multiple PAT projects and does it still happen after a fresh restart of your computer. |
From @tabuimara on July 26, 2017 19:43 Hi Tareq Isamil Abuimara, MSc, MRAIC From: David Goldwasser [mailto:[email protected]] @tabuimarahttps://github.com/tabuimara What is the status in the green bar? Does it show "Analysis Started" or is it something else? Also have you seen this on multiple PAT projects and does it still happen after a fresh restart of your computer. — |
From @DavidGoldwasser on July 26, 2017 20:37 Assuming you are running on local machine, what do you see at http://localhost:8080/ Do you see an analysis, and does that analysis seem to have any datapoints, and in the GUI on the Run tab under the row for each Datapoint is the status "Started" for at least some of the datapoints? |
From @tabuimara on July 27, 2017 14:38 Hi David Tareq Isamil Abuimara, MSc, MRAIC From: David Goldwasser [mailto:[email protected]] Assuming you are running on local machine, what do you see at http://localhost:8080/ Do you see an analysis, and does that analysis seem to have any datapoints, and in the GUI on the Run tab under the row for each Datapoint is the status "Started" for at least some of the datapoints? — |
From @DavidGoldwasser on July 27, 2017 16:39 Sorry, I have a few more questions. What operating system are you on, and if you restart your machine, make a fresh PAT project (something really basic without all of the same measures) does it run? If it is unique to a specific project might have you send it to us at [email protected]. |
From @tabuimara on July 27, 2017 16:43 Thanks for your response
Tareq Isamil Abuimara, MSc, MRAIC From: David Goldwasser [mailto:[email protected]] Sorry, I have a few more questions. What operating system are you on, and if you restart your machine, make a fresh PAT project (something really basic without all of the same measures) does it run? If it is unique to a specific project might have you send it to us at [email protected]mailto:[email protected]. — |
From @DavidGoldwasser on July 28, 2017 16:15 @tabulimara. I got your email, and saw that now, you are not getting it running forever, but the datapoints are failing. The behavior appears to be related to issue #2557 which is closed and should be fixed, so I'm not sure why you are seeing it. If you are using a PAT project that pre-dates the fix, then I can see this happening. It sounds like this project could have bene made in 2.1.0 which didn't have the fix) I'm seeing this error
That appears to come from the Add Overhang by Projection Factor measure
I just got this information out of the run.log by unizpping one of the data_point.zip files in the localResults folder. I haven't had a chance to run the project here, but What I would try is to remove the measure from the workflow (using the PAT application), save PAT, then re-add the measure, and see if this goes away. You can also just pick an opaque construction for the shading surfaces to see if that resolves the issue. You may hit similar issue in other measures for example the optional plenum zones. If I get a chance I'll try this approach on your project, but if you have a chance you may want to try it first. |
From @tabuimara on July 31, 2017 20:23 Hi David Tareq I. A. Abuimara From: David Goldwasser [email protected] @tabulimara. I got your email, and saw that now, you are not getting it running forever, but the datapoints are failing. The behavior appears to be related to issue #2557NREL/OpenStudio#2557 which is closed and should be fixed, so I'm not sure why you are seeing it. If you are using a PAT project that pre-dates the fix, then I can see this happening. I'm seeing this error
[11:52:14.211511 ERROR] C:/openstudio-2.2.0/pat/OpenStudio-server/gems/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb failed with message Error assigning argument in measure C:/openstudio-2.2.0/pat/OpenStudio-server/gems/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb. Failed with Could not set argument 'construction' to value '', C:/openstudio-2.2.0/pat/OpenStudio-server/gems/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:186:in `apply_arguments_2' That appears to come from the Add Overhang by Projection Factor measure
I just got this information out of the run.log by unizpping one of the data_point.zip files in the localResults folder. I haven't had a chance to run the project here, but What I would try is to remove the measure from the workflow. Save PAT, then re-add the measure back, and see if this goes away. You can also just pick an opaque construction for the shading surfaces to see if that resolves the issue. You may hit similar issue in other measures for example the optional plenum zones. If I get a chance I'll try this approach on your project, but if you have a chance you may want to try it first. — {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/NREL/OpenStudio","title":"NREL/OpenStudio","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/NREL/OpenStudio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@DavidGoldwasser in #2701: @tabulimara. I got your email, and saw that now, you are not getting it running forever, but the datapoints are failing. The behavior appears to be related to issue #2557 which is closed and should be fixed, so I'm not sure why you are seeing it. If you are using a PAT project that pre-dates the fix, then I can see this happening. \r\n\r\nI'm seeing this error\r\n |
From @asparke2 on August 22, 2017 16:43 @chrisbalbach reported this issue, demonstrated it, and I have a PAT project that replicates the issue (on Windows at least). Basically what's happening is that one of the design alternatives is getting re-run over and over again and never completes, even though the simulation finishes and everything. |
From @mbcoalson on August 30, 2017 14:57 I seem to be having a similar issue. I had difficulty getting PAT to run locally, so I uninstalled and reinstalled it directly in the C-drive. Changing where I have PAT installed has allowed me to connect to the local-virtual server. Unfortunately, I am receiving a datapoint failure status message on all my simulations, even as I have progressively simplified them (as is talked about in this thread). I'm running Windows 10, on a 64bit system. Here is the zip file associated with my most recent simulation. Any thoughts are greatly appreciated. |
From @asparke2 on September 16, 2017 22:46 We believe that this issue is the result of having some reserved characters (periods, dollar signs) in the measure option and/or design alternative names. This hypothesis is being tested and if it is true we will add GUI logic into PAT to warn users ahead of time. The better long term solution to allow these characters in the names may be pursued in the future. |
Chris B. was able to reproduce this problem with arguments keys that contain periods (90.1). |
The behavior gets funky starting with an exception here |
I was able to resolve the issue for specific project by updating the measure to cleans names used similar to how runner.registerValues from model objects are cleansed in reporting measures. Arguments didn't cleanly update in PAT without deleting and re-adding the measure. I first tried changing the model used for arguments, and then changing it back. Seems like an easy fix could be to update PAT to catch this in pre-flight similar to periods in design alternative names. |
From @tabuimara on July 26, 2017 15:22
SINCE I UPDATED OPEN-STUDIO to 2.2.0, I am not able to perform any parametric analysis , the process starts and keeps in progress forever . I thought might be an issue with one of the weather files , so i tested them one at a time , nothing changes !
Copied from original issue: NREL/OpenStudio#2701
The text was updated successfully, but these errors were encountered: