tailpype 0.0.7__tar.gz

tailpype-0.0.7/LICENSE.txt

@@ -0,0 +1,19 @@
+Copyright (c) 2018 The Python Packaging Authority
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

tailpype-0.0.7/PKG-INFO

@@ -0,0 +1,199 @@
+Metadata-Version: 2.4
+Name: tailpype
+Version: 0.0.7
+Summary: A toolbox for the analysis of emissions of internal combustion engines.
+Author-email: Pierre Paschinger <ppaschinger@gmx.at>
+License-Expression: MIT
+Project-URL: Homepage, https://test.pypi.org/manage/account/
+Project-URL: Issues, https://test.pypi.org/manage/account/
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE.txt
+Dynamic: license-file
+
+# tailpype
+
+## Table of Contents
+- [Introduction](#introduction)
+- [Getting started](#getting-started)
+- [Building, uploading, and installing the package](#building-uploading-and-installing-the-package)
+- [The modules](#the-modules)
+  - [engine](#engine)
+  - [ftir](#ftir)
+  - [read_meas](#read_meas)
+- [Tests](#tests)
+- [References](#references)
+
+
+
+
+
+
+
+
+
+
+## Introduction
+
+## License
+
+## Getting started
+
+## Building, uploading, and installing the package
+
+The steps needed to make a new build of a Python package, to upload it to (Test)PyPI, and to install it are described in this section. The information has been taken from the part 'Packaging Python Projects' of [1].  A sample Python project/package can be downloaded from [2]. This has not been done for tailpipe but the project structure has been studied as a reference.
+First of all, it is a good idea to have the latest versions of pip (package manager) and twine (utility for publishing Python packages) installed. This can be achieved with the following commands:
+```
+py -m pip install --upgrade pip
+py -m pip install --upgrade twine
+```
+
+To create a new build of the package, use
+```
+py -m build
+```
+
+To upload the build to (Test)PyPI, type
+```
+py -m twine upload --repository testpypi dist/*
+```
+
+You need an API token to finish this process. API tokens can be created in the account settings of your (Test)PyPI account. Logging in to the (Test)PyPI account requires two-factor authentication: the first is username/password, the second is the Authenticator app. If the error message below occurs, it might help to clear the 'dist' folder:
+```
+"ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
+File already exists. See https://test.pypi.org/help/#file-name-reuse for more information."
+```
+
+To install a build of the package example-package use
+```
+py -m pip install --index-url https://test.pypi.org/simple/ --no-deps example-package
+```
+If a specific version, e.g., 1.2.3. is needed, use
+```
+py -m pip install --index-url https://test.pypi.org/simple/ --no-deps example-package==1.2.3
+```
+
+If the package is located in PyPI, the usual way with using pip can also be used to install a build.
+
+## The modules
+
+### engine
+
+### ftir
+
+### read_meas
+
+## Tests
+
+## Release notes
+
+- 0.0.1 - 0.0.x: Development builds to be published on TestPyPI
+- 1.0.0: First build to be published on PyPI
+
+## References
+
+1. “Python Packaging User Guide.” Accessed: Mar. 10, 2026. [Online]. Available: https://packaging.python.org/en/latest/
+
+1. “A sample Python project.” Accessed: Mar. 10, 2026. [Online]. Available: https://github.com/pypa/sampleproject
+
+1. B. Klein, Einführung in Python 3: Für Ein- und Umsteiger, 4th ed. München,: Carl Hanser Fachbuchverlag, 2021.
+
+1. B. Klein, Numerisches Python: Arbeiten mit NumPy, Matplotlib und Pandas. München,: Carl Hanser Fachbuchverlag, 2019.
+
+1. D. Hillard, Publishing Python Packages: Test, Share, and Automate Your Projects. Shelter Island: Manning Publications Co., 2023.
+
+1. “PEP 8 – Style Guide for Python Code.” [Online]. Available: https://peps.python.org/pep-0008/
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+* [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://ci.tno.nl/gitlab/STL/tailpype.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+* [Set up project integrations](https://ci.tno.nl/gitlab/STL/tailpype/-/settings/integrations)
+
+## Collaborate with your team
+
+* [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+* [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+* [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+* [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+* [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+* [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

tailpype-0.0.7/README.md

@@ -0,0 +1,184 @@
+# tailpype
+
+## Table of Contents
+- [Introduction](#introduction)
+- [Getting started](#getting-started)
+- [Building, uploading, and installing the package](#building-uploading-and-installing-the-package)
+- [The modules](#the-modules)
+  - [engine](#engine)
+  - [ftir](#ftir)
+  - [read_meas](#read_meas)
+- [Tests](#tests)
+- [References](#references)
+
+
+
+
+
+
+
+
+
+
+## Introduction
+
+## License
+
+## Getting started
+
+## Building, uploading, and installing the package
+
+The steps needed to make a new build of a Python package, to upload it to (Test)PyPI, and to install it are described in this section. The information has been taken from the part 'Packaging Python Projects' of [1].  A sample Python project/package can be downloaded from [2]. This has not been done for tailpipe but the project structure has been studied as a reference.
+First of all, it is a good idea to have the latest versions of pip (package manager) and twine (utility for publishing Python packages) installed. This can be achieved with the following commands:
+```
+py -m pip install --upgrade pip
+py -m pip install --upgrade twine
+```
+
+To create a new build of the package, use
+```
+py -m build
+```
+
+To upload the build to (Test)PyPI, type
+```
+py -m twine upload --repository testpypi dist/*
+```
+
+You need an API token to finish this process. API tokens can be created in the account settings of your (Test)PyPI account. Logging in to the (Test)PyPI account requires two-factor authentication: the first is username/password, the second is the Authenticator app. If the error message below occurs, it might help to clear the 'dist' folder:
+```
+"ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
+File already exists. See https://test.pypi.org/help/#file-name-reuse for more information."
+```
+
+To install a build of the package example-package use
+```
+py -m pip install --index-url https://test.pypi.org/simple/ --no-deps example-package
+```
+If a specific version, e.g., 1.2.3. is needed, use
+```
+py -m pip install --index-url https://test.pypi.org/simple/ --no-deps example-package==1.2.3
+```
+
+If the package is located in PyPI, the usual way with using pip can also be used to install a build.
+
+## The modules
+
+### engine
+
+### ftir
+
+### read_meas
+
+## Tests
+
+## Release notes
+
+- 0.0.1 - 0.0.x: Development builds to be published on TestPyPI
+- 1.0.0: First build to be published on PyPI
+
+## References
+
+1. “Python Packaging User Guide.” Accessed: Mar. 10, 2026. [Online]. Available: https://packaging.python.org/en/latest/
+
+1. “A sample Python project.” Accessed: Mar. 10, 2026. [Online]. Available: https://github.com/pypa/sampleproject
+
+1. B. Klein, Einführung in Python 3: Für Ein- und Umsteiger, 4th ed. München,: Carl Hanser Fachbuchverlag, 2021.
+
+1. B. Klein, Numerisches Python: Arbeiten mit NumPy, Matplotlib und Pandas. München,: Carl Hanser Fachbuchverlag, 2019.
+
+1. D. Hillard, Publishing Python Packages: Test, Share, and Automate Your Projects. Shelter Island: Manning Publications Co., 2023.
+
+1. “PEP 8 – Style Guide for Python Code.” [Online]. Available: https://peps.python.org/pep-0008/
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+* [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://ci.tno.nl/gitlab/STL/tailpype.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+* [Set up project integrations](https://ci.tno.nl/gitlab/STL/tailpype/-/settings/integrations)
+
+## Collaborate with your team
+
+* [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+* [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+* [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+* [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+* [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+* [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

tailpype-0.0.7/pyproject.toml

@@ -0,0 +1,24 @@
+[project]
+name = "tailpype"
+version = "0.0.7"
+authors = [
+  { name="Pierre Paschinger", email="ppaschinger@gmx.at" },
+]
+description = "A toolbox for the analysis of emissions of internal combustion engines."
+readme = "README.md"
+requires-python = ">=3.12"
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "Operating System :: OS Independent",
+]
+license = "MIT"
+license-files = ["LICEN[CS]E*"]
+
+[project.urls]
+Homepage = "https://test.pypi.org/manage/account/"
+Issues = "https://test.pypi.org/manage/account/"
+
+[tool.pytest.ini_options]
+pythonpath = [
+  "src", "tailpipe"
+]

tailpype-0.0.7/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

tailpype-0.0.7/src/tailpype/__init__.py

@@ -0,0 +1,3 @@
+"""
+A really cool package that does a lot of stuff !
+"""

tailpype-0.0.7/src/tailpype/example.py

@@ -0,0 +1,6 @@
+"""
+A lot of interesting stuff
+"""
+
+def add_one(number):
+    return number + 1

tailpype-0.0.7/src/tailpype/ftir/read_write_spectra.py

@@ -0,0 +1,63 @@
+"""
+The module 'read_write_spectra' provides functionality for reading and storing (infrared) spectra in different
+formats. The focus lies on spectra that can be imported exported by the Calcmet software of Gasmet Technologies Oy.
+"""
+
+import os
+import pandas as pd
+
+from pathlib import Path
+from typing import Literal, Union
+
+
+def read_spectrum(file_path:  str | os.PathLike[str],
+                  file_extension: Literal['dx', 'txt']='dx') -> pd.DataFrame | None:
+
+    file_extension = os.path.splitext(os.path.basename(file_path))[1].lower()
+    # use lowercase to allow for unique check of file extension
+
+    if file_extension == '.dx':
+
+        print(f'\nReading spectra in DX-format is not yet implemented in tailpype !')
+
+        return pd.DataFrame()
+
+    elif file_extension == '.txt':
+
+        df_spectrum = pd.read_csv(filepath_or_buffer=file_path, sep=' ', header=None, encoding='ascii').\
+            rename(columns={0: 'Wave number [cm-1]', 1: os.path.splitext(os.path.basename(file_path))[0]})
+
+    else:
+        raise 'File type of spectrum file could not be determined'
+
+    return df_spectrum
+
+
+def save_spectrum_as(df: pd.DataFrame, file_path: str | Path) -> None:
+    # https: // old.iupac.org / jcamp / protocols / dxir01.pdf
+
+    file_extension = os.path.splitext(os.path.basename(file_path))[1].lower()
+    # use lowercase to allow for unique check of file extension
+
+    if file_extension == '.dx':
+
+        # open templates of DX-file to be filled with data
+        with open(Path(os.path.join(Path(__file__).resolve().parent, 'templates', 'JCAMP‑DX template.dx'))) as fobj:
+            jcamp_dx_file = fobj.read()
+
+        df.iloc[:, 1] = df.iloc[:, 1] * 1e6
+        df.iloc[:, 1] = df.iloc[:, 1].round(0).astype(int)
+        # needed to match the number format
+
+        jcamp_dx_file = jcamp_dx_file.replace(r'REPLACE WITH DATA !', df.to_string(index=False, header=False))
+
+        with open(file_path, 'w') as fobj:
+            fobj.write(jcamp_dx_file)
+
+        return None
+
+    elif file_extension == '.txt':
+
+        print(f'\nStoring spectra in TXT-format is not yet implemented in tailpype !')
+
+        return None

tailpype-0.0.7/src/tailpype.egg-info/PKG-INFO

@@ -0,0 +1,199 @@
+Metadata-Version: 2.4
+Name: tailpype
+Version: 0.0.7
+Summary: A toolbox for the analysis of emissions of internal combustion engines.
+Author-email: Pierre Paschinger <ppaschinger@gmx.at>
+License-Expression: MIT
+Project-URL: Homepage, https://test.pypi.org/manage/account/
+Project-URL: Issues, https://test.pypi.org/manage/account/
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE.txt
+Dynamic: license-file
+
+# tailpype
+
+## Table of Contents
+- [Introduction](#introduction)
+- [Getting started](#getting-started)
+- [Building, uploading, and installing the package](#building-uploading-and-installing-the-package)
+- [The modules](#the-modules)
+  - [engine](#engine)
+  - [ftir](#ftir)
+  - [read_meas](#read_meas)
+- [Tests](#tests)
+- [References](#references)
+
+
+
+
+
+
+
+
+
+
+## Introduction
+
+## License
+
+## Getting started
+
+## Building, uploading, and installing the package
+
+The steps needed to make a new build of a Python package, to upload it to (Test)PyPI, and to install it are described in this section. The information has been taken from the part 'Packaging Python Projects' of [1].  A sample Python project/package can be downloaded from [2]. This has not been done for tailpipe but the project structure has been studied as a reference.
+First of all, it is a good idea to have the latest versions of pip (package manager) and twine (utility for publishing Python packages) installed. This can be achieved with the following commands:
+```
+py -m pip install --upgrade pip
+py -m pip install --upgrade twine
+```
+
+To create a new build of the package, use
+```
+py -m build
+```
+
+To upload the build to (Test)PyPI, type
+```
+py -m twine upload --repository testpypi dist/*
+```
+
+You need an API token to finish this process. API tokens can be created in the account settings of your (Test)PyPI account. Logging in to the (Test)PyPI account requires two-factor authentication: the first is username/password, the second is the Authenticator app. If the error message below occurs, it might help to clear the 'dist' folder:
+```
+"ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
+File already exists. See https://test.pypi.org/help/#file-name-reuse for more information."
+```
+
+To install a build of the package example-package use
+```
+py -m pip install --index-url https://test.pypi.org/simple/ --no-deps example-package
+```
+If a specific version, e.g., 1.2.3. is needed, use
+```
+py -m pip install --index-url https://test.pypi.org/simple/ --no-deps example-package==1.2.3
+```
+
+If the package is located in PyPI, the usual way with using pip can also be used to install a build.
+
+## The modules
+
+### engine
+
+### ftir
+
+### read_meas
+
+## Tests
+
+## Release notes
+
+- 0.0.1 - 0.0.x: Development builds to be published on TestPyPI
+- 1.0.0: First build to be published on PyPI
+
+## References
+
+1. “Python Packaging User Guide.” Accessed: Mar. 10, 2026. [Online]. Available: https://packaging.python.org/en/latest/
+
+1. “A sample Python project.” Accessed: Mar. 10, 2026. [Online]. Available: https://github.com/pypa/sampleproject
+
+1. B. Klein, Einführung in Python 3: Für Ein- und Umsteiger, 4th ed. München,: Carl Hanser Fachbuchverlag, 2021.
+
+1. B. Klein, Numerisches Python: Arbeiten mit NumPy, Matplotlib und Pandas. München,: Carl Hanser Fachbuchverlag, 2019.
+
+1. D. Hillard, Publishing Python Packages: Test, Share, and Automate Your Projects. Shelter Island: Manning Publications Co., 2023.
+
+1. “PEP 8 – Style Guide for Python Code.” [Online]. Available: https://peps.python.org/pep-0008/
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+* [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://ci.tno.nl/gitlab/STL/tailpype.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+* [Set up project integrations](https://ci.tno.nl/gitlab/STL/tailpype/-/settings/integrations)
+
+## Collaborate with your team
+
+* [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+* [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+* [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+* [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+* [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+* [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

tailpype-0.0.7/src/tailpype.egg-info/SOURCES.txt

@@ -0,0 +1,12 @@
+LICENSE.txt
+README.md
+pyproject.toml
+src/tailpype/__init__.py
+src/tailpype/example.py
+src/tailpype/read_meas.py
+src/tailpype.egg-info/PKG-INFO
+src/tailpype.egg-info/SOURCES.txt
+src/tailpype.egg-info/dependency_links.txt
+src/tailpype.egg-info/top_level.txt
+src/tailpype/ftir/__init__.py
+src/tailpype/ftir/read_write_spectra.py

tailpype-0.0.7/src/tailpype.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

tailpype-0.0.7/src/tailpype.egg-info/top_level.txt

@@ -0,0 +1 @@
+tailpype