tidye - Tidal simulation with multiple moons in Python
The tidye simulator calculates tidal interactions between a planet and one or more moons.
Installation
The easiest way to install the package is to download it from PyPI using pip.
Note that tidye depends on Python 3.9 or newer; please
ensure that you have a semi-recent version of Python installed before proceeding.
Run the following command in a shell (a UNIX-like environment is assumed):
$ pip install tidye
The package has a few external dependencies besides Python itself. If you wish to sandbox your installation inside a virtual environment, you may choose to use virtualenvwrapper or a similar utility to do so.
When successfully installed, a program called tidye will be placed on your PATH.
See the Usage section below for details about how to use this program.
Usage
The tidye program is a command-line interface for simulating tidal forces.
At any time, you can use the -h or --help flags to see a summary of options that
the program accepts.
$ tidye -h
usage: tidye [-h] [-d DURATION] file
Simulate lunar tides from a provided configuration file.
positional arguments:
file Path to config file (e.g., config.json)
optional arguments:
-h, --help show this help message and exit
-d DURATION, --duration DURATION
Simulation duration (defaults to two full orbits)
Typical usage is tidye <config_file>, where <config_file> is the path to a file
describing the configuration of the planet and moons that you wish to simulate. For an
example config file, see the sample_config.json included in the repository, or check
the example below:
{
"planet": {
"mass": 1000
},
"moons": [
{
"mass": 100,
"orbital_radius": 300,
"orbital_period": 1
},
{
"mass": 200,
"orbital_radius": 500,
"orbital_period": 2,
"orbital_phase": 0.5
},
{
"mass": 150,
"orbital_radius": 400,
"geostationary": true
}
]
}
The program will produce a graph showing the tidal forces on the planet resulting from
each individual moon, as well as the cumulative force from all moons combined
(labeled All). See the image below for an example graph generated by tidye.
Metadata
Release files for tidye 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tidye-0.1.4.tar.gz | 4.6 kB | Without provenance | Details for tidye-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tidye-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for tidye-0.1.4-py3-none-any.whl |
Total release size: 10.4 kB
Release files / tidye-0.1.4.tar.gz
| Download URL | tidye-0.1.4.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bcbe1e3e33ec14a64ff98963615efc85f8222c925becc6b3e332787fbf2108f2
|
|
BLAKE2b-256 checksum How to use checksums |
10602f617ddac016a964819184e1979089afda334522a23002813498c1bd6365
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.1 Darwin/24.3.0
|
Release files / tidye-0.1.4-py3-none-any.whl
| Download URL | tidye-0.1.4-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b6ca9bb68d432776c81fe8728ac76f6f0d53830bcf7844356fe1fc6d93c0da03
|
|
BLAKE2b-256 checksum How to use checksums |
46dbe5d1e0d4f40bbfb250e05fba16eb819c7d5e2e3b333d7ee644b22454dbc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.1 Darwin/24.3.0
|
Security for tidye 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.