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.