tts-dtat 0.2.3__tar.gz

tts_dtat-0.2.3/.gitignore

@@ -0,0 +1,39 @@
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# OS files
+.DS_Store
+._*
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class

tts_dtat-0.2.3/PKG-INFO

@@ -0,0 +1,62 @@
+Metadata-Version: 2.4
+Name: tts-dtat
+Version: 0.2.3
+Summary: Data Trending and Analysis Tool Library
+Author: winner
+Author-email: winner <emily.winner@jpl.nasa.gov>, muszynsk <matt.muszynski@jpl.nasa.gov>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/NASA-JPL-Teamtools-Studio/tts_dtat
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: Apache Software License
+Requires-Python: >=3.6
+Description-Content-Type: text/markdown
+Requires-Dist: nbformat>=4.2.0
+Requires-Dist: plotly>=5.14
+Requires-Dist: pytest
+Requires-Dist: pandas>=2.0.0; python_version >= "3.9"
+Requires-Dist: pandas>=1.1.0; python_version < "3.9"
+Requires-Dist: tts-utilities
+Dynamic: author
+Dynamic: requires-python
+
+# DTAT
+
+![Project logo](https://github.com/NASA-JPL-Teamtools-Studio/teamtools_documentation/blob/main/docs/images/tts_image_artifacts/dtat.png)
+
+## About Teamtools Studio
+
+Teamtools Studio Utilities is part of JPL's Teamtools Studio (TTS).
+
+TTS is an effort originated in JPL's Planning and Execution section to centralize shared repositories across missions. This benefits JPL by reducing cost through reducing duplicated code, collaborating across missions, and unifying standards for development and design across JPL.
+
+Although Planning and Execution is primarily concerned with flight operations, the TTS suite has been generalized and atomized to the point where many of these tools are applicable during other mission phases and even in non-spaceflight contexts. Through our work flying space missions, we hope to provide tools to the open source community that have utility in data analysis or planning for any complex system where failure is not an option.
+
+For more infomation on how to contribute, and how these libraries form a complete ecosystem for high reliability data analysis, see the [Full TTS Documentation](https://nasa-jpl-teamtools-studio.github.io/teamtools-documentation/).
+
+## What is DTAT?
+
+### Overview
+
+DTAT is the TTS solution to complex plotting. It is largely an extension of Plotly. Although we love Plotly and use it often,
+one of the problems with such libraries is that they are so open ended that they take significant expertise in order to
+create maintainable, reusable code.
+
+DTAT wraps Plotly to handle common plotting issues with a more user friendly interface. It is not as flexible as raw Plotly,
+but it is significantly easier to grab out of the box and use.
+
+Furthermore, there are some known challenges with Plotly that every user hits and average developers struggle to overcome. DTAT
+is a place where we can encode lessons learned about these limitations so not every user who wants to make a plot needs to
+overcome them.
+
+### Projects Currently Supported
+
+* Europa Clipper
+* Mars Sample Return
+* Orbiting Carbon Observatory 2
+* Mars 2020
+
+## Architecture
+
+### TTS dependencies
+
+* TTS Utilities

tts_dtat-0.2.3/README.md

@@ -0,0 +1,41 @@
+# DTAT
+
+![Project logo](https://github.com/NASA-JPL-Teamtools-Studio/teamtools_documentation/blob/main/docs/images/tts_image_artifacts/dtat.png)
+
+## About Teamtools Studio
+
+Teamtools Studio Utilities is part of JPL's Teamtools Studio (TTS).
+
+TTS is an effort originated in JPL's Planning and Execution section to centralize shared repositories across missions. This benefits JPL by reducing cost through reducing duplicated code, collaborating across missions, and unifying standards for development and design across JPL.
+
+Although Planning and Execution is primarily concerned with flight operations, the TTS suite has been generalized and atomized to the point where many of these tools are applicable during other mission phases and even in non-spaceflight contexts. Through our work flying space missions, we hope to provide tools to the open source community that have utility in data analysis or planning for any complex system where failure is not an option.
+
+For more infomation on how to contribute, and how these libraries form a complete ecosystem for high reliability data analysis, see the [Full TTS Documentation](https://nasa-jpl-teamtools-studio.github.io/teamtools-documentation/).
+
+## What is DTAT?
+
+### Overview
+
+DTAT is the TTS solution to complex plotting. It is largely an extension of Plotly. Although we love Plotly and use it often,
+one of the problems with such libraries is that they are so open ended that they take significant expertise in order to
+create maintainable, reusable code.
+
+DTAT wraps Plotly to handle common plotting issues with a more user friendly interface. It is not as flexible as raw Plotly,
+but it is significantly easier to grab out of the box and use.
+
+Furthermore, there are some known challenges with Plotly that every user hits and average developers struggle to overcome. DTAT
+is a place where we can encode lessons learned about these limitations so not every user who wants to make a plot needs to
+overcome them.
+
+### Projects Currently Supported
+
+* Europa Clipper
+* Mars Sample Return
+* Orbiting Carbon Observatory 2
+* Mars 2020
+
+## Architecture
+
+### TTS dependencies
+
+* TTS Utilities

tts_dtat-0.2.3/docs/conf.py

@@ -0,0 +1,71 @@
+# TTS-specifc add ons
+from pathlib import Path
+from datetime import datetime
+from setuptools_scm import get_version
+import toml
+
+# Configuration file for the Sphinx documentation builder.
+#
+# This file only contains a selection of the most common options. For a full
+# list see the documentation:
+# https://www.sphinx-doc.org/en/master/usage/configuration.html
+
+# -- Path setup --------------------------------------------------------------
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#
+
+import os
+import sys
+import importlib.metadata
+sys.path.insert(0, os.path.abspath('..'))
+
+# -- Project information -----------------------------------------------------
+
+pyproject = toml.load(Path(__file__).parent.parent.joinpath("pyproject.toml"))
+project = pyproject["project"]["name"]
+release = get_version(root='..', relative_to=__file__)
+version = '.'.join(release.split('.')[:2])
+
+copyright = f'{datetime.now().strftime('%Y')} JPL'
+author = 'JPL Teamtools Studio'
+
+
+# -- General configuration ---------------------------------------------------
+
+# Add any Sphinx extension module names here, as strings. They can be
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
+# ones.
+extensions = ['sphinx.ext.autodoc']
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+# This pattern also affects html_static_path and html_extra_path.
+exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']
+
+# The master toctree document.
+master_doc = 'index'
+
+pygments_style = 'sphinx'
+# html_theme = 'nature'
+# html_theme = 'sphinx_material'
+html_theme = 'pydata_sphinx_theme'
+
+# -- Options for HTML output -------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+#
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+html_css_files = ['bugfix.css']
+html_copy_source = False
+html_show_sourcelink = False