MVS operator_name

CHANGELOG.md

@@ -9,6 +9,7 @@ All notable changes to this project will be documented in this file, following t
 - Add `vector_radius` param for primitive `angle_measurement`
 - Add `field_remapping` param for `*_from_*` nodes
 - Add `palette` param for `color_from_*` nodes
+- Add `operator_name` field to ComponentExpression and MVS annotations
 
 ## [v1.6.0] - 2025-04-22
 

docs/docs/annotations.md

@@ -133,6 +133,7 @@ Table of selector field names supported by individual MVS annotation schemas:
 | type_symbol       |                 |        |       |         |               |  X   |            |              |                    |     X     |     X      |
 | atom_id           |                 |        |       |         |               |  X   |            |              |                    |     X     |     X      |
 | atom_index        |                 |        |       |         |               |  X   |            |              |                    |     X     |     X      |
+| operator_name     |                 |   X    |   X   |    X    |       X       |  X   |     X      |      X       |         X          |     X     |     X      |
 
 To include all selector field names that are present in the annotation, one can use `"schema": "all_atomic"` (we could use it in the example above and the result would be the same). In future versions of MVS, non-atomic schemas might be added, to select parts of structures that are not composed of atoms, e.g. coarse models or geometric primitives.
 

docs/docs/selectors.md

@@ -27,6 +27,7 @@ There are three kinds of selectors:
         type_symbol?: str,        // Element symbol like 'H', 'HE', 'LI', 'BE'
         atom_id?: int,            // Unique atom identifier (_atom_site.id)
         atom_index?: int,         // 0-based index of the atom in the source data
+        operator_name?: str       // Symmetry operator name like 'X0-1' for assemblies or '1_555' for crystals
     }
     ```