expDB

R interface for expDB which is used to store experiment-based data.

https://github.com/byzheng/expdb

Science Score: 23.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
    1 of 1 committers (100.0%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (11.0%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

R interface for expDB which is used to store experiment-based data.

Basic Info
  • Host: GitHub
  • Owner: byzheng
  • License: other
  • Language: R
  • Default Branch: master
  • Homepage: https://expdb.bangyou.me/
  • Size: 408 KB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created almost 6 years ago · Last pushed 10 months ago
Metadata Files
Readme Changelog License Code of conduct

README.md

expDB

R-CMD-check CRAN_Status_Badge

R interface for expDB which is used to store experiment-based data.

Installation

Install from CRAN.

r install.packages('rapsimng')

Install the developing version from Github.

r devtools::install_github('byzheng/expdb')

Database design

A SQLite database is used to store all information of experiment-based data.

  • Researchers collect the basic information about researchers, e.g. name, email, etc.
  • ApSoils specify the soil name in the ApSoils which distribute with APSIM.

  • Sites collect the basic information about experiment fields, e.g. name, latitude, longitude, soil, etc. The soil must be the same in the table ApSoils.

  • Met specify the information about weather records, e.g. type and filename. The valid met types include “daily” and “hourly”.

  • Genotypes collect genotype name and other information.

  • Traits collect all information about traits, e.g. name, type, label, unit and description. There aren't limitation of trait names and types. But we normally use crop and soil as trait types.

  • Trials collect basic information about trials, e.g. year, site, trial code (trialcode), sowing, density, depth, row spacing (rowspacing) and researcher and met. Trial code must be unique for expDB. Site should come from table Sites.

  • Design specify the design of each plot, e.g. year, trialcode, site, row (range), column (plot), replicate, block, treatment, genotype, etc. Each plot specifies by year, site, row, column which must be unique. The trialcode is from table Trials, site from table Sites, and genotype from table Genotypes.

  • TrialSoils collect the soil information to some trials, e.g. trial code, bulk density, no3-n, nh4-n, etc.

  • Irrigation collect the irrigation information to some trials, e.g. date, amount, etc.

  • Fertilization collect the fertilization information to some trials, e.g. date, fertilizer, amount, etc.

Import data

The experiment-based data can be imported from a excel file which supports by readxl package. expDB is case-insensitive. The Australia style should be used for all date related fields (dd/mm/yyyy).

Traits

The processes of plant growth and development can be classified into several hierarchical levels, e.g. biosphere, ecosystem or cropping system, field or plot, whole plant, plant organ, cell, molecule, atom, and subatomic particle (Hodges 1991). We could collect data from field, plant, organ in an agricultural experiment. The values in the higher levels can be derived from lower levels. In most cases, we don't directly record data in levels above, but through specific protocol. These observations are used to derive values in other levels. For example, population is converted from the establishment counts; dry weights of leaves, stems, and heads are converted from quadrat harvest. An extra level, measurement is added into the convention.

|Levels | Prefix | Example | |------------|--------|----------------------| |Field | F_ | FStemNumber | |Plant | P | PStemNumber | |Organ | O | OLeafArea | |Measurement | M | M_DryWeightGreenLeaf |

A list of traits are provided in the released version of expDB.

Extraction of observations from datasets

The low level function dbGetPhenotype is provided to extract the raw observations from database. Some traits can be observed or calculated from other traits.

Population

The plant population (F_Population) is defined as the number of plants in unit area. F_Population is retrived from database, then calculated from measurement establishment count (M_EstablishmentCount) and row spacing (RowSpacing). The density is assumed to equal to population if none of above traits are specified in the database.

Final leaf number

Final leaf number (O_FinalLeafNumber) is defined as the total completed leaf number of a fertile stem after head emergence (main stem and tillers). O_FinalLeafNumber is retrived from database, then calculated from Haun Index. Huan Index is assumed the full expanded flag leaf is recorded. Consequently the maximum integer value in the observations is treated as the O_FinalLeafNumber.

Stem/tiller numbers for field and plant

The stem/tiller numbers are defined as the number stems/tillers per unit area and per plant. The relationships among 4 traits are as follows.

$$P_StemNumber = P_TillerNumber + 1$$ $$F_StemNumber = P_StemNumber \times F_Population$$ $$F_TillerNumber = P_TillerNumber \times F_Population$$ $$F_StemNumber = (P_TillerNumber + 1) \times F_Population$$

The stem/tiller numbers are retrived from observations, then calculated by other traits.

Owner

  • Name: Bangyou Zheng
  • Login: byzheng
  • Kind: user

Bangyou is a research scientist at CSIRO. His research interests include crop modelling, crop adaptation, high throughput phenotyp, big data and R programming.

GitHub Events

Total
  • Push event: 3
Last Year
  • Push event: 3

Committers

Last synced: about 2 years ago

All Time
  • Total Commits: 46
  • Total Committers: 1
  • Avg Commits per committer: 46.0
  • Development Distribution Score (DDS): 0.0
Past Year
  • Commits: 5
  • Committers: 1
  • Avg Commits per committer: 5.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Bangyou Zheng b****g@c****u 46
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 0
  • Total pull requests: 1
  • Average time to close issues: N/A
  • Average time to close pull requests: 8 minutes
  • Total issue authors: 0
  • Total pull request authors: 1
  • Average comments per issue: 0
  • Average comments per pull request: 0.0
  • Merged pull requests: 1
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
  • byzheng (1)
Top Labels
Issue Labels
Pull Request Labels

Packages

  • Total packages: 1
  • Total downloads:
    • cran 240 last-month
  • Total dependent packages: 0
  • Total dependent repositories: 1
  • Total versions: 1
  • Total maintainers: 1
cran.r-project.org: expDB

Database for Experiment Dataset

  • Versions: 1
  • Dependent Packages: 0
  • Dependent Repositories: 1
  • Downloads: 240 Last month
Rankings
Dependent repos count: 23.9%
Forks count: 27.8%
Dependent packages count: 28.7%
Average: 33.0%
Stargazers count: 34.6%
Downloads: 49.7%
Maintainers (1)
Last synced: 10 months ago

Dependencies

DESCRIPTION cran
  • DBI * imports
  • RSQLite * imports
  • dplyr * imports
  • grid * imports
  • lubridate * imports
  • magrittr * imports
  • methods * imports
  • png * imports
  • readxl * imports
  • reshape2 * imports
  • rlang * imports
  • stats * imports
  • stringr * imports
  • tibble * imports
  • tidyr * imports
  • tidyverse * imports
  • utils * imports
  • weaana >= 0.1.1 imports
  • testthat * suggests
.github/workflows/R-CMD-check.yaml actions
  • actions/cache v2 composite
  • actions/checkout v2 composite
  • actions/upload-artifact main composite
  • r-lib/actions/setup-pandoc v1 composite
  • r-lib/actions/setup-r v2-branch composite
.github/workflows/pkgdown.yaml actions
  • actions/cache v2 composite
  • actions/checkout v2 composite
  • r-lib/actions/setup-pandoc v2-branch composite
  • r-lib/actions/setup-r v2-branch composite
  • r-lib/actions/setup-tinytex v2-branch composite