Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
PAT has always had to start up the local sever which takes time, however there was a recent change that altered this behavior. It used to start up the server when you launched PAT, and then the server was waiting for you, assuming you worked on the project for 5 or so minutes before you ran. This change was made because many users are using cloud sources more, and by not having the server start you can quickly open and close different PAT projects.
When you click run on an analysis, and have "Run Locally" selected PAT will start a server if there isn't already one running. If you know you will are going to run locally, you can mimic the hold behavior and start the server right after you create or load a PAT project. Open the "Server Tools" dialog under the "Window" menu and then click "Start Local Server". You can continue to work on your project while this happens, and then when you are ready to click run, assuming the server has finished starting, it will a quick run like your subsequent runs.
| | 2 | No.2 Revision |
PAT has always had to start up the local sever which takes time, however there was a recent change that altered this behavior. It used to start up the server when you launched PAT, and then the server was waiting for you, assuming you worked on the project for 5 or so minutes before you ran. This change was made because many users are using cloud sources more, and by not having the server start you can quickly open and close different PAT projects.
When you click run on an analysis, and have "Run Locally" selected PAT will start a server if there isn't already one running. If you know you will are going to run locally, you can mimic the hold behavior and start the server right after you create or load a PAT project. Open the "Server Tools" Server Tools dialog under the "Window" menu and then click "Start Start Local Server". Server. You can continue to work on your project while this happens, and then when you are ready to click run, assuming the server has finished starting, it will a quick run like your subsequent runs.
| | 3 | No.3 Revision |
PAT has always had to start up the local sever which takes time, however there was a recent change that altered this behavior. It used to start up the server when you launched PAT, and then the server was waiting for you, assuming you worked on the project for 5 or so minutes before you ran. This Now it doesn't start automatically, this change was made because many users are using cloud sources more, and by not having the server start you can quickly open and close different PAT projects.
When you click run on an analysis, and have "Run Locally" selected PAT will start a server if there isn't already one running. If you know you will are going to run locally, you can mimic the hold behavior and start the server right after you create or load a PAT project. Open the Server Tools dialog under the "Window" menu and then click Start Local Server. You can continue to work on your project while this happens, and then when you are ready to click run, assuming the server has finished starting, it will a quick run like your subsequent runs.
