The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

normfluodbf: Cleans and Normalizes FLUOstar DBF and DAT Files from 'Liposome' Flux Assays

Cleans and Normalizes FLUOstar DBF and DAT Files obtained from liposome flux assays. Users should verify extended usage of the package on files from other assay types.

Version: 2.0.0
Depends: R (≥ 4.3.0)
Imports: shiny, data.table, foreign (≥ 0.8.86), tidyr (≥ 1.3.1), tibble, dplyr (≥ 1.1.4), emojifont, stats, ggplot2 (≥ 3.5.0), badger, stringr, magrittr (≥ 2.0.3), assertthat, forcats, gridExtra, pkgsearch, plotly (≥ 4.10.4), purrr (≥ 1.0.2), rlang (≥ 1.1.3), rstudioapi, wesanderson, hexSticker, testthat (≥ 3.2.1)
Suggests: knitr, learnr, rmarkdown
Published: 2024-09-27
DOI: 10.32614/CRAN.package.normfluodbf
Author: Tingwei Adeck ORCID iD [aut, cre, cph], Tesla Adeck [cph], Amina Adeck [cph]
Maintainer: Tingwei Adeck <awesome.tingwei at outlook.com>
BugReports: https://github.com/AlphaPrime7/normfluodbf/issues
License: MIT + file LICENSE
URL: https://github.com/AlphaPrime7/normfluodbf, https://alphaprime7.github.io/normfluodbf/
NeedsCompilation: no
Materials: README NEWS
CRAN checks: normfluodbf results

Documentation:

Reference manual: normfluodbf.pdf
Vignettes: normfluodbf (source, R code)
test_file (source, R code)

Downloads:

Package source: normfluodbf_2.0.0.tar.gz
Windows binaries: r-devel: normfluodbf_2.0.0.zip, r-release: normfluodbf_2.0.0.zip, r-oldrel: normfluodbf_2.0.0.zip
macOS binaries: r-release (arm64): normfluodbf_2.0.0.tgz, r-oldrel (arm64): normfluodbf_2.0.0.tgz, r-release (x86_64): normfluodbf_2.0.0.tgz, r-oldrel (x86_64): normfluodbf_2.0.0.tgz
Old sources: normfluodbf archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=normfluodbf to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.