actinet 0.0.dev0__tar.gz

actinet-0.0.dev0/LICENSE.md

@@ -0,0 +1,52 @@
+# Academic Use Licence
+
+**These licence terms apply to all licences granted by THE CHANCELLOR, MASTERS AND SCHOLARS OF THE UNIVERSITY OF OXFORD whose administrative offices are at University Offices, Wellington Square, Oxford OX1 2JD, United Kingdom (the “University”) for use of “actinet” (“the Software”) through this website (https://github.com/OxWearables) (the ”Website”). 
+
+By downloading the Software through the Website, you (the “Licensee”) are confirming that you agree that your use of the Software is subject to these licence terms**
+
+**PLEASE READ THESE LICENCE TERMS CAREFULLY BEFORE DOWNLOADING THE SOFTWARE. IF YOU DO NOT AGREE TO THESE LICENCE TERMS YOU SHOULD NOT DOWNLOAD THE SOFTWARE.**
+
+**THE SOFTWARE IS INTENDED FOR USE BY ACADEMICS CARRYING OUT RESEARCH AND NOT FOR USE BY CONSUMERS OR COMMERCIAL BUSINESSES.**
+
+**1.	Academic Use Licence**  
+1.1	The Licensee is granted a limited non-exclusive and non-transferable royalty free licence to download and use the Software provided that the Licensee will:
+- (a)	limit their use of the Software to their own internal academic non-commercial research which is undertaken for the purposes of education or other scholarly use;
+- (b)	not use the Software for or on behalf of any third party or to provide a service or integrate all or part of the Software into a product for sale or license to third parties;
+- (c)	use the Software in accordance with the prevailing instructions and guidance for use given on the Website and comply with procedures on the Website for user identification, authentication and access;
+- (d)	comply with all applicable laws and regulations with respect to their use of the Software; and
+- (e)	ensure that the Copyright Notice “Copyright © 2022, University of Oxford” appears prominently wherever the Software is reproduced and is referenced or cited with the Copyright Notice when the Software is described in any research publication or on any documents or other material created using the Software.
+
+
+1.2	The Licensee may only reproduce, modify, transmit or transfer the Software where:
+- (a)	such reproduction, modification, transmission or transfer is for academic, research or other scholarly use;
+- (b)	the conditions of this Licence are imposed upon the receiver of the Software or any modified Software;
+- (c)	all original and modified Source Code is included in any transmitted software program; and
+- (d)	the Licensee grants the University an irrevocable, indefinite, royalty free, non-exclusive unlimited licence to use and sub-licence any modified Source Code as part of the Software.
+
+
+1.3	The University reserves the right at any time and without liability or prior notice to the Licensee to revise, modify and replace the functionality and performance of the access to and operation of the Software. 
+
+
+1.4	The Licensee acknowledges and agrees that the University owns all intellectual property rights in the Software.  The Licensee shall not have any right, title or interest in the Software.
+
+
+1.5	This Licence will terminate immediately and the Licensee will no longer have any right to use the Software or exercise any of the rights granted to the Licensee upon any breach of the conditions in Section 1 of this Licence.
+
+
+**2.	Indemnity and Liability**  
+2.1	The Licensee shall defend, indemnify and hold harmless the University against any claims, actions, proceedings, losses, damages, expenses and costs (including without limitation court costs and reasonable legal fees) arising out of or in connection with the Licensee's possession or use of the Software, or any breach of these terms by the Licensee.
+
+2.2	The Software is provided on an ‘as is’ basis and the Licensee uses the Software at their own risk. No representations, conditions, warranties or other terms of any kind are given in respect of the the Software and all statutory warranties and conditions are excluded to the fullest extent permitted by law. Without affecting the generality of the previous sentences, the University gives no implied or express warranty and makes no representation that the Software or any part of the Software: (a) will enable specific results to be obtained; or (b) meets a particular specification or is comprehensive within its field or that it is error free or will operate without interruption; or (c) is suitable for any particular, or the Licensee's specific purposes. 
+
+2.3	Except in relation to fraud, death or personal injury, the University's liability to the Licensee for any use of the Software, in negligence or arising in any other way out of the subject matter of these licence terms, will not extend to any incidental or consequential damages or losses, or any loss of profits, loss of revenue, loss of data, loss of contracts or opportunity, whether direct or indirect.
+
+2.4	The Licensee hereby irrevocably undertakes to the University not to make any claim against any employee, student, researcher or other individual engaged by the University, being a claim which seeks to enforce against any of them any liability whatsoever in connection with these licence terms or their subject-matter. 
+
+
+**3.	General**  
+**3.1	Severability** - If any provision (or part of a provision) of these licence terms is found by any court or administrative body of competent jurisdiction to be invalid, unenforceable or illegal, the other provisions shall remain in force.  
+**3.2	Entire Agreement** - These licence terms constitute the whole agreement between the parties and supersede any previous arrangement, understanding or agreement between them relating to the Software.  
+**3.3	Law and Jurisdiction** - These licence terms and any disputes or claims arising out of or in connection with them shall be governed by, and construed in accordance with, the law of England. The Licensee irrevocably submits to the exclusive jurisdiction of the English courts for any dispute or claim that arises out of or in connection with these licence terms.
+
+
+If you are interested in using the Software commercially, please contact Oxford University Innovation Limited to negotiate a licence. Contact details are enquiries@innovation.ox.ac.uk

actinet-0.0.dev0/PKG-INFO

@@ -0,0 +1,188 @@
+Metadata-Version: 2.1
+Name: actinet
+Version: 0.0.dev0
+Summary: Activity detection algorithm compatible with the UK Biobank Accelerometer Dataset
+Home-page: https://github.com/OxWearables/actinet
+Download-URL: https://github.com/OxWearables/actinet
+Author: Shing Chan, Aidan Acquah, Charilaos Zisou, Aiden Doherty
+Maintainer: Shing Chan
+Maintainer-email: shing.chan@ndph.ox.ac.uk
+License: See LICENSE file.
+Keywords: example,setuptools,versioneer
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.8, <4
+Description-Content-Type: text/markdown
+Provides-Extra: dev
+Provides-Extra: docs
+License-File: LICENSE.md
+
+# actinet
+
+A tool to extract meaningful health information from large accelerometer datasets. 
+The software generates time-series and summary metrics useful for answering key questions such as how much time is spent in sleep, sedentary behaviour, or doing physical activity.
+The backbone of this repository is a self-supervised Resnet18 model.
+
+## Install
+
+*Minimum requirements*: Python>=3.8, Java 8 (1.8)
+
+The following instructions make use of Anaconda to meet the minimum requirements:
+
+1. Download & install [Miniconda](https://docs.conda.io/en/latest/miniconda.html) (light-weight version of Anaconda).
+1. (Windows) Once installed, launch the **Anaconda Prompt**.
+1. Create a virtual environment:
+    ```console
+    $ conda create -n actinet python=3.9 openjdk pip
+    ```
+    This creates a virtual environment called `actinet` with Python version 3.9, OpenJDK, and Pip.
+1. Activate the environment:
+    ```console
+    $ conda activate actinet
+    ```
+    You should now see `(actinet)` written in front of your prompt.
+1. Install `actinet`:
+    ```console
+    $ pip install actinet
+    ```
+
+You are all set! The next time that you want to use `actinet`, open the Anaconda Prompt and activate the environment (step 4). If you see `(actinet)` in front of your prompt, you are ready to go!
+
+## Usage
+
+```bash
+# Process an AX3 file
+$ actinet sample.cwa
+
+# Or an ActiGraph file
+$ actinet sample.gt3x
+
+# Or a GENEActiv file
+$ actinet sample.bin
+
+# Or a CSV file (see data format below)
+$ actinet sample.csv
+```
+
+
+### Troubleshooting 
+Some systems may face issues with Java when running the script. If this is your case, try fixing OpenJDK to version 8:
+```console
+$ conda install -n actinet openjdk=8
+```
+
+### Output files
+By default, output files will be stored in a folder named after the input file, `outputs/{filename}/`, created in the current working directory. You can change the output path with the `-o` flag:
+
+```console
+$ actinet sample.cwa -o /path/to/some/folder/
+```
+
+The following output files are created:
+
+- *Info.json* Summary info, as shown above.
+- *timeSeries.csv* Raw time-series of activity levels
+
+See [Data Dictionary](https://biobankaccanalysis.readthedocs.io/en/latest/datadict.html) for the list of output variables.
+
+
+### Crude vs. Adjusted Estimates
+Adjusted estimates are provided that account for missing data.
+Missing values in the time-series are imputed with the mean of the same timepoint of other available days.
+For adjusted totals and daily statistics, 24h multiples are needed and will be imputed if necessary.
+Estimates will be NaN where data is still missing after imputation.
+
+
+### Processing CSV files
+If a CSV file is provided, it must have the following header: `time`, `x`, `y`, `z`. 
+
+Example:
+```console
+time,x,y,z
+2013-10-21 10:00:08.000,-0.078923,0.396706,0.917759
+2013-10-21 10:00:08.010,-0.094370,0.381479,0.933580
+2013-10-21 10:00:08.020,-0.094370,0.366252,0.901938
+2013-10-21 10:00:08.030,-0.078923,0.411933,0.901938
+...
+```
+
+### Processing multiple files
+#### Windows
+To process multiple files you can create a text file in Notepad which includes one line for each file you wish to process, as shown below for *file1.cwa*, *file2.cwa*, and *file2.cwa*.
+
+Example text file *commands.txt*: 
+```console
+actinet file1.cwa &
+actinet file2.cwa &
+actinet file3.cwa 
+:END
+````
+Once this file is created, run `cmd < commands.txt` from the terminal.
+
+#### Linux
+Create a file *command.sh* with:
+```console
+actinet file1.cwa
+actinet file2.cwa
+actinet file3.cwa
+```
+Then, run `bash command.sh` from the terminal.
+
+#### Collating outputs
+
+A utility script is provided to collate outputs from multiple runs:
+
+```console
+$ actinet-collate-outputs outputs/
+```
+This will collate all *-Info.json files found in outputs/ and generate a CSV file.
+
+## Citing our work
+
+When using this tool, please consider citing the works listed in [CITATION.md](https://github.com/OxWearables/actinet/blob/main/CITATION.md).
+
+
+## Licence
+See [LICENSE.md](https://github.com/OxWearables/actinet/blob/main/LICENSE.md).
+
+
+## Acknowledgements
+We would like to thank all our code contributors, manuscript co-authors, and research participants for their help in making this work possible.
+
+# Sample PyPI package + GitHub Actions + Versioneer
+
+This template aims to automate the tedious and error-prone steps of tagging/versioning, building and publishing new package versions. This is achieved by syncing git tags and versions with Versioneer, and automating the build and release with GitHub Actions, so that publishing a new version is as painless as:
+
+```console
+$ git tag vX.Y.Z && git push --tags
+```
+
+The following guide assumes familiarity with `setuptools` and PyPI. For an introduction to Python packaging, see the references at the bottom.
+
+## How to use this template
+
+1. Click on the *Use this template* button to get a copy of this repository.
+1. Rename *src/sample_package* folder to your package name &mdash; *src/* is where your package must reside.
+1. Go through each of the following files and rename all instances of *sample-package* or *sample_package* to your package name. Also update the package information such as author names, URLs, etc.
+    1. setup.py
+    1. pyproject.toml
+    1. \_\_init\_\_.py
+1. Install `versioneer` and `tomli`, and run `versioneer`:
+
+    ```console
+    $ pip install tomli
+    $ pip install versioneer
+    $ versioneer install
+    ```
+    Then *commit* the changes produced by `versioneer`. See [here](https://github.com/python-versioneer/python-versioneer/blob/master/INSTALL.md) to learn more.
+1. Setup your PyPI credentials. See the section *Saving credentials on Github* of [this guide](https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/). You should use the variable names `TEST_PYPI_API_TOKEN` and `PYPI_API_TOKEN` for the TestPyPI and PyPI tokens, respectively. See *.github/workflows/release.yaml*.
+
+You are all set! It should now be possible to run `git tag vX.Y.Z && git push --tags` to automatically version, build and publish a new release to PyPI.
+
+Finally, it is a good idea to [configure tag protection rules](https://docs.github.com/en/enterprise-server@3.8/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) in your repository.
+
+## References
+- Python packaging guide: https://packaging.python.org/en/latest/tutorials/packaging-projects/
+    - ...and how things are changing: https://snarky.ca/what-the-heck-is-pyproject-toml/ &mdash; in particular, note that while *pyproject.toml* seems to be the future, currently Versioneer still depends on *setup.py*.
+- Versioneer: https://github.com/python-versioneer/python-versioneer
+- GitHub Actions: https://docs.github.com/en/actions

actinet-0.0.dev0/README.md

@@ -0,0 +1,169 @@
+# actinet
+
+A tool to extract meaningful health information from large accelerometer datasets. 
+The software generates time-series and summary metrics useful for answering key questions such as how much time is spent in sleep, sedentary behaviour, or doing physical activity.
+The backbone of this repository is a self-supervised Resnet18 model.
+
+## Install
+
+*Minimum requirements*: Python>=3.8, Java 8 (1.8)
+
+The following instructions make use of Anaconda to meet the minimum requirements:
+
+1. Download & install [Miniconda](https://docs.conda.io/en/latest/miniconda.html) (light-weight version of Anaconda).
+1. (Windows) Once installed, launch the **Anaconda Prompt**.
+1. Create a virtual environment:
+    ```console
+    $ conda create -n actinet python=3.9 openjdk pip
+    ```
+    This creates a virtual environment called `actinet` with Python version 3.9, OpenJDK, and Pip.
+1. Activate the environment:
+    ```console
+    $ conda activate actinet
+    ```
+    You should now see `(actinet)` written in front of your prompt.
+1. Install `actinet`:
+    ```console
+    $ pip install actinet
+    ```
+
+You are all set! The next time that you want to use `actinet`, open the Anaconda Prompt and activate the environment (step 4). If you see `(actinet)` in front of your prompt, you are ready to go!
+
+## Usage
+
+```bash
+# Process an AX3 file
+$ actinet sample.cwa
+
+# Or an ActiGraph file
+$ actinet sample.gt3x
+
+# Or a GENEActiv file
+$ actinet sample.bin
+
+# Or a CSV file (see data format below)
+$ actinet sample.csv
+```
+
+
+### Troubleshooting 
+Some systems may face issues with Java when running the script. If this is your case, try fixing OpenJDK to version 8:
+```console
+$ conda install -n actinet openjdk=8
+```
+
+### Output files
+By default, output files will be stored in a folder named after the input file, `outputs/{filename}/`, created in the current working directory. You can change the output path with the `-o` flag:
+
+```console
+$ actinet sample.cwa -o /path/to/some/folder/
+```
+
+The following output files are created:
+
+- *Info.json* Summary info, as shown above.
+- *timeSeries.csv* Raw time-series of activity levels
+
+See [Data Dictionary](https://biobankaccanalysis.readthedocs.io/en/latest/datadict.html) for the list of output variables.
+
+
+### Crude vs. Adjusted Estimates
+Adjusted estimates are provided that account for missing data.
+Missing values in the time-series are imputed with the mean of the same timepoint of other available days.
+For adjusted totals and daily statistics, 24h multiples are needed and will be imputed if necessary.
+Estimates will be NaN where data is still missing after imputation.
+
+
+### Processing CSV files
+If a CSV file is provided, it must have the following header: `time`, `x`, `y`, `z`. 
+
+Example:
+```console
+time,x,y,z
+2013-10-21 10:00:08.000,-0.078923,0.396706,0.917759
+2013-10-21 10:00:08.010,-0.094370,0.381479,0.933580
+2013-10-21 10:00:08.020,-0.094370,0.366252,0.901938
+2013-10-21 10:00:08.030,-0.078923,0.411933,0.901938
+...
+```
+
+### Processing multiple files
+#### Windows
+To process multiple files you can create a text file in Notepad which includes one line for each file you wish to process, as shown below for *file1.cwa*, *file2.cwa*, and *file2.cwa*.
+
+Example text file *commands.txt*: 
+```console
+actinet file1.cwa &
+actinet file2.cwa &
+actinet file3.cwa 
+:END
+````
+Once this file is created, run `cmd < commands.txt` from the terminal.
+
+#### Linux
+Create a file *command.sh* with:
+```console
+actinet file1.cwa
+actinet file2.cwa
+actinet file3.cwa
+```
+Then, run `bash command.sh` from the terminal.
+
+#### Collating outputs
+
+A utility script is provided to collate outputs from multiple runs:
+
+```console
+$ actinet-collate-outputs outputs/
+```
+This will collate all *-Info.json files found in outputs/ and generate a CSV file.
+
+## Citing our work
+
+When using this tool, please consider citing the works listed in [CITATION.md](https://github.com/OxWearables/actinet/blob/main/CITATION.md).
+
+
+## Licence
+See [LICENSE.md](https://github.com/OxWearables/actinet/blob/main/LICENSE.md).
+
+
+## Acknowledgements
+We would like to thank all our code contributors, manuscript co-authors, and research participants for their help in making this work possible.
+
+# Sample PyPI package + GitHub Actions + Versioneer
+
+This template aims to automate the tedious and error-prone steps of tagging/versioning, building and publishing new package versions. This is achieved by syncing git tags and versions with Versioneer, and automating the build and release with GitHub Actions, so that publishing a new version is as painless as:
+
+```console
+$ git tag vX.Y.Z && git push --tags
+```
+
+The following guide assumes familiarity with `setuptools` and PyPI. For an introduction to Python packaging, see the references at the bottom.
+
+## How to use this template
+
+1. Click on the *Use this template* button to get a copy of this repository.
+1. Rename *src/sample_package* folder to your package name &mdash; *src/* is where your package must reside.
+1. Go through each of the following files and rename all instances of *sample-package* or *sample_package* to your package name. Also update the package information such as author names, URLs, etc.
+    1. setup.py
+    1. pyproject.toml
+    1. \_\_init\_\_.py
+1. Install `versioneer` and `tomli`, and run `versioneer`:
+
+    ```console
+    $ pip install tomli
+    $ pip install versioneer
+    $ versioneer install
+    ```
+    Then *commit* the changes produced by `versioneer`. See [here](https://github.com/python-versioneer/python-versioneer/blob/master/INSTALL.md) to learn more.
+1. Setup your PyPI credentials. See the section *Saving credentials on Github* of [this guide](https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/). You should use the variable names `TEST_PYPI_API_TOKEN` and `PYPI_API_TOKEN` for the TestPyPI and PyPI tokens, respectively. See *.github/workflows/release.yaml*.
+
+You are all set! It should now be possible to run `git tag vX.Y.Z && git push --tags` to automatically version, build and publish a new release to PyPI.
+
+Finally, it is a good idea to [configure tag protection rules](https://docs.github.com/en/enterprise-server@3.8/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) in your repository.
+
+## References
+- Python packaging guide: https://packaging.python.org/en/latest/tutorials/packaging-projects/
+    - ...and how things are changing: https://snarky.ca/what-the-heck-is-pyproject-toml/ &mdash; in particular, note that while *pyproject.toml* seems to be the future, currently Versioneer still depends on *setup.py*.
+- Versioneer: https://github.com/python-versioneer/python-versioneer
+- GitHub Actions: https://docs.github.com/en/actions

actinet-0.0.dev0/pyproject.toml

@@ -0,0 +1,163 @@
+# [project]
+# # Template from: https://github.com/pypa/sampleproject
+# # This is the name of your project. The first time you publish this
+# # package, this name will be registered for you. It will determine how
+# # users can install this project, e.g.:
+# #
+# # $ pip install sampleproject
+# #
+# # And where it will live on PyPI: https://pypi.org/project/sampleproject/
+# #
+# # There are some restrictions on what makes a valid project name
+# # specification here:
+# # https://packaging.python.org/specifications/core-metadata/#name
+# name = "sample-package-chanshing"  # Required
+
+# # Versions should comply with PEP 440:
+# # https://www.python.org/dev/peps/pep-0440/
+# #
+# # For a discussion on single-sourcing the version, see
+# # https://packaging.python.org/guides/single-sourcing-package-version/
+# version = "0.0.1"  # Required
+
+# # This is a one-line description or tagline of what your project does. This
+# # corresponds to the "Summary" metadata field:
+# # https://packaging.python.org/specifications/core-metadata/#summary
+# description = "An example Python project"  # Optional
+
+# # This is an optional longer description of your project that represents
+# # the body of text which users will see when they visit PyPI.
+# #
+# # Often, this is the same as your README, so you can just read it in from
+# # that file directly (as we have already done above)
+# #
+# # This field corresponds to the "Description" metadata field:
+# # https://packaging.python.org/specifications/core-metadata/#description-optional
+# readme = "README.md" # Optional
+
+# # Specify which Python versions you support. In contrast to the
+# # 'Programming Language' classifiers above, 'pip install' will check this
+# # and refuse to install the project if the version does not match. See
+# # https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
+# requires-python = ">=3.8"
+
+# # This is either text indicating the license for the distribution, or a file
+# # that contains the license
+# # https://packaging.python.org/en/latest/specifications/core-metadata/#license
+# license = {file = "LICENSE.md"}
+
+# # This field adds keywords for your project which will appear on the
+# # project page. What does your project relate to?
+# #
+# # Note that this is a list of additional keywords, separated
+# # by commas, to be used to assist searching for the distribution in a
+# # larger catalog.
+# keywords = ["example", "setuptools", "development"]  # Optional
+
+# # This should be your name or the name of the organization who originally
+# # authored the project, and a valid email address corresponding to the name
+# # listed.
+# authors = [
+#   {name = "A. Random Developer", email = "author@example.com" } # Optional
+# ]
+
+# # This should be your name or the names of the organization who currently
+# # maintains the project, and a valid email address corresponding to the name
+# # listed.
+# maintainers = [
+#   {name = "A. Great Maintainer", email = "maintainer@example.com" } # Optional
+# ]
+
+# # Classifiers help users find your project by categorizing it.
+# #
+# # For a list of valid classifiers, see https://pypi.org/classifiers/
+# classifiers = [  # Optional
+#   # How mature is this project? Common values are
+#   #   3 - Alpha
+#   #   4 - Beta
+#   #   5 - Production/Stable
+#   "Development Status :: 3 - Alpha",
+
+#   # Indicate who your project is intended for
+#   "Intended Audience :: Developers",
+#   "Topic :: Software Development :: Build Tools",
+
+#   # Pick your license as you wish
+#   "License :: OSI Approved :: MIT License",
+
+#   # Specify the Python versions you support here. In particular, ensure
+#   # that you indicate you support Python 3. These classifiers are *not*
+#   # checked by "pip install". See instead "python_requires" below.
+#   "Programming Language :: Python :: 3",
+#   "Programming Language :: Python :: 3.7",
+#   "Programming Language :: Python :: 3.8",
+#   "Programming Language :: Python :: 3.9",
+#   "Programming Language :: Python :: 3.10",
+#   "Programming Language :: Python :: 3.11",
+#   "Programming Language :: Python :: 3 :: Only",
+# ]
+
+# # This field lists other packages that your project depends on to run.
+# # Any package you put here will be installed by pip when your project is
+# # installed, so they must be valid existing projects.
+# #
+# # For an analysis of this field vs pip's requirements files see:
+# # https://packaging.python.org/discussions/install-requires-vs-requirements/
+# dependencies = [ # Optional
+#   "peppercorn"
+# ]
+
+# # List additional groups of dependencies here (e.g. development
+# # dependencies). Users will be able to install these using the "extras"
+# # syntax, for example:
+# #
+# #   $ pip install sampleproject[dev]
+# #
+# # Similar to `dependencies` above, these must be valid existing
+# # projects.
+# [project.optional-dependencies] # Optional
+# dev = ["check-manifest", "build", "twine", "versioneer", "flake8", "autopep8", "ipdb"]
+# test = ["coverage"]
+
+# # List URLs that are relevant to your project
+# #
+# # This field corresponds to the "Project-URL" and "Home-Page" metadata fields:
+# # https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use
+# # https://packaging.python.org/specifications/core-metadata/#home-page-optional
+# #
+# # Examples listed include a pattern for specifying where the package tracks
+# # issues, where the source is hosted, where to say thanks to the package
+# # maintainers, and where to support the project financially. The key is
+# # what's used to render the link text on PyPI.
+# [project.urls]  # Optional
+# "Homepage" = "https://github.com/pypa/sampleproject"
+# "Bug Reports" = "https://github.com/pypa/sampleproject/issues"
+# "Funding" = "https://donate.pypi.org"
+# "Say Thanks!" = "http://saythanks.io/to/example"
+# "Source" = "https://github.com/pypa/sampleproject/"
+
+# # The following would provide a command line executable called `example`
+# # which executes the function `main` from this package when invoked.
+# [project.scripts]  # Optional
+# example = "sample_package.main:main"
+
+# This is configuration specific to the `setuptools` build backend.
+# If you are using a different build backend, you will need to change this.
+# [tool.setuptools]
+# If there are data files included in your packages that need to be
+# installed, specify them here.
+# package-data = {"sample_package" = ["*.rst", "*.txt", "*.java", "*.class"]}
+
+[build-system]
+# These are the assumed default build requirements from pip:
+# https://pip.pypa.io/en/stable/reference/pip/#pep-517-and-518-support
+requires = ["setuptools>=43.0.0", "wheel", "tomli"]
+build-backend = "setuptools.build_meta"
+
+[tool.versioneer]
+VCS = "git"
+style = "pep440"
+versionfile_source = "src/actinet/_version.py"
+versionfile_build = "actinet/_version.py"
+tag_prefix = "v"
+parentdir_prefix = "actinet-"

actinet-0.0.dev0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

actinet-0.0.dev0/setup.py

@@ -0,0 +1,92 @@
+import sys
+import os.path
+# https://github.com/python-versioneer/python-versioneer/issues/193
+sys.path.insert(0, os.path.dirname(__file__))
+
+from setuptools import setup, find_packages
+import codecs
+
+import versioneer
+
+
+
+def main():
+
+    with open("README.md", "r") as fh:
+        long_description = fh.read()
+
+    setup(
+        name="actinet",
+        version=versioneer.get_version(),    # Do not edit
+        cmdclass=versioneer.get_cmdclass(),  # Do not edit
+        python_requires=">=3.8, <4",
+        description="Activity detection algorithm compatible with the UK Biobank Accelerometer Dataset",
+        long_description=long_description,  # Do not edit. See README.md
+        long_description_content_type="text/markdown",
+        keywords="example, setuptools, versioneer",
+        url="https://github.com/OxWearables/actinet",
+        download_url="https://github.com/OxWearables/actinet",
+        author=get_string("__author__"),                      # Do not edit. see src/actinet/__init__.py
+        maintainer=get_string("__maintainer__"),              # Do not edit. see src/actinet/__init__.py
+        maintainer_email=get_string("__maintainer_email__"),  # Do not edit. See src/actinet/__init__.py
+        license=get_string("__license__"),                    # Do not edit. See src/actinet/__init__.py
+
+        # This is for PyPI to categorize your project. See: https://pypi.org/classifiers/
+        classifiers=[
+            "Programming Language :: Python :: 3",
+            "Topic :: Scientific/Engineering",
+        ],
+
+        # Where to find the source code
+        packages=find_packages(where="src", exclude=("test", "tests")),
+        package_dir={"": "src"},
+        # What other files to include, e.g. *.class if the package uses some Java code.
+        package_data={"actinet": ["*.txt", "*.rst", "*.md"]},
+
+        # Dependencies
+        install_requires=[],
+
+        extras_require={
+            "dev": [
+                "versioneer",
+                "twine",
+                "ipdb",
+                "flake8",
+                "autopep8",
+            ],
+            "docs": [
+                "sphinx>=4.2",
+                "sphinx_rtd_theme>=1.0",
+                "readthedocs-sphinx-search>=0.1",
+                "docutils<0.18",
+            ]
+        },
+
+        # Define entry points for command-line scripts, e.g.: `$ hello --name Alice`
+        entry_points={
+            "console_scripts": [
+                "hello=actinet.main:main",
+            ],
+        },
+
+    )
+
+
+def read(rel_path):
+    here = os.path.abspath(os.path.dirname(__file__))
+    with codecs.open(os.path.join(here, rel_path), 'r') as fp:
+        return fp.read()
+
+
+def get_string(string, rel_path="src/actinet/__init__.py"):
+    for line in read(rel_path).splitlines():
+        if line.startswith(string):
+            delim = '"' if '"' in line else "'"
+            return line.split(delim)[1]
+    else:
+        raise RuntimeError(f"Unable to find {string}.")
+
+
+
+if __name__ == "__main__":
+    main()