init empty pkg

.Rbuildignore

+^.*\.Rproj$
+^\.Rproj\.user$
+^LICENSE\.md$

.gitignore

+.Rproj.user
+.Rhistory
+.RData
+.Ruserdata

AUTHORS.R

+Maxime Jaunatre <maxime.jaunatre@inrae.fr>
+Benoit Courbaud <benoit.courbaud@inrae.fr>

DESCRIPTION

+Package: marteloscope
+Title: Report production from marteloscopes with Capsis
+Version: 0.0.0.9999
+Authors@R: c(
+    person("Maxime", "Jaunatre", comment = c(ORCID = "0009-0002-2816-1677"), email = "maxime.jaunatre@inrae.fr", role = c("aut", "cre", "trl")),
+    person("INRAE", role = "cph"),
+    person("Benoit", "Courbaud", comment = c(ORCID = "0000-0002-3050-9559"), email = "benoit.courbaud@inrae.fr", role = "aut")
+  )
+Description: The goal of this package is to help users in using Capsis softawre and compile reports for field workshops.
+    The workshop consist in predicting management effects on forest stand within the capsis platform.
+License: MIT + file LICENSE
+URL: https://forgemia.inra.fr/lessem/marteloscope
+Encoding: UTF-8
+LazyData: true

LICENSE

+YEAR: 2024
+COPYRIGHT HOLDER: maxime jaunatre

LICENSE.md

+# MIT License
+
+Copyright (c) 2024 maxime jaunatre
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

NAMESPACE

+exportPattern("^[[:alpha:]]+")

NEWS.md

+# marteloscope (development version)
+
+
+# marteloscope 0.0.0.9999
+
+* Added a `NEWS.md` file to track changes to the package.
+
+* Packaging functions from [Kunstler *et al* (2020)](https://doi.org/10.1111/1365-2745.13533) under initial name `{treeforce}`.

R/hello.R

+# Hello, world!
+#
+# This is an example function named 'hello' 
+# which prints 'Hello, world!'.
+#
+# You can learn more about package authoring with RStudio at:
+#
+#   http://r-pkgs.had.co.nz/
+#
+# Some useful keyboard shortcuts for package authoring:
+#
+#   Install Package:           'Ctrl + Shift + B'
+#   Check Package:             'Ctrl + Shift + E'
+#   Test Package:              'Ctrl + Shift + T'
+
+hello <- function() {
+  print("Hello, world!")
+}

R/marteloscope.R

+#' marteloscope
+#'
+#' Report production from marteloscopes with Capsis
+#'
+#' The goal of this package is to help users in using Capsis softawre and
+#' compile reports for field workshops.
+#' The workshop consist in predicting management effects on forest stand within
+#' the capsis platform.
+#'
+#' @name marteloscope
+'_PACKAGE'

README.md

+# {marteloscope} 
+<!-- badges: start -->
+[![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#active)
+[![](https://img.shields.io/badge/devel%20version-0.0.0.9999-blue.svg)](https://forgemia.inra.fr/lessem/marteloscope)
+<!-- badges: end -->
+
+The goal of this package is to help users in using Capsis softawre and compile reports for field workshops. The workshop consist in predicting management effects on forest stand within the capsis platform.
+
+## Installation
+
+### Dependencies
+
+This package relies on very few packages listed below, that you can install with the following code.
+
+```
+deps <- c('checkmate', 'cli', 'dplyr', 'here', 'Matrix',
+'purrr', 'rlang', 'statmod', 'stats', 'tidyr')
+for (i in deps ){
+if(!require(i,character.only = TRUE))
+install.packages(i)
+}
+```
+
+### Stable version
+
+<!--
+Be aware that anyone who installs directly from GitHub will need to explicitly request vignettes, e.g. with devtools::install_github(dependencies = TRUE, build_vignettes = TRUE).
+-->
+
+You can install the `{marteloscope}` package from [forgemia](https://forgemia.inra.fr/lessem/marteloscope) with :
+
+```
+# install.packages("remotes")
+remotes::install_git("https://forgemia.inra.fr/lessem/marteloscope")
+```
+
+### Development version
+
+You can install the development version of `{marteloscope}` from github with :
+
+```
+# install.packages("remotes")
+remotes::install_git("https://forgemia.inra.fr/lessem/marteloscope", ref = "dev")
+```
+
+
+**If you install the development version of this package, please check the NEWS.md or [changelog](https://forgemia.inra.fr/lessem/marteloscope-/blob/main/NEWS.md) regularly. The package is in active development and some changes may break your code !**
+
+
+## Support
+
+Issues are centralized on [the forgemia project.](https://forgemia.inra.fr/lessem/marteloscope/-/issues).
+
+
+## License
+
+Project is under MIT Licence.
+
+<!--
+## Suggestions for a good README
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+-->
+

man/hello.Rd

+\name{hello}
+\alias{hello}
+\title{Hello, World!}
+\usage{
+hello()
+}
+\description{
+Prints 'Hello, world!'.
+}
+\examples{
+hello()
+}

marteloscope.Rproj

+Version: 1.0
+
+RestoreWorkspace: Default
+SaveWorkspace: Default
+AlwaysSaveHistory: Default
+
+EnableCodeIndexing: Yes
+UseSpacesForTab: Yes
+NumSpacesForTab: 4
+Encoding: UTF-8
+
+RnwWeave: Sweave
+LaTeX: pdfLaTeX
+
+AutoAppendNewline: Yes
+StripTrailingWhitespace: Yes
+
+BuildType: Package
+PackageUseDevtools: Yes
+PackageInstallArgs: --no-multiarch --with-keep.source