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.
Provides a convenient way to log scalars, images, audio, and histograms in the 'tfevent' record file format. Logged data can be visualized on the fly using 'TensorBoard', a web based tool that focuses on visualizing the training progress of machine learning models.
| Version: | 0.0.4 |
| Imports: | Rcpp, withr, fs, rlang (≥ 1.0.0), vctrs, blob, png, digest, cli, zeallot |
| LinkingTo: | Rcpp |
| Suggests: | testthat (≥ 3.0.0), tibble, tidyr, reticulate, rmarkdown, ggplot2, tensorflow, wav |
| Published: | 2024-06-27 |
| DOI: | 10.32614/CRAN.package.tfevents |
| Author: | Daniel Falbel [aut, cre, cph], Posit, PBC [cph], The tl::optional authors [cph] (For the vendored tl::optional code.), Mark Adler [cph] (For the included crc32c code.) |
| Maintainer: | Daniel Falbel <daniel at posit.co> |
| BugReports: | https://github.com/mlverse/tfevents/issues |
| License: | MIT + file LICENSE |
| URL: | https://github.com/mlverse/tfevents, https://mlverse.github.io/tfevents/ |
| NeedsCompilation: | yes |
| SystemRequirements: | libprotobuf, protobuf-compiler |
| Materials: | README NEWS |
| CRAN checks: | tfevents results |
| Reference manual: | tfevents.pdf |
| Package source: | tfevents_0.0.4.tar.gz |
| Windows binaries: | r-devel: tfevents_0.0.4.zip, r-release: tfevents_0.0.4.zip, r-oldrel: tfevents_0.0.4.zip |
| macOS binaries: | r-release (arm64): tfevents_0.0.4.tgz, r-oldrel (arm64): tfevents_0.0.4.tgz, r-release (x86_64): tfevents_0.0.4.tgz, r-oldrel (x86_64): tfevents_0.0.4.tgz |
| Old sources: | tfevents archive |
| Reverse suggests: | luz |
Please use the canonical form https://CRAN.R-project.org/package=tfevents 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.