Note that the slot weight expression is typically configured to correspond to the "most limiting" resource, and furthermore behaves as a _measure of the number of potential matches remaining on the partitionable slot_.
+{section: Mixed Pools}
+Consumption Policy logic is enabled by attributes defined on individual partitionable slots, and is detected on a per-slot basis. This allows HTCondor pools to configure slots having Consumption Policies along side slots without them.
+
+Additionally, it is valid to configure slots having Consumpion Policies on the same pool with slots using scheduler splitting (CLAIM_PARTITIONABLE_LEFTOVERS).
+
+*NOTE*: Configuring the same execute node with both Consumption Policies _and_ CLAIM_PARTITIONABLE_LEFTOVERS is *not supported*. If an execute node enables Consumption Policies, it cannot enable CLAIM_PARTITIONABLE_LEFTOVERS, and vice versa.
{section: Consumption Policy Examples}
In the preceding discussion, examples of a cpu-centric and a memory-centric Consumption Policy were provided. A few other examples are listed here.
