Science Score: 44.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (15.6%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

Basic Info
  • Host: GitHub
  • Owner: Yreus6
  • License: apache-2.0
  • Language: Jupyter Notebook
  • Default Branch: main
  • Size: 12.1 MB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created over 2 years ago · Last pushed about 2 years ago
Metadata Files
Readme License Citation

README.md

Lightning Lab

Overview

Lightning Lab is a public template for artificial intelligence and machine learning research projects using Lightning AI's PyTorch Lightning.

The recommended way for Lightning Lab users to create new repos is with the use this template button.

You can find domain specific variations of Lightning Lab on my wiki.

The Structure

Source Module

lightninglab.cli contains code for the command line interface built with Typer.

lightninglab.components contains experiment utilities grouped by purpose for cohesion.

lightninglab.core contains code for the Lightning Module and Trainer.

lightninglab.pipeline contains code for data acquistion and preprocessing, and building a TorchDataset and LightningDataModule.

lightninglab.serve contains code for model serving APIs built with FastAPI.

lightninglab.config assists with project, trainer, and sweep configurations.

Project Root

data directory should be used to cache the TorchDataset and training splits locally if the size of the dataset allows for local storage. additionally, this directory should be used to cache predictions during HPO sweeps.

docs directory should be used for technical documentation.

logs directory contains logs generated from experiment managers and profilers.

models directory contains training checkpoints and the pre-trained production model.

notebooks directory can be used to present exploratory data analysis, explain math concepts, and create a presentation notebook to accompany a conference style paper.

requirements directory should mirror base requirements and extras found in setup.cfg. the requirements directory and requirements.txt at root are required by the basic Coverage GitHub Action.

tests module contains unit and integration tests targeted by pytest.

streamlit contains the Streamlit UI.

setup.py setup.cfg pyproject.toml and MANIFEST.ini assist with packaging the Python project.

.pre-commit-config.yaml is required by pre-commit to install its git-hooks.

Installation

Lightning Lab installs minimal requirements out of the box, and provides extras to make creating robust virtual environments easier. To view the requirements, in setup.cfg, see install_requires for the base requirements and options.extras_require for the available extras.

The recommended install is as follows:

sh python3 -m venv .venv source .venv/bin/activate pip install -e ".[all, { domain extra(s) }]"

where { domain extra(s) } is one of, or some combination of (vision, text, audio, rl, forecast) e.g.

sh python3 -m venv .venv source .venv/bin/activate pip install -e ".[all, vision]"

!!! warning

Do not install multiple variations of Lightning Lab into a single virtual environment. As this will override the lab CLI for each new variation that is installed.

Refactoring the Template

Lightning Lab is a great template for deep learning projects. Using the template will require some refactoring if you intend to rename src/lightninglab to something like src/textlab. You can refactor in a few simple steps in VS Code:

  1. Start by renaming the src/lightninglab to something like src/textlab or src/imagenetlab. Doing so will allow VS Code to refactor all instance of lightninglab that exists in any .py file.
  2. Open the search pane in VS Code and search for lightniglab in tests/ and replace those occurences with whatever you have renamed the source module to.
  3. Next, search for lightninglab and replace those occurences in all .toml .md cfg files and string occurences in .py files.
  4. Next, search for Lightning Lab and change that to your repo name.
  5. Next, search for my name – Justin Goheen and replace that with either your name or GitHub username.
  6. Next, search once again for my name as justingoheen and do the following:
    • replace the occurences in mkdocs.yml with your GitHub username.
    • replace the occurences in authors.yml with your choice of author name for your docs and blog.

Tools and Concepts

Owner

  • Name: Hieutran
  • Login: Yreus6
  • Kind: user

Citation (CITATION.cff)

cff-version: 1.2.0
message: "If you use this software, please cite it as below."
authors:
  - family-names: lastName
    given-names: firstName
  - name: "FirstName LastName"
title: "Project Title"
version: 0.0.1
date-released: 2022-08-06
license: "Apache-2.0"
repository-code: ""
keywords:
  - machine learning
  - deep learning
  - artificial intelligence

GitHub Events

Total
Last Year

Dependencies

.github/workflows/codeql-analysis.yml actions
  • actions/checkout v3 composite
  • github/codeql-action/analyze v2 composite
  • github/codeql-action/autobuild v2 composite
  • github/codeql-action/init v2 composite
.github/workflows/coverage.yml actions
  • actions/checkout v4 composite
  • actions/setup-python v4 composite
  • codecov/codecov-action v3 composite
.github/workflows/docs.yml actions
  • actions/cache v3 composite
  • actions/checkout v4 composite
  • actions/setup-python v4 composite
pyproject.toml pypi
requirements/base.txt pypi
  • optuna *
  • pandas *
  • python-dotenv *
  • pytorch-lightning *
  • scikit-learn *
  • supabase *
  • torch *
  • torch-tb-profiler *
  • torchmetrics *
  • wandb *
requirements/cli.txt pypi
  • rich *
  • typer *
requirements/dev.txt pypi
  • bandit * development
  • black * development
  • coverage * development
  • isort * development
  • mypy * development
  • pre-commit * development
  • pytest * development
  • ruff * development
requirements/docs.txt pypi
  • mkdocs-material *
  • mkdocstrings *
requirements/frontends.txt pypi
  • plotly *
  • streamlit *
requirements/packaging.txt pypi
  • build *
  • setuptools *
  • twine *
requirements.txt pypi
setup.py pypi