You’ve coded up your CEA plugin - now it’s time to add it to the CEA and share it with the rest of the world!

This article goes into the details of the plots.yml file used in CEA plugins.

Now that you have an overview of the CEA plugin template, let’s dive into some of the files responsible for adding a new tool to the CEA.

The easiest was to get started creating your own plugin is to start with the CEA plugin template. In this article, we’ll get you started with your own plugin based on the CEA plugin template on GitHub.

Let’s take a bird’s-eye view of the parts that make up a CEA plugin. We’ll cover the interface expected by the CEA when you define a plugin as well as it’s default implementation: cea.plugin.CeaPlugin.

If you’d rather just start with an example and tinker from there, skip to Part 3: Introduction to the CEA plugin template and come back here if you have any questions.

The City Energy Analyst (CEA) consists of a core set of tools and visualizations of the output of those tools. This article is about extending that set with your own tools and your own visualizations. To do that, you’ll need to write a CEA plugin.

Version 2.30.0 of the City Energy Analyst (CEA) introduced a new feature: The Database Editor. In this 3 part series, I’ll explain how to

• jump-start your scenario with Archetypes (this post)
• fine-tune your scenario with Assemblies (part 2 of this series)
• a few words on Components, also exporting and assigning databases (part 3 in this series)

The Archetypes Mapper mentioned in part 1 of this series sets up basic properties for your scenario. In this post, I’ll go into more detail on how to fine-tune your scenario using the Assemblies defined in the database.

It’s time to wrap up the series on working with CEA Databases - in this post we’ll examine the role of Components for the CEA simulations as well as assigning and exporting databases for your scenarios.

Hold on - we’re in for a bumpy ride! Today, we’re going to explore a feature of the City Energy Analyst that is slightly hidden: The cea workflow command.

This post goes into the gory details of plotting with the CEA Dashboard interface. It should help understand existing code as well as creating new plots for the CEA.

Or “How To Replicate the Read The Docs Bild Process Locally with Docker”

This is not the first time I came across the RTD Build Process documentation and failed to figure out how to run this locally with their docker image. So. This time I’m going to document the steps I take for future reference.

This post is a bit of a little note to myself: The other day, when writing a post on the new installer for the CEA, I wanted to stitch together a bunch of screenshots into a GIF, with each screenshot showing for one second.

In part 1 of this series, I showed you how to do a basic installation of the City Energy Analyst (CEA). For Researchers and Developers that would like to edit the source code of the CEA, this post explains how to set it up.

Up until very recently, the official guide to installing the City Energy Analyst (CEA) on Windows involved a bunch of arcane steps that sometimes tripped up new (and experienced) users. So we set out to come up with a better solution:

Try out the CEA Installer!

You have no idea how excited I am about this release! Revision r223 of the RevitPythonShell has been tested by a select few very brave people (Ehsan Iran Nejad and Callum Freeman) and seems to work. Normally I’m not so worried about pushing out new versions, but this one is… different.

This post explains how to use the esoreader, a python module for parsing the .eso file produced by EnergyPlus. It also includes a small (incomplete) reverse engineering of the .eso file format.