Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.7%) to scientific vocabulary
Keywords
Repository
Python CLI for alignment-free genomics.
Basic Info
- Host: GitHub
- Owner: MatthewRalston
- License: apache-2.0
- Language: Python
- Default Branch: main
- Homepage: https://matthewralston.github.io/kmerdb
- Size: 59.8 MB
Statistics
- Stars: 12
- Watchers: 1
- Forks: 1
- Open Issues: 24
- Releases: 33
Topics
Metadata Files
README.md
README - kmerdb
Python CLI and module for k-mer profiles, similarities, and graph files
NOTE: Beta-stage .bgzf and zlib compatible k-mer count vectors and DeBruijn graph edge-list formats.
Development Status
Summary
kmerdb is a Python CLI designed for k-mer counting and k-mer graph edge-lists. It addresses the 'k-mer' problem (substrings of length k) in a simple and performant manner. It stores the k-mer counts in a columnar format (input checksums, total and unique k-mer counts, nullomers, mononucleotide counts) with a YAML formatted metadata header in the first block of a bgzf formatted file.
- [ x ] Homepage:
- [ x ] Quick Start guide
- [ x ]
kmerdb usage subcommand_nameprofile- Make k-mer count vectors/profiles, calculate unique k-mer counts, total k-mer counts, nullomer counts. Import to read/write NumPy arrays from profile object attributes.graph- Make a weighted edge list of kmer-to-kmer relationships, akin to a De Bruijn graph.minimizers- Generate minimizers in a plain-text format from input sequences.alignment- Generate Smith-Waterman alignment (not yet functional)usage- Display verbose input file/parameter and algorithm details of subcommands.help- Display verbose input file/parameter and algorithm details of subcommands.view- View .tsv count/frequency vectors with/without preamble.header- View YAML formatted header and aggregate countsmatrix- Collate multiple profiles into a count matrix for dimensionality reduction, etc.kmeans- k-means clustering on a distance matrix via Scikit-learn or BioPython with kcluster distanceshierarchical- hierarchical clustering on a distance matrix via BioPython with linkage choicesdistance- Distance matrices (from kmer count matrices) including SciPy distances, a Pearson correlation coefficient implemented in Cython, and Spearman rank correlation included as additional distances.index- Create an index file for the kmer profile (Delayed:)shuf- Shuffle a k-mer count vector/profile (Delayed:)version- Display kmerdb version numbercitation- Silence citation suggestion
- [ x ]
kmerdb subcommand -h|--help
k-mer counts from .fa(.gz)/.fq(.gz) sequence data can be computed and stored for access to metadata and count aggregation faculties. For those familiar with .bam, a view and header functions are provided. This file is compatible with zlib.
Install with pip install kmerdb
Please see the Quickstart guide for more information about the format, the library, and the project.
Usage
```bash
Usage --help option --debug mode
kmerdb --help # [+ --debug mode] kmerdb usage profile
+
[ 3 main features: ] [ 1. - k-mer counts ]
Create a [composite] profile of k-mer counts from sequence files. (.fasta|.fastq|.fa.gz|.fq.gz)
kmerdb profile -vv -k 8 --output-name sample1 sample1rep1.fq.gz [sample1_rep2.fq.gz]
Creates k-mer count vector/profile in sample_1.8.kdb. This is the input to other steps, including count matrix aggregation. --minK and --maxK options can be specified to create multiple k-mer profiles at once.
De Bruijn graphs (not a main feature yet, delayed)
Build a weighted edge list (+ node ids/counts = De Bruijn graph)
kmerdb graph -vv -k 12 example1.fq.gz example2.fq.gz edges_1.kdbg
View k-mer count vector
kmerdb view profile_1.8.kdb # -H for full header
Note: zlib compatibility
zcat profile_1.8.kdb
View header (config.py[kdbmetadataschema#L84])
kmerdb header profile_1.8.kdb
[ 3 main features: ] [ 2. Optional normalization, PCA/tSNE, and distance metrics ]
K-mer count matrix - Cython Pearson coefficient of correlation [ ssxy/sqrt(ssxx*ssyy) ]
kmerdb matrix from *.8.kdb | kmerdb distance pearson STDIN
kmerdb matrix -vv DESeq2 *.8.kdb
kmerdb matrix -vv PCA *.8.kdb
kmerdb matrix -vv tSNE *.8.kdb
# just makes a k-mer count matrix from k-mer count vectors.
Distances on count matrices [ SciPy ] pdists + [ Cython ] Pearson correlation, scipy Spearman and scipy correlation pdist calculations are available ]
kmerdb distance -h
usage: kmerdb distance [-h] [-v] [--debug] [-l LOG_FILE] [--output-delimiter OUTPUT_DELIMITER] [-p PARALLEL] [--column-names COLUMN_NAMES] [--delimiter DELIMITER] [-k K]
{braycurtis,canberra,chebyshev,cityblock,correlation,cosine,dice,euclidean,hamming,jaccard,jensenshannon,kulsinski,mahalanobis,matching,minkowski,pearson,rogerstanimotorusselrao,seuclidean,sokalmichener,sokalsneath,spearman,sqeuclidean,yule} [ ...]
[ 3 main features: ] [ 3. Clustering: k-means and hierarchical with matplotlib ]
Kmeans (sklearn, BioPython)
kmerdb kmeans -vv -k 4 -i dist.tsv
BioPython Phylip tree + upgma
kmerdb hierarchical -vv -i dist.tsv
```
Usage example

Installation
OSX and Linux release:
sh
pip install kmerdb
Optional DESeq2 normalization
DESeq2 is an optional R dependency for rpy2-mediated normalization. Make sure development libraries are installed from the repository.
pip install -r requirements-dev.txt
Next, install DESeq2 via bioconductor.
```r
if (!requireNamespace("BiocManager", quietly = TRUE))
install.packages("BiocManager")
BiocManager::install("DESeq2") ```
IUPAC support:
bash
kmerdb profile -k $k -o output input.fa # This simply discards non-IUPAC characters.
IUPAC residues (ATCG+RYSWKM+BDHV) are kept throughout the k-mer counting. But non-IUPAC residues (N) and characters are trimmed from the sequences prior to k-mer counting. Non-standard IUPAC residues are counted as doublets or triplets.
Documentation
Check out the main webpage and the Readthedocs documentation, with examples and descriptions of the module usage.
Important features to usage that may be important may not be fully documented as the project is in beta.
For example, the IUPAC treatment is largely custom, and does the sensible thing when ambiguous bases are found in fasta files, but it could use some polishing. For example, the 'N' residue rejection creates gaps in the k-mer profile from the real dataset by admittedly ommitting certain k-mer counts.
This is one method for counting k-mers and handling ambiguity. Fork it and play with it a bit.
Also, the parallel handling may not always be smooth, if you're trying to load dozens of 12+ mer profiles into memory. This would especially matter in the matrix command, before the matrix is generated. You can use single-core if your machine can't collate that much into main memory at once, depending on how deep the fastq dataset is. Even when handling small-ish k-mer profiles, you may bump into memory overheads rather quickly.
Besides that, I'd suggest reading the source, the differente elements of the main page or the RTD documentation.
Minimum-viable product Documentation
Problem statement:
Calculate relevant metadata from k-mer profiles, manipulate count matrices and distance matrices on inter-species inter-profile distances, perform exploartory analysis using tools such as UPGMA hierarchical clustering, k-means clustering, PCA, and others.
Currently unsupported but targeted features include regression modeling, strassen multiplication, NumPy CPU multipication option, least squares and associated regression code.
Currently in-progress is the application note. I wouldn't mind ironing out a few more components of the program for the application note.
Target audience:
Biologists and researchers using metagenomics and genomics tools for the assessment of inter-genomic distances, k-mer counts, nullomer counts, unique counts, and other metadata.
Feature prioritization:
Features currently implemented in kmerdb include:
- [x] k-mer counting and profile generation
- [x] multiplexed profiles
- [x] De Bruijn graph structures
- [x] Count aggergation and normalization (DESeq2)
- [x] PCA
- [x] t-Stochastic Neighbor Embedding
- [x] Cython Pearson correlation coefficient
- [x] Other correlation coefficients (Spearman, Pearson via scipy)
- [x] hierarchical clustering
- [x] k-means clustering
- [x] data pipelining (Unix pipelines)
Features currently under consideration include:
- [ ] regression modeling for metagenomnic populations
- [ ] alternative k-mer count vector distances
- [ ] alignment using k-mers as seed regions
- [ ] De Bruijn graph traversals and contig generation using DBA (De Bruijn graph) assembly
Success Criteria:
Technical specifications:
User stories:
Development timeline:
2/24 - 6/24 v0.7.7+ - appmap, De Bruijn parser, other updates
10/23 -
Testing and quality assurance plan:
Feedback collection strategy:
Development
https://matthewralston.github.io/kmerdb/developing
bash
python setup.py test
License
Created by Matthew Ralston - Scientist, Programmer, Musician - Email
Distributed under the Apache license. See LICENSE.txt for the copy distributed with this project. Open source software is not for everyone, and im the author and maintainer. cheers, on me. You may use and distribute this software, gratis, so long as the original LICENSE.txt is distributed along with the software. This software is distributed AS IS and provides no warranties of any kind.
``` Copyright 2020 Matthew Ralston
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ```
Contributing
- Fork it (https://github.com/MatthewRalston/kmerdb/fork)
- Create your feature branch (
git checkout -b feature/fooBar) - Commit your changes (
git commit -am 'Add some fooBar') - Push to the branch (
git push origin feature/fooBar) - Create a new Pull Request
Acknowledgements
Thanks mom and dad and my hometown, awesome hs, and the University of Delaware faculty for support and encouragement. Thanks to my former mentors, bosses, and coworkers. It's been really enjoyable anticipating what the metagenomics community might want from a tool that can handle microbial k-mers well.
Thank you to the authors of kPAL and Jellyfish for the inspiration and bit shifting trick. And thank you to others for the encouragement along the way, who shall remain nameless.
The intention is that more developers would want to add functionality to the codebase or even just utilize things downstream, but to build out directly with numpy and scipy/scikit as needed to suggest the basic infrastructure for the ML problems and modeling approaches that could be applied to such datasets. This project began under GPL v3.0 and was relicensed with Apache v2. Hopefully this project could gain some interest. I have so much fun working on this project. There's more to it than meets the eye. I'm working on a preprint, and the draft is included in some of the latest versions of the codebase, specifically .Rmd files.
More on the flip-side. It's so complex with technology these days...
Owner
- Name: Matt Ralston
- Login: MatthewRalston
- Kind: user
- Location: Newark, DE
- Company: MS Data Science Student
- Website: http://matthewralston.github.io
- Twitter: TheWaterAndWind
- Repositories: 73
- Profile: https://github.com/MatthewRalston
Hi, I'm new to OSS and like to code. I'm a bioinformatics data science studying data science for my second masters. Check out my website for more info.
Citation (CITATION_FAQ.md)
== Citation FAQ == - Why does kmerdb show a citation notice? Kmerdb is indirectly funded through citations. Kmerdb is funded by me having a paid job that allows for maintaining Kmerdb. This is much easier to get if kmerdb is cited in scientific journals, and history has shown that researchers forget to do this if they are not reminded explicitly. It is therefore important for the long-term survival of Kmerdb that it is cited. The citation notice makes users aware of this. See also: https://lists.gnu.org/archive/html/parallel/2013-11/msg00006.html - Is the citation notice compatible with Apache? Apparently so, because this citation notice is not part of the license, but part of our academic tradition. Therefore the notice is not adding a term that would require citation as mentioned on: https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation - Do automated scripts break if the notice is not silenced? No. Not a single time has that happened. This is due to the notice only being printed, if the output is to the screen - not if the output is to a file or a pipe. - How do I silence the citation notice? Run this once: kmerdb citation It takes less than 10 seconds to do and is thus comparable to an 'OK. Do not show this again'-dialog box seen in Firefox and similar programs. It is even optional to run this, as kmerdb will work without having 'kmerdb citation' run first (in other words it is _not_ comparable to a clickwrap license, that must be accepted before the program will run). However, not running it does not change that academic tradition requires you to cite in scientific articles. That tradition requires you to cite even if there had been no notice. > I do not write scientific articles. Does the notice apply to me? I suspect that you do, if you know what a k-mer does or what it means enough to look into this library. If not, then you need to acknowledge my work. It doesn't need to fit my citation style, but it needs to be a credible reference to the public, acknowledging this work and its timing. But yes, the notice is only relevant if you write scientific articles. > What shows citing software is an academic tradition? These links say: Yes, you should cite software, and if the author suggests a way of citing, use that. * https://blog.apastyle.org/apastyle/2015/01/how-to-cite-software-in-apa-style.html * https://libguides.mit.edu/c.php?g=551454&p=3900280 * https://www.software.ac.uk/how-cite-software * https://aut.ac.nz.libguides.com/APA6th/software * https://libguides.rgu.ac.uk/c.php?g=380081&p=2983956 * https://journals.aas.org/policy-statement-on-software/ * https://guides.lib.monash.edu/c.php?g=219786&p=1454293 * https://www.maxqda.com/how-to-cite-maxqda If you feel the benefit from using kmerdb is too small to warrant a citation, then prove that by simply using another tool. If you replace your use of 'GNU Parallel' aka kmerdb with another tool, you obviously do not have to cite kmerdb. If it is too much work replacing the use of GNU Parallel, then it is a good indication that the benefit is big enough to warrant a citation. > Do other software tools show how to cite? Here are other examples of software showing how to cite. Some of these refer to peer-reviewed articles - others do not: * https://www.scipy.org/citing.html * https://octave.org/doc/interpreter/Citing-Octave-in-Publications.html (Octave has citation for individual packages, too) * https://stat.ethz.ch/pipermail/r-help/2008-May/161481.html * https://stat.ethz.ch/R-manual/R-devel/library/utils/html/citation.html (R has citation for individual packages, too) * http://www.partek.com/citing-partek-software-in-a-publication/ * http://www.fluortools.com/misc/cite * https://www.maxqda.com/how-to-cite-maxqda * https://www.open-mpi.org/papers/ * https://www.tensorflow.org/about/bib * http://www.fon.hum.uva.nl/paul/praat.html > I do not like the notice. Can I fork kmerdb and remove it? Technically... well, anyways. Kmerdb is released under the Apache license and that means that its attribution and the patent right both belong to me. The LICENSE provision clearly states that you are entitled to a copy of the software under the provisions of the Apache license. This notice in the citation FAQ does not represent additional licensing terms. I am merely stating that the citation term will remain in the program and development is not going in that direction. At this time I am the only developer that has even downloaded the code. I will continue to cite the resources used in this archive and I must admit that most of this citation notice comes directly from GNU parallels. I was looking for their citation for my preprint since I have used them so much but published so little, I wanted to make sure they were in my first article and even my first preprint. (continuing to imitate the GNU parallels citation faq) You have to make sure that your forked version cannot be confused with the original, so for one thing you cannot call it anything similar to kmerdb as that would cause confusion between your forked version and the original. Also documentation cannot be confused with the documentation for kmerdb. This principle has even been tested in court: http://www.inta.org/INTABulletin/Pages/GERMANYGeneralPublicLicenseDoesNotPermitUseofThird-PartyTrademarksforAdvertisingModifiedVersionsofOpen-SourceSoftware.aspx https://www.admody.com/urteilsdatenbank/cafe6fdaeed3/OLG-Duesseldorf_Urteil_vom_28-September-2010_Az_I-20-U-41-09 Also know that if you fork kmerdb and remove the notice, you are not helping to fund further develpment and you could be moving in a direction that may violate the terms of the Apache license. So if you like kmerdb and want to really see the project grow, then please, invest in kmerdb in an honest way and do not take this academic citation notice as abuse. > How important is the notice for the survival of kmerdb <!-- My last $50 after making too many "good" friends in St. Louis was given to Spectrum, --> <!-- to pay for the internet that got me paid during the pandemic. I have invested my last savings into a --> <!-- Threadripper upgrade for my PC, and I might be going back to school. I have some real need. --> Citations mean the world to me and thanks to all my supporters. I hope anyone who read this far, knows that community resources means the world to me, and I really hope some day I'll have a few people who eagerly want more features and can facillitate discussion with other academics in the areas that I've highlighted as foci. <!-- Citations means respect, friendliness, and cheer in my life when others can look at me as capable in the academy. --> <!-- Even outside the academy reputation is everything and an extra citation means the world. If publish or perish was a 'thing' even before the PhD glut, then it means it even more now, especially for researchers like myself who have not completed their doctorate. --> Before the citation notice was implemented hardly anyone cited kmerdb. And that's cause there was nothing to cite! Actually they could technically use internet resource citing but you have to look it up everytime because most academicians provide their citation information directly. (continuing...) Funding development aligns well with "We will give back to the free software community" and "To accelerate innovation and underpin operations". Therefore it is more important to keep the notice than to be included in different distributions. Specifically, it will be preferable to be moved from Github to the AUR, but I don't nearlly have enough users to get to my kinfolk out there. **In other words: It is preferable having fewer users, who all know they should cite, over having many users, who do not know they should cite.** If the goal had been to get more users, then the license would have been public domain. This is because a long-term survival with funding is more important than short-term gains in popularity that can be achieved by being distributed as part of a distribution. - Is there another way I can get rid of the citation notice? Yes. Find a way to finance future development of kmerdb. If you pay me a normal salary, I will be happy to remove the citation notice. The citation notice is about (indirect) funding - nothing else. - I do not think it is fair having to cite If the inconvenience of having to cite is too big for you, then you should use another tool. If you do not want to help fund GNU Parallel, then you will not be a happy GNU Parallel user, and thus you using another tool is the best solution for all parties. Here is a list of parallelizing tools to help you find an alternative: https://www.gnu.org/software/parallel/parallel_alternatives.html - I do not want to run 'kmerdb citation' If the inconvenience of running 'kmerdb citation' one single time after installing GNU Parallel is too big, then you do not have to do it. You only need to do that if you do not want to see the citation notice. But it really only takes 10 seconds to run. - I do not want to see the citation notice at every run You do not have to. Spend 10 seconds on running 'kmerdb citation' and the notice is silenced. This is similar to clicking 'OK. Do not show this again' in a dialog box seen in Firefox and similar programs. If GNU Parallel does not save you more than 10 seconds, then you should probably not be using it anyway. - I do not want to help finance the development If you care so little about kmerdb that you do not want to help finance development, then you should contemplate whether GNU Parallel is really the right tool for you. It is, however, doable (e.g. by forking and changing the code). But you will be going against the wishes of the author, because you make it harder to make a living, thus you will be making it harder to justify producing more free software. If you like GNU Parallel and want to see it maintained in the future, then this is not the way to go. Maybe it is you Nadia Eghbal addresses in https://www.slideshare.net/NadiaEghbal/consider-the-maintainer: **"Is it alright to compromise, or even deliberately ignore, the happiness of maintainers so we that can enjoy free and open source software?"** Thanks again for the citation notice faq GNU parallels. https://www.youtube.com/watch?v=9QRXtA4I8aQ&list=PLg9oy-P5Ts1_j15203blhIQ1twe7OCvOw
GitHub Events
Total
- Create event: 12
- Issues event: 12
- Release event: 5
- Delete event: 3
- Issue comment event: 25
- Push event: 55
- Pull request event: 5
Last Year
- Create event: 12
- Issues event: 12
- Release event: 5
- Delete event: 3
- Issue comment event: 25
- Push event: 55
- Pull request event: 5
Committers
Last synced: almost 3 years ago
All Time
- Total Commits: 154
- Total Committers: 2
- Avg Commits per committer: 77.0
- Development Distribution Score (DDS): 0.006
Top Committers
| Name | Commits | |
|---|---|---|
| MatthewRalston | m****9@g****m | 153 |
| dependabot[bot] | 4****]@u****m | 1 |
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 107
- Total pull requests: 51
- Average time to close issues: 3 months
- Average time to close pull requests: 2 months
- Total issue authors: 1
- Total pull request authors: 2
- Average comments per issue: 0.92
- Average comments per pull request: 0.24
- Merged pull requests: 37
- Bot issues: 0
- Bot pull requests: 17
Past Year
- Issues: 4
- Pull requests: 3
- Average time to close issues: about 24 hours
- Average time to close pull requests: N/A
- Issue authors: 1
- Pull request authors: 1
- Average comments per issue: 0.75
- Average comments per pull request: 0.33
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 3
Top Authors
Issue Authors
- MatthewRalston (107)
Pull Request Authors
- MatthewRalston (34)
- dependabot[bot] (17)
Top Labels
Issue Labels
Pull Request Labels
Packages
- Total packages: 1
-
Total downloads:
- pypi 189 last-month
- Total dependent packages: 0
- Total dependent repositories: 1
- Total versions: 62
- Total maintainers: 1
pypi.org: kmerdb
Yet another k-mer counter for Genomics, Metagenomics, and Phylogenomics applications...
- Homepage: https://github.com/MatthewRalston/kmerdb
- Documentation: https://kmerdb.readthedocs.io/
- License: Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2020 Matthew Ralston Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-
Latest release: 0.9.5
published 7 months ago
Rankings
Maintainers (1)
Dependencies
- Cython ==0.29.26 development
- auditwheel ==5.1.2 development
- coverage ==4.5.4 development
- expects ==0.9.0 development
- ghstats ==1.2.0 development
- ipykernel ==5.1.4 development
- ipython ==7.16.3 development
- ipython-genutils ==0.2.0 development
- ipywidgets ==7.5.1 development
- jedi ==0.16.0 development
- jupyter ==1.0.0 development
- jupyter-client ==6.0.0 development
- jupyter-console ==6.1.0 development
- jupyter-core ==4.6.3 development
- mamba ==0.10 development
- memory-profiler ==0.57.0 development
- pytest ==5.3.5 development
- PyYAML ==6.0
- biopython ==1.79
- boto3 ==1.20.25
- botocore ==1.23.25
- cython ==0.29.26
- distlib ==0.3.4
- docutils ==0.17
- jsonschema ==4.3.2
- matplotlib ==3.5.1
- numpy ==1.21.5
- pandas ==1.3.5
- psutil ==5.8.0
- rpy2 ==3.4.2
- s3transfer ==0.5.0
- scipy ==1.7.3
- sklearn ==0.0
- sphinx ==4.3.2
- sphinx-rtd-theme ==1.0.0
- sphinxcontrib-htmlhelp ==2.0.0
- sphinxcontrib-serializinghtml ==1.1.5
- actions/checkout v2 composite
- actions/setup-python v2 composite
- PyYAML >=6.0
- biopython >=1.79
- cython >=0.29.26
- distlib >=0.3.4
- jsonschema >=4.17.3
- matplotlib >=3.6.2
- numpy >=1.22.0
- pandas >=1.3.5
- psutil >=5.9.4
- rpy2 >=3.5.6
- scikit-learn >=1.4.0
- scipy >=1.9.3