Metadata-Version: 2.1
Name: cactice
Version: 0.0.2
Summary: Computing Agricultural Crop latTICEs
Home-page: https://github.com/Computational-Plant-Science/cactice
Author: Computational Plant Science Lab
Author-email: wbonelli@uga.edu
License: BSD-3-Clause
Description: # cactice
        
        ![CI](https://github.com/Computational-Plant-Science/cactice/workflows/CI/badge.svg)
        [![PyPI version](https://badge.fury.io/py/cactice.svg)](https://badge.fury.io/py/cactice)
        [![Coverage Status](https://coveralls.io/repos/github/Computational-Plant-Science/cactice/badge.svg?branch=main)](https://coveralls.io/github/Computational-Plant-Science/cactice?branch=main)
        
        <!-- START doctoc generated TOC please keep comment here to allow auto update -->
        <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
        
        - [Overview](#overview)
        - [Usage](#usage)
        - [Conventions](#conventions)
        
        <!-- END doctoc generated TOC please keep comment here to allow auto update -->
        
        ## Overview
        
        `cactice` stands for **c**omputing **a**gricultural **c**rop lat**tice**s. This repository explores questions about regular spatial arrangements of plant phenotypes (e.g., in a field or greenhouse). For instance:
        
        - How does environmental context influence morphological development?
        - What mechanisms underlie spatial patterning?
        - Is a given phenotype distribution highly structured or mostly random? In either case, why?
        - If structure is evident, can we formalize or predict it? If so, from which (and how much) information?
        
        **This repository is exploratory, unstable, and currently very minimal.**
        
        ## Usage
        
        Check out the `notebooks/explore.ipynb` notebook for some examples.
        
        ## Conventions
        
        This library makes several assumptions about datasets to which the user must conform:
        
        - Class values are parsed as strings (and mapped internally to integers). Each distinct string is a class, regardless of numeric value: for instance, `9.5` and `9.5000` are considered distinct.
Platform: UNKNOWN
Requires-Python: >=3.6.8
Description-Content-Type: text/markdown
