README.md 1.99 KB
Newer Older
Dongz's avatar
Dongz committed
1
# LightX2V: Light Video Generation Inference Framework
helloyongyang's avatar
helloyongyang committed
2

helloyongyang's avatar
helloyongyang committed
3
4
5
6
7
<div align="center">
  <picture>
    <img alt="LightLLM" src="assets/img_lightx2v.jpg" width=75%>
  </picture>
</div>
helloyongyang's avatar
helloyongyang committed
8

helloyongyang's avatar
helloyongyang committed
9
--------------------------------------------------------------------------------
helloyongyang's avatar
helloyongyang committed
10

11
## Fast Start Up With Conda
helloyongyang's avatar
helloyongyang committed
12

Dongz's avatar
Dongz committed
13
```shell
14
git clone https://github.com/ModelTC/lightx2v.git lightx2v && cd lightx2v
15
git submodule update --init --recursive
16
17
18
19
20
21

conda create -n lightx2v python=3.11 && conda activate lightx2v
pip install -r requirements.txt

# modify the parameters of the running script
bash scripts/run_hunyuan_t2v.sh
helloyongyang's avatar
helloyongyang committed
22
23
```

24
## Fast Start Up With Docker
helloyongyang's avatar
helloyongyang committed
25

Dongz's avatar
Dongz committed
26
```shell
zhiwei.dong's avatar
zhiwei.dong committed
27
28
docker pull lightx2v/lightx2v:latest
docker run -it --rm --gpus all --ipc=host lightx2v/lightx2v:latest
helloyongyang's avatar
helloyongyang committed
29
```
Dongz's avatar
Dongz committed
30

31
## Contributing Guidelines
Dongz's avatar
Dongz committed
32

33
We have prepared a `pre-commit` hook to enforce consistent code formatting across the project. If your code complies with the standards, you should not see any errors, you can clean up your code following the steps below:
Dongz's avatar
Dongz committed
34
35
36
37
38
39
40

1. Install the required dependencies:

```shell
    pip install ruff pre-commit
```

41
2. Then, run the following command before commit:
Dongz's avatar
Dongz committed
42
43
44
45
46

```shell
    pre-commit run --all-files
```

47
48
49
50
51
52
3. Finally, please double-check your code to ensure it complies with the following additional specifications as much as possible:
  - Avoid hard-coding local paths: Make sure your submissions do not include hard-coded local paths, as these paths are specific to individual development environments and can cause compatibility issues. Use relative paths or configuration files instead.
  - Clear error handling: Implement clear error-handling mechanisms in your code so that error messages can accurately indicate the location of the problem, possible causes, and suggested solutions, facilitating quick debugging.
  - Detailed comments and documentation: Add comments to complex code sections and provide comprehensive documentation to explain the functionality of the code, input-output requirements, and potential error scenarios.

Thank you for your contributions!