Skip to content
This repository was archived by the owner on Oct 1, 2025. It is now read-only.

UTS-SSTC/Age-Detection

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

32 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Age Detection

Setup Environment

Prerequisite

  • Python 3.11.9
  • Anaconda
  • VSCode
  • Git
  • NVIDIA Graphics
  • NVIDIA CUDA Toolkit

Steps

  1. Fork the Age-Detection repository
  2. Clone the forked Age-Detection repository from GitHub to your local machine
    git clone https://github.com/<your-username>/Age-Detection.git
  3. Navigate into the cloned repository directory
    cd Age-Detection
  4. Create a new Conda environment named "Age-Detection" with Python 3.11.9
    conda create -n "Age-Detection" python=3.11.9
  5. Activate the newly created Conda environment
    conda activate Age-Detection
  6. Install all the required dependencies specified in the requirements.txt file
    pip install -r requirements/requirements-normal.txt
    pip install -r requirements/requirements-pytorch.txt
  7. Open the entire folder in VSCode for development

Rules

Commit Messages - Conventional Commits

The commit message should be structured as follows:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
  1. fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).
  2. feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).
  3. BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
  4. types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.
  5. footers other than BREAKING CHANGE: <description> may be provided and follow a convention similar to git trailer format.

Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •