Tokens
Track, visualize, and compete on AI coding assistant token usage across Claude Code, Cursor, OpenCode, Codex, Gemini, Kimi, and Qwen. The Kardashev Scale for AI Devs.
翻譯準備中
Cell type labels in spatial single-cell data are uncertain, particularly between closely related subtypes. fuzzyCell estimates a per-cell classification confidence by bootstrapping (multinomial resamp
翻譯準備中
資料RGitHub @shreyarajeshrao上線中營運者未確認
試用過了嗎? 點一下就好,不需要登入。
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Cell type labels in spatial single-cell data are uncertain, particularly between closely related subtypes. fuzzyCell estimates a per-cell classification confidence by bootstrapping (multinomial resampling of each cells counts followed by re-classification) and uses the resulting confidences as soft cell type weights. The weights are propagated through downstream analyses: cell type proportions, co-localisation (spicyRs L-function, and Statial's Kontextual test for relative co-localisation) and n
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Cell type labels in spatial single-cell data are uncertain, particularly between closely related subtypes (for example CD4+ and CD8+ T cells), but most downstream analyses treat them as known. fuzzyCell estimates a per-cell classification confidence by bootstrapping (resampling each cell's transcript counts and re-classifying it), and uses the confidences as soft cell type weights in downstream spatial analyses:
Each analysis is run with the original hard labels and with the confidence weights, so the two can be compared, and each can be tested against a sample-level outcome. Cell types are organised with a user-supplied hierarchy of lineages, groups and subtypes.
The development version is on GitHub.
It depends on several Bioconductor packages (for example SpatialExperiment
and Statial), so install it with BiocManager, which installs those
dependencies from Bioconductor:
if (!requireNamespace("BiocManager", quietly = TRUE))
install.packages("BiocManager")
BiocManager::install("shreyarajeshrao/fuzzyCell")
Or, with remotes, which also needs the Bioconductor repositories set:
# install.packages("remotes")
remotes::install_github("shreyarajeshrao/fuzzyCell",
repos = BiocManager::repositories())
fuzzyCell requires R >= 4.5.0. To also build the vignette, add
build_vignettes = TRUE. This needs the Quarto command
line tool, the quarto R package, and the example data package
SpatialDatasets:
BiocManager::install(c("quarto", "SpatialDatasets"))
BiocManager::install("shreyarajeshrao/fuzzyCell", build_vignettes = TRUE)
fuzzyCell is being prepared for Bioconductor. Once it is accepted it will be installed with:
BiocManager::install("fuzzyCell")
library(fuzzyCell)
# heart transplant Xenium biopsies (downloads the data on first use)
spe = loadAmancherla("pre")
data(heartCellTypeTree)
# per-cell confidence for each group of related subtypes
confList = bootstrapLineageConfidence(spe, heartCellTypeTree, nBoot = 50)
# weighted vs unweighted analyses, tested against the outcome
props = runProportionsPipeline(spe, heartCellTypeTree, confList,
outcomeCol = "resolution_broad", subject = "subject")
coloc = runColocalisationModels(spe, heartCellTypeTree, confList,
outcomeCol = "resolution_broad", subject = "subject")
# the weights themselves, to pass to spicyR or lisaClust directly
w = confidenceWeights(spe, heartCellTypeTree, confList)
The input is any SummarizedExperiment (such as a SpatialExperiment) with a
"counts" assay and cellID, imageID, cellType, x and y in its
colData.
See vignette("fuzzyCell") for a full walkthrough.
Please report bugs and requests at https://github.com/shreyarajeshrao/fuzzyCell/issues.
Parts of fuzzyCell (package code, tests, documentation and the vignette) were written with the assistance of Claude (Anthropic), via Claude Code, in line with Bioconductor's AI and third-party code policy. All code has been reviewed and tested by the maintainer, who is responsible for its correctness and maintenance.