Skip to content

Latest commit

 

History

History
56 lines (27 loc) · 1.74 KB

File metadata and controls

56 lines (27 loc) · 1.74 KB

08ed6ac7

Examples

ARC examples for 08ed6ac7

Rules (DSL)

DSL rules for 08ed6ac7

Notes

Finding Rules

Scene Parsing

We parse the input and output scenes into objects.

Mapping Input Objects to Output Objects

For each input object, there is only one object in the output scene with a matching position and shape, making it straightforward to produce a mapping from input objects to output objects.

e.g.

image 1

Finding Rules from Object Mappings

  • Before looking for rules, we prune the outputs of the mappings to keep only those properties that are being modified. We notice that the shape is always the same, it is just the “Colors” property that is changing.
  • When the objects are grouped by HeightRank, we notice that the “Colors” property can be determined.
    • If the HeightRank of an object is 1, it means that it is the shortest object.
    • If the HeightRank of an object is 2, it means that it is the second shortest object.
    • etc.

image 2

  • As of September 2022, the rule finder is now producing a single rule because it notices that the color integer of the output object can be inferred using the HeightRank value. This is probably not desirable, but works.

image 3

Some Notes on Input Object Properties

  • For each input object, we populate a long list of property values which can be used for potential rule formation. (e.g. Y, X, Height, Width, etc.)
  • We then supplement those properties, if they are numeric, with corresponding “Rank” and “InverseRank” properties.
  • Here is an example input object with each of its properties:

image 4