CopyNet implementation with TensorFlow 2
- Incorporating Copying Mechanism in Sequence-to-Sequence Learning
- Uses
TensorFlow 2.0and above APIs withtf.kerastoo - Adapted from AllenNLP's PyTorch implementation, their blog referenced below was very helpful to understand the math from an implementation perspective
Environment to run examples
Setup
- Copy
sample.envto.envand enter appropriate values for the variables - A brief description of each is provided as a comment in that file
- Post that run,
./setup-env.sh [--no-docker]
- Uses env file to configure project environment
- Builds required docker images (if you don't wanna use Docker then pass
--no-dockeroption to thesetup-env.shscript) - Makes a python environment and installes required packages in it
- Prepares an
lock.envfile. Do not edit/ delete it
Rebuilding environment
- You may change environment config in the process of development
- This includes adding a new python package to requirements.txt
- After changing run,
./setup-env.sh [--no-docker] - If you do not want Docker, then pass
--no-dockeroption similar to before
Start environment
- At the end of setup script you will be shown the commands to start the environments
- They are,
./start-env.sh nb # For Dockerized jupyter server ./start-env.sh bash # For Dockerized bash
- It is not necessary to use the
start-env.shscript for virtualenv, the regularsourcecommand to activate it is enough
Note on Dockerized environment
- The dockerized environment is specifically helpful and recommended when
using
GPU - It takes care of many nuances involved in setting up CUDA. Your host machine should just have correct NVIDIA drivers and nothing else
- It is recommended to run the examples in this environment to ensure all correct dependencies are met
Run examples
- Instructions to run an example are detailed in its own folders respectively
References
Metadata
Release files for copynet-tf 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| copynet-tf-0.2.0.tar.gz | 21.5 kB | Without provenance | Details for copynet-tf-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| copynet_tf-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for copynet_tf-0.2.0-py3-none-any.whl |
Total release size: 47.0 kB
Release files / copynet-tf-0.2.0.tar.gz
| Download URL | copynet-tf-0.2.0.tar.gz |
|---|---|
| Size | 21.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4316f412c45375fe30cc533264d3321632280dac31a546f0ce8a361aa37598b
|
|
BLAKE2b-256 checksum How to use checksums |
7d215942b8045a8c4c31d3f333283fcbffd45995dd61a61d86e77b33b88d0007
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.2
|
Release files / copynet_tf-0.2.0-py3-none-any.whl
| Download URL | copynet_tf-0.2.0-py3-none-any.whl |
|---|---|
| Size | 25.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2992ceb84048f7a5f8e105f37afead20cf89ec4cbdc25525e7692f1925aa693
|
|
BLAKE2b-256 checksum How to use checksums |
8dd316f3a2df1445f98c077b5051cabf085a7a17ac49f51c523b839f3a246a45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.2
|
Security for copynet-tf 0.2.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.