top of page
WhatsApp Image 2026-10-07 at 11.40.37 PM.jpeg

Cálculos de carga ASHRAE Std 183

Esta serie de tutoriales de YouTube de Helix Energy Partners abarca metodologías avanzadas de OpenStudio, incluyendo la creación de medidas personalizadas complejas en Ruby o Python, la interacción con el MCP de OpenStudio y la contribución al software de código abierto OpenStudio. La serie está dirigida a ingenieros que dominan los fundamentos de OpenStudio y están preparados para abordar el diseño detallado de sistemas, la caracterización de equipos y la manipulación programática de modelos. Asimismo, puede servir como punto de partida para proyectos de investigación y tesis de nivel universitario mediante la contribución de estrategias de automatización a la Building Component Library (Biblioteca de Componentes de Edificación).

Estándar ASHRAE 183: Cálculos de cargas en edificaciones con SketchUp/OpenStudio
8 de octubre de 2019

Conózcanos

En este video de YouTube, explicamos los pasos necesarios para crear la geometría de un edificio con SketchUp y el complemento OpenStudio. Las cargas de calefacción y refrigeración del edificio se calculan según la norma ASHRAE 183 utilizando el motor de simulación EnergyPlus del Departamento de Energía de EE. UU. a través de OpenStudio.
Todo el software utilizado para estos cálculos (SketchUp, OpenStudio y EnergyPlus) es de código abierto y se puede descargar gratuitamente.

Pasos de modelado de Open Studio:

1. Cree un nuevo modelo de OpenStudio (OSM) con el asistente.

2. Vaya a Ventana → Preferencias → General. Configure el tiempo de guardado automático según sus preferencias.

3. Vaya a Extensiones → OpenStudio → Preferencias. Configure el sistema de unidades en IP.

4. Vaya a Ventana → Información del modelo → Geoubicación. Agregue la ubicación del proyecto.

5. Vaya a Ventana → Preferencias → OpenGL. Marque la opción "Usar tamaño máximo de textura". (Puede desmarcar esta opción más adelante si ralentiza el modelo).

6. Vaya a Extensiones → Scripts de usuario de OpenStudio → Generadores de plantillas → Asistente para tipos de espacio y conjuntos de construcción. 
- Añada tipos de espacio adicionales según sea necesario.
- Desmarque "Crear conjunto de construcción".
- Desmarque "Establecer valores predeterminados del edificio".

7. Dibuje una línea de escala hasta la dimensión exacta conocida del edificio.

8. Vaya a Archivo → Importar.
Importe el plano del sitio o de planta del proyecto. 
Colóquelo en el modelo y escálelo utilizando la línea de escala. 
NO gire el modelo al norte verdadero todavía.

9. Trace la distribución del edificio sobre el plano de planta con las herramientas de dibujo de SketchUp. Seleccione la imagen del plano → Haga clic derecho → Ocultar/Mostrar según sea necesario. (Opcional: Ventana → Preferencias → Atajos de teclado para personalizar los atajos de teclado).

10. Una vez finalizado el trazado del plano, seleccione todos los elementos de línea del plano y haga clic en el botón "Crear espacios a partir del diagrama".

11. Haga doble clic en los espacios individuales para: - Editar la altura del espacio - Añadir plénums o elementos adicionales - Insertar ventanas y puertas

12. Vaya a Extensiones → Scripts de usuario de OpenStudio → Modificar o añadir elementos del modelo → Intersecar geometría del espacio.

13. Haga clic en el botón Coincidencia de superficies → Coincidir con todo el modelo.

14. Seleccione un espacio y haga clic en "Establecer atributos para los espacios seleccionados".

Asigne tipos de espacio a todos los espacios.

Abra el Inspector de OpenStudio si es necesario y cambie el nombre de los espacios como prefiera.

15. Vaya a Extensiones → Scripts de usuario de OpenStudio → Modificar o añadir elementos del modelo →

Añadir nueva zona térmica para espacios sin zona térmica.

16. Seleccione los espacios uno por uno y cambie el nombre según los planos del proyecto.

17. Vaya a Extensiones → Scripts de usuario de OpenStudio → Modificar o añadir elementos del modelo →

Cambiar el nombre de las zonas térmicas según los nombres de los espacios.

18. Seleccione los espacios en grupos por tipo. Haga clic en "Establecer atributos para espacios seleccionados" y asigne: - Tipo de espacio - Tipo de termostato (También puede combinar varios espacios en una sola zona térmica aquí).

19. Vaya a Extensiones → Scripts de usuario de OpenStudio → Modificar o agregar elementos del modelo → Eliminar zonas térmicas no utilizadas.

20. Seleccione ventanas específicas → Extensiones → Scripts de usuario de OpenStudio → Modificar o agregar elementos del modelo → Agregar voladizos por factor de proyección.

21. Para sombreado vertical o personalizado, haga clic en el botón "Nuevo grupo de superficies de sombreado".

22. Gire el modelo para alinearlo con el norte verdadero.

23. Si se perdió la geolocalización, reinsértela para mantener la orientación de referencia.

24. Crear sombreado adyacente (edificios, árboles, etc.):
- Haga clic en "Nuevo grupo de superficies de sombreado".
- Use imágenes de geolocalización como referencia.
- Trace la imagen de geolocalización si es necesario antes de editar las superficies de sombreado.

25. Vaya a Ventana → Bandeja predeterminada → Sombras.
Revise y simule sombras. 
Elimine las superficies de sombreado innecesarias para reducir el tiempo de cálculo.

26. Abra el Inspector de OpenStudio → Purgar objetos no utilizados de los recursos de OpenStudio. 
Seleccione "OS:Edificio" e introduzca el nombre del proyecto.

27. Haga clic en el botón "Iniciar OpenStudio".

28. Vaya a Preferencias → Unidades.
Establezca las unidades en inglés (I-P).

29. Seleccione los archivos de Clima y Día de Diseño adecuados.

30. Vaya a la pestaña "Programaciones" → "Programaciones".
Cree y asigne una programación de encendido/apagado para los extractores de aire.

31. Vaya a la pestaña "Zonas Térmicas" → "Sistemas de HVAC".
Verifique que todas las zonas tengan programadas las programaciones del termostato. 
Agregue extractores de aire a las zonas correspondientes.

32. Vaya a la pestaña "Zonas Térmicas" → "Parámetros de Dimensionamiento de Refrigeración".
- Establezca la Temperatura del Aire de Suministro de Refrigeración de la Zona a 13 °C.
- Ajuste la eficacia de la distribución del aire, si corresponde.

33. Repita el paso 32 para los Parámetros de Dimensionamiento de Calefacción.

34. Vaya a la pestaña "Medidas" → "Informes".
Arrastre la medida "Resultados de BCL OpenStudio" a "Medidas de Informes".

35. Ejecute la simulación.

36. Navegue al directorio del modelo. Abra el archivo HTML de resultados generado en un navegador web. Imprímalo o guárdelo como PDF para su registro y referencia.

RESULTADOS DE ENERGYPLUS EN UNIDADES IP

37. Vaya a la pestaña Medidas → Haga clic en "Buscar medida en BCL".

38. Busque "Unidades IP".

39. Descargue la medida titulada "Establecer tabla de salida en unidades IP".

40. Cierre la ventana BCL.

41. Arrastre la medida descargada a la sección "Medidas de EnergyPlus".

42. Vuelva a ejecutar la simulación para ver los resultados en unidades IP.

2. Set up GitHub – Creates a GitHub account, configures Git identity and line endings, and installs the GitHub CLI (gh) so you can fork repos and open pull requests from the terminal.   3. Fork the OpenStudioApplication repository – Uses Claude Code and the gh CLI to fork openstudiocoalition/OpenStudioApplication and clone it locally, then creates a CLAUDE.md file so Claude has persistent project context (build command, clang-format version requirements, and known local test failures).   4. Build OpenStudio locally on Windows – Installs the native build toolchain (CMake, Visual Studio Build Tools, Python, Ruby, Conan, Qt), works around a known NREL Conan server SSL issue with a local Ruby package, configures with CMake, and compiles OpenStudioApp.exe. Also covers a Docker/WSL-based alternative build path for anyone who prefers a containerized environment. Timestamps: 0:00 Introduction 4:00 Part 1: Install Claude Code (AI CLI) 5:00 - Install Node.js 5:45 - Install Claude Code 6:40 - Add Claude Code to your PATH 8:10 - Install Git for Windows 9:50 - Authenticate 13:50 Part 2: Set Up GitHub 14:00 - Create a GitHub account 14:40 - Configure Git identity and line endings 20:50 - Install the GitHub CLI 23:30 Part 3: Fork the OpenStudioApplication Repository 23:45 - Fork with AI assistance 32:05 - Create a CLAUDE.md file 33:35 Part 4: Build OpenStudio Locally on Windows 34:11 - Install prerequisites 36:05 - Install Qt 36:30 - Set up Conan 38:05 - Create a local Ruby package for Conan 38:30 - Edit the project's conanfile.py 39:00 - Run Conan install 41:10 - Configure with CMake 43:00 - Build 44:45 - Launch and test

Proceso de modelado y simulación de OpenStudio paso a paso

Esta sección explica el flujo de trabajo completo para realizar cálculos de carga de edificios utilizando SketchUp y OpenStudio.

Today we are going to be talking about MCP servers, and specifically the MCP server that was created by the National Laboratory of the Rockies to be used with the OpenStudio application. We will search for it here. It is on GitHub and it is NREL's OpenStudio MCP. What is an MCP? It is a newer thing. It has to do with AI agents and it is a standardized way for AI agents to exchange information. For this specific purpose, it is for the AI agent to understand all of the commands and capabilities of OpenStudio, so that the agent itself can execute those commands and modify your models. If you are cloning an HVAC loop, or injecting a thermal zone, or any of those functions that you do in the OpenStudio application, the AI agent can execute those. In fact, the AI agent has even more capabilities because the OpenStudio application's graphical user interface has only exposed a limited set of the basic needs of the OpenStudio and EnergyPlus software. An AI agent would have the full capabilities of the OpenStudio software development kit. It would have a fuller understanding of how to modify your model. The National Laboratory of the Rockies has developed this MCP server to exchange information with AI agents and basically to teach AI agents how to use OpenStudio. With that, you can basically tell the AI agent in plain English, or whatever your language happens to be, in plain language what exactly you want the AI agent to do. The AI agent can ask you more questions, or if it is simple enough, the AI agent will understand and will query the MCP server to find out what kind of data can be manipulated or changed to modify your model. You could tell the agent: I want to change these windows on the north side of the building to an R-value of this, or a solar heat gain of this. The AI agent can understand that, it can execute the commands for the OpenStudio software development kit, and it can modify your OpenStudio model. With that said, we are going to go through a tutorial on how to get set up with the OpenStudio MCP today. I have created a tutorial. This is an MD file. I will put a link to that in the description below. The idea is that you can go through this yourself, or you can also have your AI go through this with you, and it would help install the OpenStudio MCP. This video presupposes that you have already installed an AI onto your computer. I do go through that in one of my previous videos. I will also put a link to that in the description. That video goes through the installation process for Claude CLI, also known as Claude Code. So that is what we are going to do. Let us go ahead and start Claude. We are going to open up a command prompt and we need to browse to our projects folder. This is a folder that we set up in my previous video. One note about my previous video: there is a lot of extra unrelated stuff, so I would just follow through the steps on that previous video for installing Claude Code. You do not have to continue to the additional steps. I will put a note in the description below. Let us open up that projects folder and let us instantiate Claude. I want to install and test out the OpenStudio MCP. Please guide me through this tutorial, and then we are just going to paste the path to this tutorial. All right. Claude wants to log in. Sometimes that happens. Okay. We are logged in. Claude wants to check if we have WSL, Docker, Git, or a repo or MCP installed. We will just accept. All right. Most of this stuff is not installed. You may have some of these installed, most likely not, but it is entirely possible. Some of this you will have to do by yourself. We need to open up a command prompt separate from Claude. Let us do that. We really need to open up a command prompt with administrator privileges. Let us right click on the Windows button and do Terminal Admin. Click yes. This is PowerShell, but that is okay. Let us copy this and paste it into our PowerShell. Hit enter. It is going to go through installing WSL. WSL stands for Windows Subsystem for Linux and it basically allows you to run Linux on a Windows computer. The reason we need this is because the OpenStudio MCP uses Linux. In order for our Windows machine to talk to the OpenStudio MCP, it uses WSL as an interpreter or a bridge to allow that to happen. Okay, so that is good. We are just going to paste this output back to Claude. Okay. It installed WSL, but Ubuntu was not set up. So first we need to reboot the machine. Let us go ahead and reboot it first. Okay. We are booted back up. Let us open up Claude again, and resume our session. It is going to be this one here. All right. It says: reboot the machine and after it comes up, open up another command prompt and run this right here. Let us copy, right click, Terminal Admin, yes, and paste. We will paste this back to Claude. It says that Ubuntu was not installed. Let us go ahead and copy this and install Ubuntu. Paste this back to Claude. This is one of the issues. We will have to turn off a VPN if we already have one running, as it is not able to resolve this. Let us go ahead and do that now. All right. Let us go ahead and try this again. All right. That works. It is downloading Ubuntu now. If it seems to get stuck, you can cancel and try again. Control-C to cancel. Then let us try to do it again. All right. It is installed successfully and it just wants us to create an account and a password. All right. We will say no for now. Excellent. Ubuntu is installed. All right. We will tell Claude that Ubuntu is installed. It just wants to verify. All right. We have WSL running. The next step is to install Docker Desktop. Docker Desktop is like a sandbox that allows you to run programming code, AI agents, and test programs inside a safe area that is only allowed certain access to certain files. It is contained within this sandbox, so it is not able to get out into your computer. That is what we are going to do here. We will install Docker. We need to go to the website and download Docker Desktop. For us, it is going to be Windows AMD64. Okay, it is downloaded. Let us go ahead and run it. The tutorial says to just go through the regular installation process, but we want to ensure that "Use WSL2 instead of HyperV" is checked. We will click this. Okay. All right. Now that we have installed this new software, we need to close and restart. We are back and we have restarted. It is just going through the service agreement and we are just going to hit Accept. We can skip this stuff for now. Let us open Claude back up. Okay. Docker is running. Claude is going to verify the version. Claude is just going through some setup notes that I have in the tutorial. Now Claude is going to clone the OpenStudio MCP repository. Click yes. This is getting all of the latest information from the MCP repository. Now it is going to build the Docker image. It is building the MCP inside the Docker that we just created. Click yes. Creating directories. Right now it is just building the MCP inside the Docker for us. It is basically building a mini computer in our sandbox that we can use to modify our OpenStudio models in that safe environment. Okay, there is a light power failure here. Let us do this. The next step is to restart Claude, because this session of Claude does not know about or is not connected to the MCP yet. Let us exit out of this and re-enter. Okay. We will type /mcp. It says the OpenStudio MCP is now connected. These are all the tools that the MCP has that Claude has access to. All right. We will hit Escape. Escape. Escape. Claude is asking for the version. Great. It is fully working and now we can jump in and start asking Claude to do something. What we are going to do is something simple. I have an example model here. We will just do something simple, like for instance, this gas heating coil here. This will maybe be easier doing it ourselves, but this is just a demonstration of Claude doing it for us. We have this coil heating gas here and I am just going to ask Claude to change this to an electric heating coil instead. We will copy the path. I have this model at this location. I want to change the coil heating gas one to an electric heating coil instead. What I am going to do here is just let Claude run free with it. Right now we are on manual mode with Claude and I am just going to do Shift-Tab until we get to automatic. That will turn Claude loose and it can just hammer away at it. Click yes. Shift-Tab. Auto. All right. Claude has successfully...well, we will see if it successfully did this, but it looks like it had to write a custom measure, a custom piece of code, to replace that coil for us. One of the things with the OpenStudio MCP is that it has a lot of connectors that allow you to do these things, but it does not actually have methods to do some of this stuff. That is not a problem, though, because AI is really good at creating custom programs. AI can figure out how to make those connections work. That is what Claude had to do here. I will talk about this in some of my future videos as far as adding a code base so that Claude has code snippets it can use. For now, let us go ahead and take a look at what Claude did and see how it turned out. I am going to have it overwrite this model for us. Let us go ahead and take a look at the model. We have got this gas heating coil here, and we asked it to replace it with an electric coil. Let us go to File, Revert to Saved. That should open up the new model that Claude just overwrote. Yes, here it is. It was successfully able to replace that gas coil with an electric heating coil. This was just a simple example. Claude can do a lot of this simple stuff, and more complicated stuff too. I go into some of my other videos about writing custom measures, and AI agents are really good at writing code. That is probably what you will end up using this for most of all: to write custom programs to modify your model, then inspect the energy use, loads, and simulating conditions. That is it in a nutshell for installing the OpenStudio MCP. I hope this tutorial was helpful for you. I look forward to seeing you in the future. Thank you. Please like and subscribe.

Proceso de modelado y simulación de OpenStudio paso a paso

Esta sección explica el flujo de trabajo completo para realizar cálculos de carga de edificios utilizando SketchUp y OpenStudio.

1. Create a branch and solve an issue with AI – Reads and understands a real GitHub issue (Issue #857), creates a new branch off develop, works with Claude Code to locate and fix the relevant code, rebuilds incrementally, tests the fix in the running app, commits the change (without staging machine-specific build workarounds), and pushes the branch to open a pull request. 2. Tips from real experience – Practical lessons for working with Claude Code day to day: treating it as a collaborator rather than a magic button, keeping CLAUDE.md updated, using "!" to run shell commands without leaving a session, fixing pre-commit hook failures, running Ruby scripts through OpenStudio's bundled interpreter, handling SSL errors safely, and asking better questions to get better results. Timestamps: 0:00 Introduction 1:15 - Understand the issue 9:30 Part 5: Create a Branch and Solve an Issue With AI 9:45 - Create a new branch 11:14 - Work with Claude to find and fix the code 12:45 - Rebuild incrementally 13:15 - Test your fix 21:30 - Commit your changes 23:11 - Discuss Push and create a pull request 23:48 - Work with Claude to solve the second part of the issue 37:15 - Rebuild incrementally 37:33 - Test your fix 40:45 - Commit the changes 42:15 - Try to Push with new Github account - Unsuccessful 43:30 - Create a whole new Repository with the fix 47:53 - Try to fork on github.com - Unsuccessful 49:08 - Summary

bottom of page