chromaquant 0.3.1__py3-none-any.whl

chromaquant-0.3.1.dist-info/METADATA

@@ -0,0 +1,189 @@
+Metadata-Version: 2.3
+Name: chromaquant
+Version: 0.3.1
+Summary: Analytical platform for gas chromatography
+Project-URL: Repository, https://github.com/JnliaH/ChromaQuant
+Author: Julia Hancock
+License: 
+        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.
+License-File: LICENSE.txt
+License-File: LICENSES_bundled.txt
+Keywords: Analysis,Analytical Chemistry,Chromatography,Complex Hydrocarbon Analysis,Mass Spectrometry
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Environment :: MacOS X
+Classifier: License :: OSI Approved :: BSD License
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python
+Classifier: Topic :: Scientific/Engineering :: Chemistry
+Requires-Python: >=3.12
+Requires-Dist: chemformula~=1.3.1
+Requires-Dist: molmass~=2024.5.24
+Requires-Dist: numpy~=1.26.4
+Requires-Dist: openpyxl~=3.1.5
+Requires-Dist: pandas~=2.2.2
+Requires-Dist: pillow~=10.3.0
+Requires-Dist: plotly~=5.22.0
+Requires-Dist: pubchempy~=1.0.4
+Requires-Dist: rdkit~=2024.3.5
+Requires-Dist: scipy~=1.13.1
+Requires-Dist: ttkthemes~=3.2.2
+Requires-Dist: xlsxwriter~=3.2.0
+Description-Content-Type: text/markdown
+
+<h1>ChromaQuant</h1>
+<i>A solution for automated gas chromatographic peak assignment and quantification</i>
+
+<h4>Introduction</h4>
+<img style="float: right;" align="right" width="256" alt="ChromaQuant Logo" src="https://github.com/JnliaH/ChromaQuant/blob/rebrand/images/ChromaQuantIcon.png">
+This project aims to simplify the workflow for combining gas chromatography (GC) data collected from multiple sources. More
+specifically, it is designed to accommodate the case where GCs with flame ionization and thermal conductivity detectors are
+used to collect quantitative data that must be labelled using data from mass spectroscopic results. This project assumes the
+following setup:
+<ul>
+  <li>A GC equipped with FID/TCD is used to quantify gaseous products from a reaction</li>
+  <li>A GC equipped with FID/MS is used to quantify liquid products from a reaction</li>
+  <li>A GC equipped with FID/MS is used to label both gas and liquid reaction products</li>
+</ul>
+The GCs mentioned in the second and third bullets are assumed to be the same GC. This project also assumes that external software can be used to obtain spectra and integration/identification results.<br><br>
+
+Relative response factors (or simply "response factors" or RFs from now on) are used to get quantitative data from liquid FID results. These are defined as:
+
+$$RF = \frac{(A_i/A_s)}{m_i/m_s}$$
+
+Where $A_i$ is the Area for the species of interest, $A_s$ is the area of the internal standard, $m_i$ is the mass of the species of interest, and $m_s$ is the mass of the internal standard. In the Rorrer Lab, we use 1,3,5-tri-tert-butylbenzene as an internal standard. Response factors are determined by making solutions (~6) of known concentration across a given concentration range and applying a linear fit. Interpolation/extrapolation is used for cases where response factors are not known using fits determined in the liquid FID RFs Excel sheet. Gas TCD integration values are quantified by using (non-relative) response factors defined as:
+
+$$RF = \frac{Area}{Volume Percent}$$
+
+Quantitative data is then determined by getting a total volume of gas collected by dividing the amount of CO2 (the internal standard) injected by the vol.% CO2. This total volume is then used alongside volume percents for each species of interest and the ideal gas law to determine the quantity of each product. Again, RFs are determined using external calibration gas injections. Gas FID integration is quantified similarly, except the total volume of gas determined in the TCD step is used since CO2 does not show up separately in the FID chromatogram.
+
+<h4>Installation</h4>
+Install ChromaQuant by running the following command in the terminal/command prompt:<br>
+
+> pip install chromaquant
+
+This should install ChromaQuant along with its dependencies. There are several subpackage files used in both manual and automatic analysis that can be imported directly. To start the GUI for automated quantification, run the following command:<br>
+> chroma-ui
+
+or
+
+> python -m chromaquant
+
+<h4>The workflow</h4>
+<p align="center">
+  <img width="498" alt="Analytical workflow diagram demonstrating which files are necessary and which processes they are used in." src="images/workflow.png"><br>
+  <b>Figure 1</b>: ChromaQuant's analytical workflow
+</p>
+
+<h4>Prerequisites</h4>
+As mentioned previously, this workflow assumes you have access to software that can take raw acquisition data files and produce spectra, integration values, and peak labels. Also, since there are duplicate FID signals for gas injections it is assumed you use the signal from the GC-FID/TCD. The files required to fully process analyzed samples are given in <b>Table 1</b>.<br><br>
+
+<div align="center">
+  <b>Table 1</b>: Files required for ChromaQuant<br><br>
+  
+  |           File Name             |                             Description                               |
+  | :-----------------------------: | :-------------------------------------------------------------------: |
+  |[Sample]_[Injection]_LQ1_FID_SPEC| Sample's FID spectra acquired from liquid sample injection            |
+  |[Sample]_[Injection]_LQ1_MS_SPEC | Sample's MS spectra acquired from liquid sample injection             |
+  |[Sample]_[Injection]_LQ1_FID_CSO | Sample's FID integration values acquired from liquid sample injection |
+  |[Sample]_[Injection]_LQ1_UA_UPP  | Sample's FID spectra acquired from liquid sample injection            |
+  |[Sample]_[Injection]_GS1_MS_SPEC | Sample's MS spectra acquired from gas sample injection                |
+  |[Sample]_[Injection]_GS2_FID_SPEC| Sample's FID spectra acquired from gas sample injection               |
+  |[Sample]_[Injection]_GS2_TCD_SPEC| Sample's TCD spectra acquired from gas sample injection               |
+  |[Sample]_[Injection]_GS2_TCD_CSO | Sample's FID spectra acquired from liquid sample injection            |
+  |[Sample]_[Injection]_GS1_UA_UPP  | Sample's FID spectra acquired from liquid sample injection            |
+  |[Sample]_INFO.json               | JSON containing necessary information about the sample                |
+</div>
+
+The FID, MS, and TCD spectra must all be .csv files with no headers and two columns. The first column (again, unlabeled) must represent retention times (in minutes) and the second column must represent the signal at each row's retention time. 
+
+The UA_UPP files must be .csv files that contain the columns "Component RT", "Compound Name", "Formula", and "Match Factor", in no particular order. These files should contain a list of all compounds identified in the MS spectra alongside their MS retention time (min), formula (standard molecular formula format, numbers not expressed as subscripts), and the match factor assigned by the MS interpretation software library search (0-100).
+
+The CSO files must be .csv files that contain the columns "Signal Name", "RT", "Area", and "Height", in no particular order. The LQ1_FID_CSO file should contain a list of all integrated peaks in the FID spectra from liquids analysis, including these peaks retention times, area, and height. The GS2_TCD_CSO file should contain a list of all integrated peaks in the FID and TCD spectra from gas analysis. In the case of LQ1, the signal name should be FID1A for every peak; for GS2, the signal name should be FID1A for the FID peaks and TCD2B for the TCD peaks. This program uses the signal name to distinguish between FID and TCD results for the gas phase analysis – there aren't separate files for these two lists of integration values.
+
+The INFO file must be a .json file containing the following information in the following format. A file version of this .json data is found under the root directory as "empty_INFO.json".
+
+```json
+{
+    "Sample Name":                 "[Sample]_[Injection]",
+    "Reactor Name":                "[Reactor name]",
+    "Catalyst Type":               "[Catalyst name, be as descriptive as possible]",
+    "Catalyst Amount (mg)":        "[Catalyst added to reactor, sum masses if more than one catalyst]",
+    "Plastic Type":                "[Name of substrate added, be as descriptive as possible]",
+    "Plastic Amount (mg)":         "[Mass of substrate added]",
+    "Reaction Temperature (C)":    "[Temperature of reactor before quenching]",
+    "Quench Temperature (C)":      "[Temperature of reactor after quenching]",
+    "Reaction Pressure (psi)":     "[Pressure of reactor before quenching]",
+    "Initial Pressure (psi)":      "[Initial charge pressure of reactor]",
+    "Quench Pressure (psi)":       "[Pressure of reactor after quenching",
+    "Start Time":                  "[Start time in format yyyy-mm-dd hh:mm:ss.000]",
+    "End Time":                    "[End time in format yyyy-mm-dd hh:mm:ss.000]",
+    "Heat Time":                   "[Time taken to reach reaction temperature from room temperature]",
+    "Internal Standard Name":      "[Name of external/internal standard]",
+    "Internal Standard Mass (mg)": "[Mass of external/internal standard]",
+    "Reactor Volume (mL)":         "[Reactor total volume]",
+    "Remaining solids (mg)":       "[Weight of dry residual solids]",
+    "Injected CO2 (mL)":           "[Volume of CO2 injected into gas bag containing gas sample]"
+}
+```
+
+<h4>Data Structure</h4>
+Inside of the ChromaQuant documents folder are a few folders: data, resources, response-factors, and images. The data folder contains directories representing individual samples or reaction products to be analyzed. This is the most frequently used folder in ChromaQuant The resources folder contains a .csv file with known gas FID compounds used in third order assignment alongside some legacy files describing compound structure. This folder also contains the theme used in the ChromaQuant UI. The response-factors folder contains several files with response factors listed by compound type and carbon number split by detector. These response factors are highly dependant on the conditions and methods used in GC analysis and therefore it is critical these are kept updated with lab-specific values for the most accurate results. Finally, the images folder contains the logo in several formats and the workflow image. <br><br>
+
+```bash
+.
+├── data
+│   └── example2
+│       ├── breakdowns
+│       │   ├── example2_Breakdown_20240729 (1).xlsx
+│       │   └── example2_Breakdown_20240729.xlsx
+│       ├── example2_INFO.json
+│       ├── log
+│       │   └── quantlog_20240729.log
+│       ├── manual
+│       │   └── MBPR053_02_ManualBreakdown.xlsx
+│       └── raw data
+│           ├── example2_GS1_MS_SPEC.csv
+│           ├── example2_GS1_UA_Comp_UPP.csv
+│           ├── example2_GS2_FID_SPEC.CSV
+│           ├── example2_GS2_FIDpMS.csv
+│           ├── example2_GS2_TCD_CSO.csv
+│           ├── example2_GS2_TCD_SPEC.CSV
+│           ├── example2_LQ1_FID_CSO.csv
+│           ├── example2_LQ1_FID_SPEC.CSV
+│           ├── example2_LQ1_FIDpMS.csv
+│           ├── example2_LQ1_MS_SPEC.csv
+│           └── example2_LQ1_UA_Comp_UPP.csv
+├── images
+│   ├── ChromaQuantIcon.icns
+│   ├── ChromaQuantIcon.png
+│   ├── ChromaQuantIcon.svg
+│   └── workflow.png
+├── resources
+│   ├── KnownCompoundsAuto.xlsx
+│   ├── gasPairs_FIDpMS.csv
+│   ├── known_compounds.csv
+│   └── smilePairs.csv
+└── response-factors
+    ├── FIDRF_7-24-24.csv
+    ├── LRF_7-24-24.xlsx
+    ├── TCDRF_7-24-24.csv
+    └── liquidRFFits.csv
+```
+
+For a given sample, all data files listed in **Table 1** should be placed in the "data/[Sample]/raw data" directory except for the INFO.json, which should be placed in the "data/[Sample]" directory.

chromaquant-0.3.1.dist-info/RECORD

@@ -0,0 +1,22 @@
+chromaquant/__init__.py,sha256=YaYoGMnzPZriraM5uOtqwkjUpgmglRu1OZC3Y068WqE,125
+chromaquant/__main__.py,sha256=zGIurUK7plMMtjM90ciHZ4RahCI8AW71uj42lvqE98A,17964
+chromaquant/properties.json,sha256=TPGCjF6kfrkBfvNukkgtNEMC5RHXw8jpSgXANIZYi8I,167
+chromaquant/Handle/__init__.py,sha256=_NTyu9nk9G9nHB9Ky0Zy0JLmRN_E9qvVnqYyqBjeXpw,166
+chromaquant/Handle/handleDirectories.py,sha256=Tb_Eh3cL8t_MvEk9UQmGJ_I-20r0_vRbntWfWT3xU10,2324
+chromaquant/Manual/HydroUI.py,sha256=R1W6n8i48sKfQOLEkihvJrKjsl8n7FUpugX-vGNehDc,17909
+chromaquant/Manual/QuantUPP.py,sha256=r_HOxjkP5rR8htYmqtW7uEM9-fRdeRfA7wx9T-D6JtM,16524
+chromaquant/Manual/Quantification.py,sha256=4UD5qZALnMaqv2TZLLi_ws_ob8HSnu5pVJpYDwHcpJs,61239
+chromaquant/Manual/__init__.py,sha256=NqutHWd40NvTa2jxXn5lkLSEo3QGBGjFUAwIQq0ldYs,132
+chromaquant/Manual/duplicateMatch.py,sha256=pYr1opZXtVOzKDFVlqb6TqahKHG7lJjdEq6NoPFKtxM,6634
+chromaquant/Manual/fpm_match.py,sha256=4enAIU7rUjptRrZDHlpkqwXw8jWwbaHOIv111oVxoi8,33026
+chromaquant/Manual/label-type.py,sha256=XKJqE5HH2haU5b8PtsTnKpQpTM_A50Wg97M6bC1RcSE,6785
+chromaquant/Match/AutoFpmMatch.py,sha256=pdrQoX8p_gXevsxVyrMN7bMgDKESoMbTAJ5gsXZesEI,49758
+chromaquant/Match/__init__.py,sha256=VSe6E42w-fxY5YndzX8e4nG_1CGuk7rGWx3C8O3DwuY,176
+chromaquant/Quant/AutoQuantification.py,sha256=532q9p_U5eS1yKMioIz-2QwZlfohMkLuKt-hwcGM2Lk,68286
+chromaquant/Quant/__init__.py,sha256=XaO0aNBHzFSJ85-CZjf7Na1Q_viINhwi_5E4tftPX4M,188
+chromaquant-0.3.1.dist-info/METADATA,sha256=mV1yf5tLVA_c2leq468fPbqk-to8Ll6tnmbG1LNT_U8,13798
+chromaquant-0.3.1.dist-info/WHEEL,sha256=1yFddiXMmvYK7QYTqtRNtX66WJ0Mz8PYEiEUoOUUxRY,87
+chromaquant-0.3.1.dist-info/entry_points.txt,sha256=ndYFHkaQbo8HqFrqgcTFR0DUf2uaaIDCKoUXq4a7fZ8,53
+chromaquant-0.3.1.dist-info/licenses/LICENSE.txt,sha256=HsSWL8nKIHN152h0IMZ333SF77CBxXVubxVfCqh1tVs,1672
+chromaquant-0.3.1.dist-info/licenses/LICENSES_bundled.txt,sha256=K856We6Y4uORXKYZfhzxxO2WH-H7X9aHYkDi4suIj5c,51623
+chromaquant-0.3.1.dist-info/RECORD,,

chromaquant-0.3.1.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.25.0
+Root-Is-Purelib: true
+Tag: py3-none-any

chromaquant-0.3.1.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[gui_scripts]
+chroma-ui = chromaquant.__main__:runUI

chromaquant-0.3.1.dist-info/licenses/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.