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.
Routines to write, simulate, and validate stock-flow consistent (SFC) models. The accounting structure of SFC models are described in Godley and Lavoie (2007, ISBN:978-1-137-08599-3). The algorithms implemented to solve the models (Gauss-Seidel and Broyden) are described in Kinsella and O'Shea (2010) <doi:10.2139/ssrn.1729205> and Peressini and Sullivan (1988, ISBN:0-387-96614-5).
Version: | 0.2.1 |
Imports: | dplyr (≥ 1.0.2), expm (≥ 0.999.5), forcats (≥ 0.5.0), igraph (≥ 1.2.6), kableExtra (≥ 1.3.1), magrittr (≥ 1.5), purrr (≥ 0.3.4), Rdpack (≥ 2.1), rootSolve (≥ 1.8.2.1), rlang (≥ 0.4.7), tibble (≥ 3.0.3), tidyr (≥ 1.1.2), tidyselect (≥ 1.1.0), stringr (≥ 1.4.0), utils, vctrs (≥ 0.3.5), Rcpp (≥ 1.0.5) |
LinkingTo: | Rcpp, RcppArmadillo |
Suggests: | ggraph, ggplot2, grDevices, knitr, pkgdown, rmarkdown, RColorBrewer, testthat (≥ 2.3.2), tidygraph, tidyverse, networkD3 |
Published: | 2021-10-11 |
DOI: | 10.32614/CRAN.package.sfcr |
Author: | Joao Macalos [aut, cre] |
Maintainer: | Joao Macalos <joaomacalos at gmail.com> |
BugReports: | https://github.com/joaomacalos/sfcr/issues |
License: | MIT + file LICENSE |
URL: | https://github.com/joaomacalos/sfcr |
NeedsCompilation: | yes |
Materials: | README NEWS |
CRAN checks: | sfcr results |
Reference manual: | sfcr.pdf |
Vignettes: |
sfcr_multis |
Package source: | sfcr_0.2.1.tar.gz |
Windows binaries: | r-devel: sfcr_0.2.1.zip, r-release: sfcr_0.2.1.zip, r-oldrel: sfcr_0.2.1.zip |
macOS binaries: | r-release (arm64): sfcr_0.2.1.tgz, r-oldrel (arm64): sfcr_0.2.1.tgz, r-release (x86_64): sfcr_0.2.1.tgz, r-oldrel (x86_64): sfcr_0.2.1.tgz |
Old sources: | sfcr archive |
Please use the canonical form https://CRAN.R-project.org/package=sfcr 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.