Spaces:
Running
Running
deploy space from main (post-cleanup library)
Browse files- README.md +5 -5
- __pycache__/app.cpython-313.pyc +0 -0
- __pycache__/app.cpython-314.pyc +0 -0
README.md
CHANGED
|
@@ -13,7 +13,7 @@ pinned: false
|
|
| 13 |
**Intent.** A Hugging Face Docker Space that runs ProcGrep server-side: it ingests a
|
| 14 |
trajectory dataset, canonicalizes it into an action vocabulary, and answers structural
|
| 15 |
queries over the **whole** dataset, not a fixed sample. Read this when changing the live
|
| 16 |
-
explorer or its hosting. The static, embedded-data version lives in
|
| 17 |
`docs/explorer/`; this Space is the version that scales past the embed's size limit.
|
| 18 |
|
| 19 |
## Why a Space and not just the static page
|
|
@@ -21,7 +21,7 @@ explorer or its hosting. The static, embedded-data version lives in the paper re
|
|
| 21 |
The static explorer embeds every trace's atom spine in the HTML, so it is bounded by page
|
| 22 |
weight (a few hundred traces per dataset) and ships only datasets pre-profiled offline.
|
| 23 |
A Space has a backend, so it can load full datasets on demand and ingest any HF set. It also
|
| 24 |
-
runs on HF infrastructure, where reading HF datasets is fast
|
| 25 |
times out elsewhere is not a problem here.
|
| 26 |
|
| 27 |
## Design decisions (benefit / price)
|
|
@@ -38,9 +38,9 @@ times out elsewhere is not a problem here.
|
|
| 38 |
|
| 39 |
## Endpoints
|
| 40 |
|
| 41 |
-
- `GET /`
|
| 42 |
-
- `GET /datasets`
|
| 43 |
-
- `POST /query`
|
| 44 |
mix, and a sample of matched traces.
|
| 45 |
|
| 46 |
## Run locally
|
|
|
|
| 13 |
**Intent.** A Hugging Face Docker Space that runs ProcGrep server-side: it ingests a
|
| 14 |
trajectory dataset, canonicalizes it into an action vocabulary, and answers structural
|
| 15 |
queries over the **whole** dataset, not a fixed sample. Read this when changing the live
|
| 16 |
+
explorer or its hosting. The static, embedded-data version lives in this repo at
|
| 17 |
`docs/explorer/`; this Space is the version that scales past the embed's size limit.
|
| 18 |
|
| 19 |
## Why a Space and not just the static page
|
|
|
|
| 21 |
The static explorer embeds every trace's atom spine in the HTML, so it is bounded by page
|
| 22 |
weight (a few hundred traces per dataset) and ships only datasets pre-profiled offline.
|
| 23 |
A Space has a backend, so it can load full datasets on demand and ingest any HF set. It also
|
| 24 |
+
runs on HF infrastructure, where reading HF datasets is fast: the parquet streaming that
|
| 25 |
times out elsewhere is not a problem here.
|
| 26 |
|
| 27 |
## Design decisions (benefit / price)
|
|
|
|
| 38 |
|
| 39 |
## Endpoints
|
| 40 |
|
| 41 |
+
- `GET /`: the query frontend.
|
| 42 |
+
- `GET /datasets`: suggested datasets + which are warm in cache.
|
| 43 |
+
- `POST /query`: `{dataset, pattern}` → match count, per-model rates, matched-vs-all action
|
| 44 |
mix, and a sample of matched traces.
|
| 45 |
|
| 46 |
## Run locally
|
__pycache__/app.cpython-313.pyc
CHANGED
|
Binary files a/__pycache__/app.cpython-313.pyc and b/__pycache__/app.cpython-313.pyc differ
|
|
|
__pycache__/app.cpython-314.pyc
ADDED
|
Binary file (34.3 kB). View file
|
|
|