semvec/pypi-packages huggingface dataset:
bayerstraits_16s 1.0.6
Inferring traits by 16S
License: MIT
Keywords: 16S

# bayerstraits_16s
# This is a temp version of bayerstraits_16s
## Introduction
* bayerstraits_16s infers traits by 16S
* input: otu table (-t) and otu sequences (-s)
* requirement: mafft
* Optional: fasttree
![alt text](https://raw.githubusercontent.com/caozhichongchong/bayerstraits_16s/master/Methodology.png)

## Install
`pip install bayerstraits_16s`\
in preparation: `anaconda download caozhichongchong/bayerstraits_16s`

## Test (any of these two commands)
`bayerstraits_16s --test`\
`bayerstraits_16s -t your.otu.table -s your.otu.seqs`

## Availability
in preparation: https://anaconda.org/caozhichongchong/bayerstraits_16s

https://pypi.org/project/bayerstraits_16s

## How to use it
1. test the bayerstraits_16s\
`bayerstraits_16s --test`

2. try your data\
`bayerstraits_16s -t your.otu.table -s your.otu.seqs`\
`bayerstraits_16s -t your.otu.table -s your.otu.seqs -top 2000`\
Warning: please keep the exactly same OTU IDs in your.otu.table and your.otu.seqs! 

3. use your own traits\
`bayerstraits_16s -t your.otu.table -s your.otu.seqs --rs your.own.reference.16s --rt your.own.reference.traits`

* your.own.reference.16s is a fasta file containing the 16S sequences of your genomes\
\>Genome_ID1\
ATGC...\
\>Genome_ID2\
ATGC...

* your.own.reference.traits is a metadata of whether there's trait in your genomes (0 for no and 1 for yes)\
Genome_ID1   0\
Genome_ID1   1

## Results
The result dir of "Bayers_model":
* `filename.infertraits.txt`: the OTUs inferring as butyrate-producing bacteria (1.0, 0.5) 
and non-butyrate-producing bacteria (0.0).
* `filename.infertraits.abu`: the total abundance of butyrate-producing bacteria in all samples.
* `filename.infertraits.otu_table`: the otu_table of butyrate-producing bacteria in all samples.

The result dir of "Filtered_OTU":
* Some temp files of filtered OTUs, alignment, and tree.

## Copyright
Copyright: An Ni Zhang, Prof. Eric Alm, Alm Lab in MIT\
Citation: Not yet, coming soon!\
Contact: anniz44@mit.edu
DisPro 0.1.3
A framework for distributed processing applications
License: MIT
Keywords: dispro distributed processing framework

DisPro: The Distributed Processing Framework
============================================
![PyPI](https://img.shields.io/pypi/v/DisPro.svg)
![GitHub](https://img.shields.io/github/license/cmsteffen-code/DisPro.svg)
![Documentation Status](https://readthedocs.org/projects/dispro/badge/?version=latest)](https://dispro.readthedocs.io/en/latest/?badge=latest)
![GitHub issues](https://img.shields.io/github/issues-raw/cmsteffen-code/DisPro.svg)
![GitHub contributors](https://img.shields.io/github/contributors/cmsteffen-code/DisPro.svg)


The DisPro framework allows you to employ distributed processing in your project by deploying numerous worker nodes across the internet, all controlled by a central master server. DisPro allows you to focus on implementing the unique functionality specific to your project, without having to reinvent the wheel to implement distributed processing.

*Please note, DisPro does not make any assumptions as to the nature of your project, such as data types, databases, front-ends, etc. All of this is left up to the users.*

Core Components
---------------

DisPro implements the two core components required to produce a distributed processing network:

**Worker**

The Worker is the distributed aspect of the DisPro framework, capable of being deployed on remote systems, communicating with the Master in order to request new tasks and transmit the results of its labor.

**Master**

The Master is responsible for the delegation of tasks to each remote Worker, as well as the processing and storage of all returned results. It is managed by the Master.