chromaquant 0.3.1__tar.gz

chromaquant-0.3.1/.gitignore

@@ -0,0 +1,3 @@
+__pycache__
+data
+.DS_Store

chromaquant-0.3.1/CONTRIBUTING.md

@@ -0,0 +1,29 @@
+<h1>Introduction</h1>
+
+Thank you for considering to contribute to the ChromaQuant project! We're super excited to have grabbed your attention. I'm Julia, a research assistant at the University of Washington (UW), Seattle. I'm passionate about sustainability and green chemistry initiatives, and I'm hopeful this project can help with some of those endeavours as well as others. I am also passionate about analytical chemistry and its intersection with data science.
+
+I'm associated with the Rorrer Lab in the Department of Chemical Engineering at UW. You can find more information about our group at https://www.rorrerlab.com!
+
+<h2>Why read these guidelines?</h2>
+
+> I am a huge supporter of collaboration, especially when it comes to academic research. That being said, collaboration depends on predefined expectations and rules. By reading and following these guidelines, you are demonstrating that you respect the work that we do. It is also necessary to get us to address your concerns.
+
+<h2>What contributions are we looking for?</h2>
+
+> ChromaQuant is an open source project for a reason – we want people to both use this project and contribute back to it for an overall improved experience. We are primarily looking for contributions in the form of bug reports and feature recommendations, although writing tutorials and helping others is also encouraged! We are also open to improving our documentation as the project progresses.
+
+<h2>What contributions are we NOT looking for?</h2>
+
+> We are not currently looking for new code at this time. Since this project will be the subject of publications in academic journals, we are looking to maintain control over the exact scripting and functionality of existing code. We are hoping that we'll be able to change this policy in the future, but for the time being please do not initiate pull requests or expect new features to be implemented on a short time scale. Thank you for following this guideline.
+
+<h1>Expectations</h1>
+
+We expect all contributors to adhere to these expectations as well as those outlined in the Code of Conduct:
+
+> 1. Connect with me, Julia, directly using built-in GitHub messaging (or with my personal contact information if we've connected before) before contributing so we can collaborate more effectively. Simple comments or bug reports don't need to follow this rule, although I might reach out for more information!
+> 2. If you make tutorials or other contributions to web information, please let me know so I can integrate/adapt to the information that's out there.
+> 3. Be welcoming to newcomers and encourage diverse new contributors from all backgrounds – further expectations along this line can be found in the Code of Conduct.
+
+<h1>Conclusions</h1>
+
+I'm very excited to watch this project grow and change and similarly excited to get a chance to work with collaborators across different fields and areas of expertise. In advance of a formal publication on this project, we are not looking for new code or pull requests but instead more indirect bug reports and feature recommendations. Tutorials, and documentation recommendations in some cases, are also encouraged. Please reach out to me over built-in GitHub messaging or through my contact info if you have gotten it previously for any questions or requests to connect. Thank you!

chromaquant-0.3.1/LICENSE.txt

@@ -0,0 +1,18 @@
+
+ChromaQuant – A quantification software for complex gas chromatographic data
+
+Copyright (c) 2024, by Julia Hancock
+              Affiliation: Dr. Julie Elaine Rorrer
+	      URL: https://www.rorrerlab.com/
+
+License: BSD 3-Clause License
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.