tailpype 0.0.7

A toolbox for the analysis of emissions of internal combustion engines.

tailpype

Table of Contents

• Introduction
• Getting started
• Building, uploading, and installing the package
• The modules
  • engine
  • ftir
  • read_meas
• Tests
• 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/

2. “A sample Python project.” Accessed: Mar. 10, 2026. [Online]. Available: https://github.com/pypa/sampleproject

3. B. Klein, Einführung in Python 3: Für Ein- und Umsteiger, 4th ed. München,: Carl Hanser Fachbuchverlag, 2021.

4. B. Klein, Numerisches Python: Arbeiten mit NumPy, Matplotlib und Pandas. München,: Carl Hanser Fachbuchverlag, 2019.

5. D. Hillard, Publishing Python Packages: Test, Share, and Automate Your Projects. Shelter Island: Manning Publications Co., 2023.

6. “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!

Add your files

• Create or upload files
• Add files using the command line 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

Collaborate with your team

• Invite team members and collaborators
• Create a new merge request
• Automatically close issues from merge requests
• Enable merge request approvals
• Set auto-merge

Test and Deploy

Use the built-in continuous integration in GitLab.

• Get started with GitLab CI/CD
• Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)
• Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy
• Use pull-based deployments for improved Kubernetes management
• Set up protected environments

---

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 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.