BrianLBall's profile - activity

https://github.com/NREL/OpenStudio-PAT/issues/283

PAT 3.9.1 has been released with a fix for this startup issue here

PAT 3.9.1 has been released with a fix for this issue here

3.8.0 and 3.9.0 had errors in them during the conversion from Ruby 2.7 to Ruby 3.2. We have taken them down. We've ident

While cloud computing capabilities have grown, its gotten less turn key. For now, users are expected to use the helm re

3.8.0 and 3.9.0 had errors in them during the conversion from Ruby 2.7 to Ruby 3.2. We have taken them down. We've ident

3.8.0 and 3.9.0 had errors in them during the conversion from Ruby 2.7 to Ruby 3.2. We have taken them down. We've ident

That console has log messages for the PAT application itself. What you want is the actual datapoint simulation logs, si

We can replicate the issue and are working on a fix.

Can you try with 3.7.0? There are issues with 3.8.0 that we are working on fixing.

you can manually run the command that PAT uses to start the local server by copying the command thats displayed after th

hm, no logs in those directories is concerning and certainly makes things difficult to debug. There is the developer co

just saw the EDIT2 comments. The error is [2024-05-13T15:06:05.565994 #8212] ERROR -- : Mongod failed to launch. Please

This is also in the EDIT2 output System call will be: 'mongod.exe --port 27017 --logpath "C:/Users/mbx/Documents/model_f

just saw the EDIT2 comments. The error is [2024-05-13T15:06:05.565994 #8212] ERROR -- : Mongod failed to launch. Please

side note, given your goal, I would approach it a different way and maybe this will work for you as well. Here is a repo

trying to catch up, so it does work on the local Windows 11 base box, but the server wont start in the virtualbox VM on

sorry, just seeing this. The example project in the PAT repo are very old and I dont think those measures work anymore.

There are notebooks here that document how to use the various SDK and CLI methods to run parametric analyses using OSAF.

those are the logs for the server backend. The sdp_log_file (toggle view) link doesnt show a log or an error in your mi

look in your project folder, in the datapoint run directories for run logs and .err files

i'm sad to say but 3.7.0 also got packaged with the wrong energyplus version. We had a change in personnel and have bee

is this a shared drive or something? I would expect the path to be 'c:\ something something', instead its 'JCl_LenexaKS

also, try using the latest 3.6.1-1 release.

this will sound silly, but reboot your computer to kill any zombie ruby processes from previous failed startups. copy th

navigate using the OSAF GUI (view server button from PAT), to the datapoint page for the failed datapoint.you do that by

what about the other log files in the datapoint zip?

3.6.1 was released with the wrong version of EnergyPlus. 3.6.1-1 was just released to fix that issue.

PAT 3.6.0 and 3.6.1 have an issue where they were packaged with the wrong version of EnergyPlus. 3.6.1-1 was just relea

just added a link to some slides which include tips on how to debug

That error message on the Admin page was just cosmetic and is safe to ignore. It was fixed a few versions ago issue her

OS 3.6.0 Should use EnergyPlus 23.1 compatibility matrix. PAT 3.6.1 is getting re-released since it had the wrong ver

i would be looking for the datapoint simulation log and the energyplus .err file. Those are avail from a datapoint page

really need more information than that, but you can start by viewing the server in a webpage. from there you can downlo

the analysis error can be debugged on the Analysis GUI page. theres a link to see the 'log' just to the right of the li

That error message on the Admin page was just cosmetic and is safe to ignore. It was fixed a few versions ago issue

you can ignore that CLI version error, that was fixed in later updates

okay, that method to start/stop AWS resources was deprecated. That relied on older EC2 instances which are increasingly

are you running in the local PAT server? or using a cluster stood up by using the helm charts (or your own docker swarm

looks like you have it correctly. The 'directory to include' will get added to the project.zip file and submitted to th

try using PAT 3.5.1. its best to use the same version of all the tools.

OS 3.6.0 uses EnergyPlus 23.1 compatibility matrix.

The OpenStudio Analysis Framework OSAF can do optimization for BEM/BPS.

We created methods for calibration with OpenStudio models and had some examples in this repo: That workflow is now depr

That sounds correct. An example OSA can be found here. The output variable section defines the output variables and whi