adding generally useful networks and losses

Author: Ritvik Vasan

README.md

@@ -1,104 +1,17 @@
 # pointcloudutils
 
-[![Build Status](https://github.com/AllenCellModeling/pointcloudutils/workflows/Build%20Main/badge.svg)](https://github.com/AllenCellModeling/pointcloudutils/actions)
-[![Documentation](https://github.com/AllenCellModeling/pointcloudutils/workflows/Documentation/badge.svg)](https://AllenCellModeling.github.io/pointcloudutils/)
-[![Code Coverage](https://codecov.io/gh/AllenCellModeling/pointcloudutils/branch/main/graph/badge.svg)](https://codecov.io/gh/AllenCellModeling/pointcloudutils)
-
 Utils and networks for point cloud related projects at AICS
 
 ---
 
-## Features
-
--   Store values and retain the prior value in memory
--   ... some other functionality
-
-## Quick Start
+First install cyto_dl. Then 
 
-```python
-from pointcloudutils import Example
+```bash
+pip install -e .
 
-a = Example()
-a.get_value()  # 10
+pip install "git+https://github.com/erikwijmans/Pointnet2_PyTorch.git#egg=pointnet2_ops&subdirectory=pointnet2_ops_lib"
+pip install --upgrade https://github.com/unlimblue/KNN_CUDA/releases/download/0.2/KNN_CUDA-0.2-py3-none-any.whl
 ```
 
-## Installation
-
-**Stable Release:** `pip install pointcloudutils`<br>
-**Development Head:** `pip install git+https://github.com/AllenCellModeling/pointcloudutils.git`
-
-## Documentation
-
-For full package documentation please visit [AllenCellModeling.github.io/pointcloudutils](https://AllenCellModeling.github.io/pointcloudutils).
-
-## Development
-
-See [CONTRIBUTING.md](CONTRIBUTING.md) for information related to developing the code.
-
-## The Four Commands You Need To Know
-
-1. `pip install -e .[dev]`
-
-    This will install your package in editable mode with all the required development
-    dependencies (i.e. `tox`).
-
-2. `make build`
-
-    This will run `tox` which will run all your tests in both Python 3.7
-    and Python 3.8 as well as linting your code.
-
-3. `make clean`
-
-    This will clean up various Python and build generated files so that you can ensure
-    that you are working in a clean environment.
-
-4. `make docs`
-
-    This will generate and launch a web browser to view the most up-to-date
-    documentation for your Python package.
-
-#### Additional Optional Setup Steps:
-
--   Turn your project into a GitHub repository:
-    -   Make an account on [github.com](https://github.com)
-    -   Go to [make a new repository](https://github.com/new)
-    -   _Recommendations:_
-        -   _It is strongly recommended to make the repository name the same as the Python
-            package name_
-        -   _A lot of the following optional steps are *free* if the repository is Public,
-            plus open source is cool_
-    -   After a GitHub repo has been created, run the commands listed under:
-        "...or push an existing repository from the command line"
--   Register your project with Codecov:
-    -   Make an account on [codecov.io](https://codecov.io)(Recommended to sign in with GitHub)
-        everything else will be handled for you.
--   Ensure that you have set GitHub pages to build the `gh-pages` branch by selecting the
-    `gh-pages` branch in the dropdown in the "GitHub Pages" section of the repository settings.
-    ([Repo Settings](https://github.com/AllenCellModeling/pointcloudutils/settings))
--   Register your project with PyPI:
-    -   Make an account on [pypi.org](https://pypi.org)
-    -   Go to your GitHub repository's settings and under the
-        [Secrets tab](https://github.com/AllenCellModeling/pointcloudutils/settings/secrets/actions),
-        add a secret called `PYPI_TOKEN` with your password for your PyPI account.
-        Don't worry, no one will see this password because it will be encrypted.
-    -   Next time you push to the branch `main` after using `bump2version`, GitHub
-        actions will build and deploy your Python package to PyPI.
-
-#### Suggested Git Branch Strategy
-
-1. `main` is for the most up-to-date development, very rarely should you directly
-   commit to this branch. GitHub Actions will run on every push and on a CRON to this
-   branch but still recommended to commit to your development branches and make pull
-   requests to main. If you push a tagged commit with bumpversion, this will also release to PyPI.
-2. Your day-to-day work should exist on branches separate from `main`. Even if it is
-   just yourself working on the repository, make a PR from your working branch to `main`
-   so that you can ensure your commits don't break the development head. GitHub Actions
-   will run on every push to any branch or any pull request from any branch to any other
-   branch.
-3. It is recommended to use "Squash and Merge" commits when committing PR's. It makes
-   each set of changes to `main` atomic and as a side effect naturally encourages small
-   well defined PR's.
-
-
 **Allen Institute Software License**
 

pointcloudutils/bin/__init__.py

@@ -0,0 +1,3 @@
+from .shapenet import ShapenetDataModule
+from .geomshapes import GeometricShapesDataModule
+from .cellpack import CellPackDataModule