The Energy Impact of Domain Model Design in Classical Planning
This paper empirically demonstrates that specific domain model design choices, such as element ordering and action arity, significantly influence the energy consumption of classical planners, often in ways that do not correlate with runtime performance.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are hiring a team of expert chefs (the AI planners) to cook a complex meal. You give them a recipe book (the Domain Model) that lists the ingredients, the steps, and the rules for cooking.
For years, researchers have only cared about one thing: How fast can the chefs finish the meal? They tweak the chefs' skills or the kitchen tools to make them faster. But this new paper asks a different question: How much electricity does the kitchen use to cook that meal?
The authors discovered that the way you write the recipe matters just as much as the chef's skill. Even if two recipes result in the exact same meal, writing them differently can make the kitchen use vastly different amounts of energy.
Here is the breakdown of their findings using simple analogies:
1. The Setup: The "Green AI" Kitchen
The researchers set up a controlled kitchen with five different types of chefs (planners) and five different types of meals (domains, like moving blocks or playing a game of "gripper"). They created 32 slightly different versions of the same recipe for each meal. Some versions just shuffled the order of words; others added useless ingredients; and some changed the rules so the meal became impossible to finish.
They measured the electricity used by the CPU (the stove) for every single attempt.
2. The Three Ways to Mess Up a Recipe
The paper groups the changes to the recipe into three categories:
A. Shuffling the Words (Syntactic Structure)
- The Analogy: Imagine a recipe that says "Add salt, then pepper" versus "Add pepper, then salt." Or listing ingredients alphabetically instead of by usage.
- The Result: For most chefs (specifically the "Fast Downward" family), this didn't matter at all. The electricity usage stayed the same. However, for a different style of chef (the "LAPKT" family), shuffling the order of steps sometimes confused them, causing the kitchen to use 3 to 4 times more electricity just because the words were in a different order.
B. Adding Useless Stuff (Modelling Redundancy)
- The Analogy: Imagine a recipe that says "Add 1 cup of flour," but then adds a line saying "Add 1 cup of invisible, unused flour" or "Add a handle to the spoon that isn't needed."
- The Result: This was the biggest energy thief. When the researchers added "dummy" parameters (like adding a handle to every tool in the kitchen that no one uses), the electricity usage skyrocketed. In some cases, the energy use went up by 12 times. It's like asking the chef to count every grain of sand on the beach before they can start chopping onions. The chefs didn't necessarily fail, but they burned a massive amount of energy doing unnecessary work.
C. Changing the Rules of the Game (Task Design)
- The Analogy: Imagine a recipe that says "If you drop the egg, you must throw the whole kitchen away" (a dead-end state). Or, a rule that makes the final dish impossible to serve.
- The Result: This was the most unpredictable. Sometimes, adding a "dead-end" rule made the chefs give up quickly, saving energy. Other times, it made them run in circles for hours, burning huge amounts of electricity. It depended entirely on the specific meal being cooked. For some dishes, a small rule change caused the energy use to jump 30 times higher.
3. The Big Takeaway
The most important lesson from this paper is that speed and energy are not the same thing.
- The Old Way: If a recipe takes 5 seconds to cook, we assume it's efficient.
- The New Reality: A recipe might take 5 seconds but use a tiny amount of electricity, while another takes 5 seconds but uses a massive amount of electricity because the chef was forced to do unnecessary mental gymnastics.
The paper concludes that the "design" of the recipe (the domain model) is a hidden lever for energy efficiency. If you want to save energy in AI planning, you don't just need a faster chef; you need a cleaner, less redundant, and smarter recipe.
Summary of the "Energy Impact"
- Shuffling words: Mostly harmless, unless you use a specific type of chef.
- Adding useless items: A disaster for energy efficiency. It makes the kitchen work 2x to 12x harder for no reason.
- Changing the rules: A gamble. It can either save energy or waste a fortune, depending on the specific problem.
The authors built a framework (a "recipe tester") to help designers spot these energy-wasting mistakes before they ever run the AI. They found that energy efficiency is a structural property of how the problem is described, not just a result of how fast the computer runs.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.