Dataset Preview
Duplicate
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
Job has been terminated due to a temporary spike in resource usage and may be restarted later.
Error code:   JobManagerCrashedError

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

cicy_id
int64
h11
int64
h12
int64
chi
int64
lcs_shard_id
int64
lcs_row_index
int64
gv_shard_id
int64
gv_row_index
int64
has_gv
bool
31
0
0
0
0
0
null
null
false
32
0
0
0
0
1
null
null
false
33
0
0
0
0
2
null
null
false
34
0
0
0
0
3
null
null
false
35
0
0
0
0
4
null
null
false
36
0
0
0
0
5
null
null
false
37
0
0
0
0
6
null
null
false
38
0
0
0
0
7
null
null
false
39
0
0
0
0
8
null
null
false
40
0
0
0
0
9
null
null
false
41
0
0
0
0
10
null
null
false
42
0
0
0
0
11
null
null
false
43
0
0
0
0
12
null
null
false
44
0
0
0
0
13
null
null
false
45
0
0
0
0
14
null
null
false
46
0
0
0
0
15
null
null
false
47
0
0
0
0
16
null
null
false
48
0
0
0
0
17
null
null
false
49
0
0
0
0
18
null
null
false
50
0
0
0
0
19
null
null
false
51
0
0
0
0
20
null
null
false
52
0
0
0
0
21
null
null
false
1
15
15
0
0
0
null
null
false
2
15
15
0
0
1
null
null
false
3
15
15
0
0
2
null
null
false
4
15
15
0
0
3
null
null
false
5
15
15
0
0
4
null
null
false
6
15
15
0
0
5
null
null
false
7
15
15
0
0
6
null
null
false
8
15
15
0
0
7
null
null
false
9
15
15
0
0
8
null
null
false
10
15
15
0
0
9
null
null
false
11
15
15
0
0
10
null
null
false
12
15
15
0
0
11
null
null
false
13
15
15
0
0
12
null
null
false
15
15
15
0
0
13
null
null
false
22
15
15
0
0
14
null
null
false
53
16
14
4
0
0
null
null
false
54
16
14
4
0
1
null
null
false
55
16
14
4
0
2
null
null
false
56
16
14
4
0
3
null
null
false
57
16
14
4
0
4
null
null
false
58
16
14
4
0
5
null
null
false
59
16
14
4
0
6
null
null
false
60
16
14
4
0
7
null
null
false
61
16
14
4
0
8
null
null
false
62
16
14
4
0
9
null
null
false
63
16
14
4
0
10
null
null
false
64
16
14
4
0
11
null
null
false
65
16
14
4
0
12
null
null
false
66
16
14
4
0
13
null
null
false
67
17
13
8
0
0
null
null
false
71
17
13
8
0
1
null
null
false
74
17
13
8
0
2
null
null
false
75
17
13
8
0
3
null
null
false
76
17
13
8
0
4
null
null
false
77
17
13
8
0
5
null
null
false
78
17
13
8
0
6
null
null
false
79
17
13
8
0
7
null
null
false
80
17
13
8
0
8
null
null
false
81
17
13
8
0
9
null
null
false
83
17
13
8
0
10
null
null
false
84
17
13
8
0
11
null
null
false
85
17
13
8
0
12
null
null
false
86
17
13
8
0
13
null
null
false
88
17
13
8
0
14
null
null
false
89
17
13
8
0
15
null
null
false
90
17
13
8
0
16
null
null
false
91
17
13
8
0
17
null
null
false
92
17
13
8
0
18
null
null
false
93
17
13
8
0
19
null
null
false
94
17
13
8
0
20
null
null
false
96
17
13
8
0
21
null
null
false
97
17
13
8
0
22
null
null
false
98
17
13
8
0
23
null
null
false
99
17
13
8
0
24
null
null
false
100
17
13
8
0
25
null
null
false
101
17
13
8
0
26
null
null
false
102
17
13
8
0
27
null
null
false
105
17
13
8
0
28
null
null
false
106
17
13
8
0
29
null
null
false
108
17
13
8
0
30
null
null
false
109
17
13
8
0
31
null
null
false
110
17
13
8
0
32
null
null
false
112
17
13
8
0
33
null
null
false
113
17
13
8
0
34
null
null
false
114
17
13
8
0
35
null
null
false
115
17
13
8
0
36
null
null
false
116
17
13
8
0
37
null
null
false
117
17
13
8
0
38
null
null
false
118
17
13
8
0
39
null
null
false
119
17
13
8
0
40
null
null
false
120
17
13
8
0
41
null
null
false
121
17
13
8
0
42
null
null
false
122
17
13
8
0
43
null
null
false
123
17
13
8
0
44
null
null
false
124
17
13
8
0
45
null
null
false
125
17
13
8
0
46
null
null
false
126
17
13
8
0
47
null
null
false
127
17
13
8
0
48
null
null
false
End of preview.

cy-database — Calabi–Yau geometries for string-compactification workflows

Precomputed Calabi–Yau threefold data, organised as a family of sub-datasets, accessed through the stringforge infrastructure package. Each sub-dataset covers one class of Calabi–Yau constructions and is keyed by a class-specific identifier system.

This top-level card describes the conventions, layout, and loading interface that are common to all sub-datasets. Each sub-dataset has its own card with construction-specific details.

Available sub-datasets

Sub-dataset Construction class Identifier Status Card
tdf/ Trilayer, double favourable toric hypersurfaces from the Kreuzer–Skarke list (ks_id, triang_id) Available TDF card
cicy/ Complete-intersection Calabi–Yau threefolds cicy_id Available CICY card
kklt/ Curated KKLT index over tdf/ (one-face-divisor conifold classes) (ks_id, coni_class_id, coni_id) Available KKLT card

Quick start

pip install stringforge
from stringforge import CYDatabase, TDFDatabase, CICYDatabase, LCSDatabase, KKLTDatabase

# 1.  Pure I/O on the TDF sub-dataset (no JAXVacua import)
db = TDFDatabase()                                # downloads catalogue only (~10 MB)
df = db.query(h11=2, has_conifolds=True)          # catalogue-level filter, no shard I/O

# 2.  Same as 1, but in mirror convention and producing JAXVacua model objects
lcs = LCSDatabase(dataset="tdf")                  # mirror-convention wrapper
tree = lcs.load(                                  # returns a jaxvacua.lcs.lcs_tree
    ks_id=int(df.iloc[0]["ks_id"]),
    triang_id=int(df.iloc[0]["triang_id"]),
    h12=int(df.iloc[0]["h12"]),                   # h12 in mirror convention
    include_gv=True,
    include_conifolds=True,
)

# 3.  Plain CICY access
cicy = CICYDatabase()
cicy_df = cicy.query(h11=3)

# 4.  Curated KKLT index (logical links into TDF; no geometry duplication)
kklt = KKLTDatabase()
polys = kklt.query_polytopes(Q_min=100)

The LCSDatabase class is the recommended entry point for JAXVacua workflows: it operates in the mirror convention used by lcs_tree / FluxVacuaFinder and exposes load_model(...) to construct a fully initialised FluxVacuaFinder in one call.

Repository layout

aschachner/cy-database/
    README.md                       ← this file (umbrella card)

    tdf/                            ← Trilayer, Double Favourable toric models
        README.md                   ← TDF card
        catalog.parquet
        conifold_catalog.parquet
        schema.json
        manifest.json
        lcs_data/h11_{N}/
        gv/h11_{N}/
        conifolds/h11_{N}/
        polytope/
        extra/

    cicy/                           ← Complete-intersection threefolds
        README.md                   ← CICY card
        catalog.parquet
        schema.json
        manifest.json
        lcs_data/h11_{N}/
        gv/

    kklt/                           ← Curated KKLT index over tdf/
        README.md                   ← KKLT card
        catalog.parquet                       ← polytope-grain
        conifold_class_catalog.parquet        ← class-grain
        conifold_catalog.parquet              ← conifold-grain (with TDF link)
        schema.json
        gv/h11_{N}/

Shared design

All sub-datasets follow the same conventions.

Format

  • Apache Parquet shards for all bulk data.
  • One small catalog.parquet per sub-dataset, serving as the lazy-download entry point. KKLT additionally carries a class-grain and a conifold-grain catalogue.

Lazy, on-demand access

The stringforge.cy_io.CYDatabase class downloads only the files required by a given query:

  • db.query(...) → catalogue only (~10 MB).
  • db.load(...) → catalogue + the specific shard(s) needed for one model.
  • db.load_batch(...) → catalogue + shards for a batch of models.

Constructing a database object performs no network access; the first query downloads the catalogue, and only subsequent model-loading steps download shard files.

Cache modes

  • cache_mode="persistent" (default): shards are cached in memory (LRU) and on disk. Optimal for repeated access.
  • cache_mode="none": shards are downloaded, the requested row is read, and the file is deleted immediately. Ideal for scanning millions of models without filling local disk.

Offline mode

For HPC clusters without outbound network access, set offline=True. All data is served from the local cache; any missing shard raises FileNotFoundError instead of triggering a network call. The common pattern is to warm the cache on a login node and replay on worker nodes.

Schema versioning

Each sub-dataset carries a schema.json file with an integer schema_version. CYDatabase checks it against the client library's stringforge.SCHEMA_VERSION and raises a clear SchemaVersionError on incompatibility.

Bucketing by $h^{1,1}$

Where row sizes scale strongly with $h^{1,1}$ (e.g. triple intersection tensors are $O(h^3)$), data is sub-bucketed by $h^{1,1}$ (directories named h11_{N}/). This keeps small-$h^{1,1}$ users from downloading large-$h^{1,1}$ data, and vice versa. Flat splits (small, uniform rows) are not bucketed.

Adaptive shard sizing

For large buckets (e.g. conifolds at high $h^{1,1}$ with millions of rows), shard sizes are chosen adaptively to target ≈ 30 files per bucket, clamped to $[500,; 50,000]$ rows. See each sub-dataset's card for specifics.

Mirror convention

Catalogues store h11 and h12 in catalogue convention (typically small h11, large h12). JAXVacua works in the mirror convention (the two are swapped). Use stringforge.lcs_database.LCSDatabase — which inherits from CYDatabase — when working with mirror-convention models; it transparently swaps the two columns at the boundary.

Loading without stringforge

All sub-datasets are plain Parquet and can be read with any compatible tool:

import pandas as pd
from huggingface_hub import hf_hub_download

catalog_path = hf_hub_download(
    repo_id="aschachner/cy-database",
    filename="tdf/catalog.parquet",
    repo_type="dataset",
)
catalog = pd.read_parquet(catalog_path)

Each catalogue contains (shard_id, row_index) pointers into the sub-dataset's data splits, so you can resolve individual rows by path construction. See each sub-dataset card for the catalogue schema and resolved path templates.

Versioning and rebuilds

Builds are incremental: unchanged models (tracked by SHA-256 hash of their source files) are skipped, and only new or changed models are appended. Major layout changes bump SCHEMA_VERSION in stringforge/cy_io.py.

Scope and limitations

  • Data is precomputed; not all fields are present for every model. Use has_gv=True, has_conifolds=True, etc. to filter in query().
  • Catalogues use pandas nullable Int64 for optional shard pointers; consumers that do not support nullable integers should cast or drop missing rows.
  • Sub-datasets are independent: different constructions live in separate top-level directories and use different identifier schemes.

Citation

If you use this dataset, please cite:

@article{XXX
}

Licence

GPL-3.0, matching the stringforge and jaxvacua libraries.

Contact

Issues, questions, and contributions: https://github.com/AndreasSchachner/stringforge/issues.

Downloads last month
456