BrianLBall's profile - activity

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

sounds like you are doing the right things. If speed is important, then make sure you are only reporting the variables

ah, its coming back to me. sorry its been 6 years. there is an argument 'verbose_messages'. This is very useful to ge

Sorry to be brief as I am traveling, but all the algorithms run in parallel. My recommendation is to choose a better in

All the algorithms run in parallel. My recommendation is to choose a better instance type, with more cores, etc.

you can use any reporting measure you want. The important part is to define the variable as an 'Objective Function', as

check the Rserve log to make sure the algorithm completed and didnt crash when trying to compute some finalization metri

there is a repo that can create OSAs from OSWs, here

The code is open source and free to use. You can stand up your own local server if you are familiar with Docker contain

OSAF is the framework (F) which encompasses PAT/OS-Server. OS-Server is the actual server which runs the models.

these notebooks have examples that use the meta_cli. they are in active development right now

i see, that is an OSA.json which describes the OSW workflow (list of measures and arguments) as well as the algorithm an

the meta_cli is a ruby file, however in the ruby notebooks, we are just doing system calls which look like: "/opt/OpenS

the meta_cli is a ruby file, however in the ruby notebooks, we are just doing system calls which look like: "/opt/OpenS

python measures are currently in development.

The PAT/sample_project files have not been updated in quite some time, so i think the errors you are getting is that the

this is a local deployment on your own hardware? for the deployment issues: check for dangling volumes, instances and c