Skip to main content

DeepUtilities

DeepUtilities Logo

What is it?

Pipeline for developing, training, and diagnosing machine learning algorithms

Why do we need it? Why is it useful?

  1. There are standard methods for pre-processing, training, and diagnosing algorithms; why should everyone reinvent the wheel every time?
  2. Let's standardize and grow the library of diagnostics for science analyses with machine learning!

General Features

  1. modularity - replaceable/extensible pipeline elements
  2. fully connected pipeline elements
  3. good for both TensorFlow and PyTorch

Requirements

  1. python 3.x
  2. more, but not sure yet.

Example

Example Image of pipeline

Pipeline Flow

  1. Ingest
  2. Pre-process
  3. Train
  4. Test
  5. Evalute
  6. Report

Original Development Team

  1. Praveen Balaji
  2. Joao Caldeira
  3. Callista Christ
  4. Aleksandra Ciprijanovic
  5. Anand Jain
  6. Francois Lanusse
  7. Brian Nord
  8. Marwah Roussi
  9. Amanda Whaley

How to contribute

I'm really glad you're reading this, because we need volunteer developers to help this project come to fruition.

Submitting changes

Please send a GitHub Pull Request to DeepUtilities with a clear list of what you've done (read more about pull requests). When you send a pull request, we will love you forever if you include examples. We can always use more test coverage. Please follow our coding conventions (below) and make sure all of your commits are atomic (one feature per commit).

Always write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should look like this:

$ git commit -m "A brief summary of the commit
> 
> A paragraph describing what changed and its impact."

Coding conventions

Start reading our code and you'll get the hang of it. We optimize for readability:

  • We indent using tabs
  • We ALWAYS put spaces after list items and method parameters ([1, 2, 3], not [1,2,3]), around operators (x += 1, not x+=1), and around hash arrows.
  • This is open source software. Consider the people who will read your code, and make it look nice for them. It's sort of like driving a car: Perhaps you love doing donuts when you're alone, but with passengers the goal is to make the ride as smooth as possible.

Metadata

Release files for deeputilities 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deeputilities 0.1.1
File Size Uploaded Provenance
deeputilities-0.1.1.tar.gz 41.3 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for deeputilities 0.1.1
File Interpreter ABI Platform
deeputilities-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 78.3 kB

Release files / deeputilities-0.1.1.tar.gz

Download URL deeputilities-0.1.1.tar.gz
Size 41.3 kB
Tags Source
SHA-256 checksum
How to use checksums
e0b71d3e77c5d6467d08293c12f107f8b8c43a7a426ef211b2f5264e6a44384b
BLAKE2b-256 checksum
How to use checksums
8700e5fa3c1ae3eaa428d377f20ef54d03936974f260e18b52b0f96249d72ac8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.4.2 CPython/3.11.3 Darwin/22.4.0

Release files / deeputilities-0.1.1-py3-none-any.whl

Download URL deeputilities-0.1.1-py3-none-any.whl
Size 37.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ae2510b499ccc574eec76cbe540e99f32e39edb7971bfb1dfb9c152df5e3b7d4
BLAKE2b-256 checksum
How to use checksums
e19a820a07728567219e8652f31e0b55bcf3243451d8c3b4c4b85973a241e2cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.4.2 CPython/3.11.3 Darwin/22.4.0

Security for deeputilities 0.1.1

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.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page