MOF++

Data › Nets › lcy-cs

Net topology

lcy-cs

Ingested production record from mofplus. Per-field provenance in field_sources.

JSON · mfpx

8 vertices and 24 edges in the unit cell. 18 of them leave the cell and continue into a neighbouring one; those are drawn in the accent colour and end at a hollow node. Squares are vertices of coordination 5 or more, circles of 4 or fewer. Drag to rotate, or focus the figure and use the arrow keys.

Crystallographic description

Spacegroup
not recorded
Cell lengths
a = 1.6175 Å, b = 1.6175 Å, c = 1.6175 Å
Cell angles
α = 90.00°, β = 90.00°, γ = 90.00°
Atoms in cell
8
Transitivity pqrs
not recorded
Catenated
yes
Yes, on the MOF+ name heuristic: that source marks a catenated net by a -c in its name, which the legacy client filters on, and this is that marker read back. A name heuristic, not a computed property of the topology, and not a measurement either source made.

Canonical key

Systre key
noneNo Systre key: the name lcy-cs is not one of the 2930 symbols in the RCSR Systre archive of 2019-06-01, and the MOF+ service supplies no canonical key at all, so neither source we read states one for this net. None is computed here.
Checksum
not recorded

Vertices

No coordination sequence is recorded for this net: the source stores none. Every sequence below is absent — which is a different fact from a sequence of length zero, and is why the field is null rather than an empty list.

Not corroborated. The coordination sequences beside these symbols carry a corroboration of their own, stated under coordination_sequences; the vertex symbols carry none. A vertex symbol names the shortest ring at each angle of a vertex, no ring perception runs anywhere in this project, and so there is nothing here that could reproduce one: these strings are served on the word of the source alone. What was checked is their shape — a d-coordinated vertex has d(d-1)/2 angles and a whole symbol names a ring at each, and a string that lists fewer is flagged rather than served as a symbol. A string that passes that count can still be wrong in its rings, and nothing here says otherwise.

One row per distinct vertex. The coordination sequence counts how many vertices lie at each topological distance; the vertex symbol names the shortest ring at each angle of the vertex. The two columns do not carry the same warrant: which of them was corroborated, and which was not, is stated above the table.
# Coordination Site symmetry Vertex symbol Coordination sequence
0 6 —3.3.3.5.5.5.5(2).5(2).5(2).5(2).5(2).5(2).6(4).6(4).6(4)—
1 6 —3.3.3.5.5.5.5(2).5(2).5(2).5(2).5(2).5(2).6(4).6(4).6(4)—
2 6 —3.3.3.5.5.5.5(2).5(2).5(2).5(2).5(2).5(2).6(4).6(4).6(4)—
3 6 —3.3.3.5.5.5.5(2).5(2).5(2).5(2).5(2).5(2).6(4).6(4).6(4)—
4 6 —3.3.3.5.5.5.5(2).5(2).5(2).5(2).5(2).5(2).6(4).6(4).6(4)—
5 6 —3.3.3.5.5.5.5(2).5(2).5(2).5(2).5(2).5(2).6(4).6(4).6(4)—
6 6 —3.3.3.5.5.5.5(2).5(2).5(2).5(2).5(2).5(2).6(4).6(4).6(4)—
7 6 —3.3.3.5.5.5.5(2).5(2).5(2).5(2).5(2).5(2).6(4).6(4).6(4)—

Provenance

Source
mofplus
Identifier at the source
lcy-cs
Retrieved
2026-09-09
Licence
CC BY 4.0 — verified from MOF++ project decision, CONTEXT §6 (Licensing): MOF+ is this group's own service, so nets retrieved from it are the project's own data to license, and the project licenses its data CC BY 4.0. No third-party grant is claimed..
Published
yes

Position in the collection

RCSR index
none No RCSR index: the name lcy-cs is not one of the 2930 symbols in the RCSR Systre archive of 2019-06-01, so this net has no position in that ordering and is listed after every net that does.
Complexity rank
380 The order the ingest processed this net in, simplest first. A different number from the RCSR index above, meaning a different thing.