Metadata-Version: 2.1
Name: redpic
Version: 0.9.3
Summary: Relativistic Difference Scheme Particle-in-Cell code (REDPIC)
Home-page: https://github.com/fuodorov/redpic
Author: Vyacheslav Fedorov
Author-email: slava@fuodorov.ru
Project-URL: Bug Reports, https://github.com/fuodorov/redpic/issues
Project-URL: PyPi, https://pypi.org/project/redpic/
Project-URL: Documentation, https://fuodorov.github.io/redpic/
Project-URL: Source, https://github.com/fuodorov/redpic/
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Classifier: Intended Audience :: Science/Research
Classifier: Topic :: Scientific/Engineering :: Physics
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: kenv==0.3.0.3
Requires-Dist: numba==0.57.1
Requires-Dist: numpy==1.24.4
Requires-Dist: pandas==2.0.3
Requires-Dist: periodictable==1.6.1
Requires-Dist: scipy==1.11.2

# Relativistic Difference Scheme Particles-In-Cell (REDPIC)

[![PyPI - Version](https://img.shields.io/pypi/v/redpic?color=blue)](https://pypi.org/project/redpic/)
[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/redpic?color=blue)](https://pypi.org/project/redpic/)

[![Check](https://github.com/fuodorov/redpic/actions/workflows/check.yml/badge.svg)](https://github.com/fuodorov/redpic/actions/workflows/check.yml)
[![Test](https://github.com/fuodorov/redpic/actions/workflows/test.yml/badge.svg)](https://github.com/fuodorov/redpic/actions/workflows/test.yml)
[![Release](https://github.com/fuodorov/redpic/actions/workflows/release.yml/badge.svg)](https://github.com/fuodorov/redpic/actions/workflows/release.yml)

This PIC code has been developed since 2022 as an alternative to 
[ASTRA](https://www.desy.de/~mpyflo/), 
[WARP](https://bitbucket.org/berkeleylab/warp/), 
[XTRACK](https://xsuite.readthedocs.io/en/latest/) 
and other codes. 

For particle dynamics simulation using finite difference scheme relativistic.

## Table of content 

-   [Getting Started](#getting-started)
    -   [Local build and launch](#local-build-and-launch)
    -   [Documentation](#documentation)
        -   [Adding a new section](#adding-a-new-section)
    -   [Additional resources](#additional-resources)
    -   [CUDA installation](#cuda-installation)
-   [Prerequisites](#prerequisites)
    -   [Latex](#latex)
-   [Useful Resources](#useful-resources)
    -   [IDE](#ide)
-   [Authors](#authors)
-   [Licence](#license)
-   [Contributing](#contributing)
    -   [Dependencies](#dependencies)
    -   [Formatting](#formatting)
    -   [Tests](#tests)
    -   [Maintaining](#maintaining)

## Getting Started

### Local build and launch

To build our application and create a Docker image, it will be enough to run the following command:

`docker build -t redpic .`

To launch the application, use the command:

`docker run -it redpic`

### Documentation

The documentation contains all the Latex files needed to generate documentation. 
The main source files are located in the `manual`.

* [main.tex](/manual/main.tex) is documentation source file. 
The final PDF can be found [here](https://github.com/fuodorov/redpic/releases/latest).

[main.tex](/manual/main.tex) is the source file that Latex compiler will use to generate the paper. 
However, in order to keep the code cleaner, the main sections of the paper are all located in the [sections](/manual/sections). 
In this way you will experience less merging issues when two or more people are working on the same doc.

Just edit the text in the relative Latex file (e.g., introduction, methodology, etc.) and you should be ready to go. 
No need to change any other file.

#### Adding a new section

Just copy a section file (e.g., [introduction.tex](/manual/sections/introduction.tex)) paste it in the same directory. 
Rename the pasted file (e.g. first_chapter.tex) and add this file to [main.tex](/manual/main.tex).

### Additional Resources

Alternatively you can find great resources on the 
[Overleaf Tutorial website](https://www.overleaf.com/learn/latex/Tutorials) or on 
[Latex wikibooks](https://en.wikibooks.org/wiki/LaTeX).

### CUDA installation

For CUDA implementation we use [Numba](https://numba.pydata.org) library.
For more information about CUDA installation see [Numba CUDA installation guide](https://numba.pydata.org/numba-doc/dev/cuda/overview.html#installing-cuda).

## Prerequisites

#### Latex

Latex IDE and compiler installed locally on your machine. 
We recommend using a PyCharm plugin called [TeXiFy IDEA](https://plugins.jetbrains.com/plugin/9473-texify-idea) as IDE and 
[miktex](https://miktex.org) as Latex compiler  

Alternatively you can push your code to Overleaf using git and only use Overleaf. 
We would discourage you from doing this! Overleaf should only be used for the review.

## Useful Resources

### IDE

You may want to take advantage of the power of IDEs. 
For Python We would recommend using [PyCharm](https://www.jetbrains.com/pycharm/). 

Alternatives are:

* [Visual Studio](https://code.visualstudio.com)
* [Atom](https://atom.io/)

### Git

You should install [git](https://git-scm.com) on your computer. And have [GitHub](https://github.com) account.

## Authors

* **[Vyacheslav Fedorov](https://github.com/fuodorov)** - *Initial work*
* **[Danila Nikiforov](https://github.com/Danila-Nikiforov)** - *Initial work*

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details

## Contributing

### Dependencies
Use `make deps` command to install library, its production and development dependencies.

### Formatting
Use `make format` to autoformat code with black tool. 

### Linter
Use `make lint` to run only linters for current python version

### Test
Use `make test` to run test for current python version

### Maintaining
If pull request consists of several meaningful commits, that should be preserved, 
then use "Rebase and merge" option. Otherwise use "Squash and merge". 

New release (changelog, tag and pypi upload) will be automatically created 
on each push to master via Github Actions workflow.
