MOF++

Data › Nets › lcw

Net topology

lcw

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

JSON · mfpx

6 vertices and 6 edges in the unit cell. 3 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 = 2.0000 Å, b = 2.0000 Å, c = 2.0000 Å
Cell angles
α = 90.00°, β = 90.00°, γ = 90.00°
Atoms in cell
6
Transitivity pqrs
not recorded
Catenated
no
No, and not from a measurement of the topology: it is the MOF+ name heuristic, the -c marker in the name read back, and that source measures no interpenetration. mofpp.periodicity v1 analysed the MOF+ deposit, the graph of the uploaded topology file and states that it cannot say how many copies this net has: 3 of 3 quotient components are not 3-periodic (3 chains (rank 1)), so the net is not made of 3-periodic copies: how many interpenetrate is not defined, and catenation cannot be judged from it So the value above is the one already on record, this measurement neither confirms nor contradicts it, and the inability is not a claim that the net is not interpenetrated.

Canonical key

Systre key
noneNo Systre key: the name lcw 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 for this row either, and that is a result rather than a gap: Systre 19.6.0 resolved the MOF+ deposit, the graph of the uploaded topology file into 3 connected nets, and computed a canonical key for each of them rather than one for the collection of them. Those keys are served under topology.symmetry beside the component each describes.
Checksum
not recorded

Vertices

The mapping of coordination sequences onto vertex classes that the source supplied was checked against a walk over the periodic topology of the net itself, one walk per vertex class, and agreed. The sequences are the values the source supplied; the walk settled nothing but which class each one describes.

Site symmetry. Not recorded. A vertex's site symmetry is its Wyckoff position in the net's maximum-symmetry embedding, and it is computed here from the net's own graph rather than read from any source — neither source states one. It is blank on this record because that computation could not be made for it, not because the vertices have no site: the commonest reasons are a 2-periodic net (whose symmetry is a plane group, and the Wyckoff tables used are the 230 space groups), a graph that resolved into more than one connected net or into an interpenetrated array, a net Systre refused or could not finish, and a net whose barycentric placement puts distinct vertices on one point. The run report names which.

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 site symmetry is the vertex's Wyckoff position in the net's maximum-symmetry embedding. The three columns do not carry the same warrant: which of them was corroborated, which was not, and which was computed here, is stated above the table.
# Coordination Site symmetry Vertex symbol Coordination sequence
0 2 ——2 2 2 2 2 2 2 2 2 2
1 2 ——2 2 2 2 2 2 2 2 2 2
2 2 ——2 2 2 2 2 2 2 2 2 2
3 2 ——2 2 2 2 2 2 2 2 2 2
4 2 ——2 2 2 2 2 2 2 2 2 2
5 2 ——2 2 2 2 2 2 2 2 2 2

Computed topology

Computed here from the quotient graph of the net itself, not transcribed from either source: periodicity, symmetry, invariants and rings, on the MOF+ deposit, the graph of the uploaded topology file, by mofpp.invariants 2, mofpp.periodicity 1, mofpp.rings 2 and systre 19.6.0 sha256:0d272e98a1a21669bc67a809b95c014ba2a2fb39a6fd2147039201216ab0d48d options:--systreKey wrapper:2. Each basis is analysed on its own and the results are never merged, because a MOF+ deposit and an RCSR archive key are two different graphs that usually describe the same net and sometimes do not. The transitivity r and s are computed by nothing in this project: they count the faces and the tiles of a natural tiling, and none is derived here. That is a measured limit rather than a job not yet done. The Gavrog library this project runs Systre from was tried on 2026-09-12: for a 3-periodic net it has no route from a net to a tiling at all, and for a 2-periodic net it has one that works, whose result is a plane tiling with faces and no tiles and so a transitivity triple rather than an r and an s. This block therefore states p and q and leaves r and s unknown rather than filling them. Every entry carries the tool, its version and input_checksum, the checksum of the graph that was actually analysed, so that a result computed from the graph this record holds now can be told from one computed before it changed. Nothing here rebuilds a graph to check that, so no entry below is claimed to be current.

Periodicity — the MOF+ deposit, the graph of the uploaded topology file

Periodicity (mofplus-deposit)
1-periodic
One connected net (mofplus-deposit)
no
Interpenetration (mofplus-deposit)
not determined
3 of 3 quotient components are not 3-periodic (3 chains (rank 1)), so the net is not made of 3-periodic copies: how many interpenetrate is not defined, and catenation cannot be judged from it
Computed by (mofplus-deposit)
mofpp.periodicity 1 — ok

Symmetry — the MOF+ deposit, the graph of the uploaded topology file

Systre found 3 separate nets in the repeat unit, so no single group, transitivity pair or key describes the structure. The fields below are therefore null and each component is served under components; none of them is promoted to stand for the whole.

Ideal space group (mofplus-deposit)
not computed
Transitivity p, q (mofplus-deposit)
not computed
Point-group order (mofplus-deposit)
not computed
Repeat-unit factor (mofplus-deposit)
not computed
RCSR identification (mofplus-deposit)
none stated
Computed Systre key (mofplus-deposit)
not computed
Key against the archive (mofplus-deposit)
not compared No Systre key was computed on this basis, so there is nothing to compare with the archive text. This is not a disagreement.
TD10 as Systre prints it (mofplus-deposit)
not computed
Computed by (symmetry, mofplus-deposit)
systre 19.6.0 sha256:0d272e98a1a21669bc67a809b95c014ba2a2fb39a6fd2147039201216ab0d48d options:--systreKey wrapper:2 — ok
The separate nets Systre found sharing this repeat unit. None of them is served above as the answer for the structure as a whole, because none of them is.
# Ideal space group Multiplicity RCSR identification TD10
1 opm — — 21
2 opm — — 21
3 opm — — 21

Invariants — the MOF+ deposit, the graph of the uploaded topology file

TD10, exact (mofplus-deposit)
21.0
Genus (mofplus-deposit)
not determinedgenus is defined for one connected 3-periodic net; this one is not (periodicity 1, connected False) (3 of 3 quotient components are not 3-periodic (3 chains (rank 1)), so the net is not made of 3-periodic copies: how many interpenetrate is not defined, and catenation cannot be judged from it)
Shells walked (mofplus-deposit)
10
Computed by (invariants, mofplus-deposit)
mofpp.invariants 2 — ok

Rings — the MOF+ deposit, the graph of the uploaded topology file

Net point symbol (mofplus-deposit)
not determined 6 vertices have no point symbol, so the net point symbol is unknown
Longest ring searched (mofplus-deposit)
40 Some angle of this net has no ring within that bound. Those angles are written * rather than given a ring that was never found.
Computed by (rings, mofplus-deposit)
mofpp.rings 2 — ok
Computed from the graph itself, one row per set of vertices carrying the same symbols. The cycle symbol follows the MOF+ convention — the shortest cycle at each angle — and is the one comparable with the stored column above; the RCSR ring symbol names the shortest ring at each angle, with * where none exists within the bound, and is a different quantity.
Vertices Cycle symbol (MOF+ convention) RCSR ring symbol Point symbol Coordination sequence
0, 1, 2, 3, 4, 5— 1 angle has no cycle of at most 40 edges * — 2 2 2 2 2 2 2 2 2 2

Cross-checks

Name against the computed key
single-source
Stored sequences against the computed ones
corroborated: 6 of 6 vertex rows agree with mofpp.invariants v2 (mofplus-deposit), compared on the stored length.

Provenance

Source
mofplus
Identifier at the source
lcw
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 lcw 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
141 The order the ingest processed this net in, simplest first. A different number from the RCSR index above, meaning a different thing.