Spaces:
Running on Zero
Running on Zero
Commit History
-
RootScope v4: manuscript model (LightGBM per round, 3 seeds, layer + soft-neighbor context, radial prior) Running
Verified signaturef2ba8d3 -
RootScope v4: manuscript model (LightGBM per round, 3 seeds, layer + soft-neighbor context, radial prior)
Verified signature80d8541 -
RootScope v4: manuscript model (LightGBM per round, 3 seeds, layer + soft-neighbor context, radial prior)
Verified signaturebb112f6
-
README: author name
Verified signature25804b7 -
README + UI text: simplify, single author
Verified signature644f141 -
README: drop the v2 env-variable note
Verified signaturef0e51ca -
RootScope v4: manuscript model (LightGBM per round, 3 seeds, layer + soft-neighbor context, radial prior)
Verified signature322ebce -
RootScope v4: manuscript model (LightGBM per round, 3 seeds, layer + soft-neighbor context, radial prior)
Verified signature47c4bf8
-
Serve the v2 model: fetch meta.json with the backbone, size the GPU reservation for ViT-B
Verified signaturea0d265c -
Serve the v2 model: fetch meta.json with the backbone, size the GPU reservation for ViT-B
Verified signaturec599bae
-
Widen the segmentation reservation margin after measuring a cold start
Verified signatured217dfe -
Ask ZeroGPU for realistic durations so signed-out visitors can run
Verified signatureThe old 150 s floor was calibrated off CPU timings and exceeded the 120 s daily quota a signed-out visitor has, so every such request was refused before the function ran. Measured on the Space: segmentation 20 s and embeddings 8 s for a 700x700 image. New formulas sit ~2x above that and cap at 100 s. Refusals now surface in plain language, and the page states the per-visitor budget.1a448c2 -
Cut the README down to what a maintainer needs
Verified signature86b8f4e -
Replace em and en dashes with ordinary punctuation
Verified signature960f984 -
Hide the Diagnostics panel from visitors
Verified signatureIt is a developer tool. Kept in the file behind ROOTSCOPE_DIAGNOSTICS=1 rather than deleted, since it is what identified the XGBoost/ZeroGPU conflict. Also corrects the stale comment blaming that abort on module-level CUDA loading.08b694d -
Use the description verbatim, no emphasis, no lead-in
Verified signature20ff4d8 -
Rewrite the page description
Verified signature51f840a -
Drop the Notes block from the page
Verified signature4ab321e -
Retitle to match the model card; expand the description
Verified signatureTitle now reads 'RootScope: Cross-species Root Cell-Type Classification from Confocal Microscopy Images', matching MODEL_CARD.md, and the blurb names the nine cell types and the anatomical post-processing step. sdk_version stays at 5.49.1 — what the Space actually runs.7e1fd81 -
Keep every classifier out of the main process (ZeroGPU abort fix)
Verified signatureUnpickling XGBoost builds a Booster that probes for CUDA devices and registers state ZeroGPU's snapshot/restore cannot reproduce, aborting every @spaces.GPU task in that process. Load the classifiers in a subprocess that exits instead. Also take the TIFF path from the File component when the State is empty.acd0294 -
Add CPU-side environment report
Verified signature77d8116 -
Fix ZeroGPU abort: build GPU models lazily, touch no CUDA at import
Verified signaturee250bca -
Diagnostics: test 60s vs 300s reservation
Verified signature81ef57e -
Add step-by-step ZeroGPU diagnostics
Verified signature39cc007 -
Fix: File input preserves the TIFF (Image re-encoded to PNG); raise ZeroGPU cold-start duration
Verified signature4668908 -
RootScope Gradio app (ZeroGPU)
Verified signature73e760d -
initial commit
Verified signature2f68eac