Skip to content

Commit

Permalink
Dev/v1.0.1 (#58)
Browse files Browse the repository at this point in the history
* update (#57)

* update

* update datautil

* add VBench prompt

* update eval

* update eval

* update intepolation

* add vbench eval

* Dev/sdedit implementation (#56)

* Update utils.py

* update

* update

* update

---------

Co-authored-by: YuKun Zhou <90625606+1zeryu@users.noreply.github.com>
  • Loading branch information
zhengzangw and 1zeryu authored Apr 20, 2024
1 parent 2c64d1c commit 570be6e
Show file tree
Hide file tree
Showing 71 changed files with 17,570 additions and 2,753 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,7 @@ samples/
samples
logs/
pretrained_models/
evaluation_results/
*.swp

# Secret files
Expand Down
15 changes: 12 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,6 @@ To contribute to Open-Sora, we would like to first guide you to set up a proper

You can refer to the [Installation Section](./README.md#installation) and replace `pip install -v .` with `pip install -v -e .`.


### Code Style

We have some static checks when you commit your code change, please make sure you can pass all the tests and make sure the coding style meets our requirements. We use pre-commit hook to make sure the code is aligned with the writing standard. To set up the code style checking, you need to follow the steps below.
Expand All @@ -21,7 +20,6 @@ pre-commit install

Code format checking will be automatically executed when you commit your changes.


## Contribution Guide

You need to follow these steps below to make contribution to the main repository via pull request. You can learn about the details of pull request [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
Expand Down Expand Up @@ -68,7 +66,6 @@ git push origin main

You should not make changes to the `main` branch of your forked repository as this might make upstream synchronization difficult. You can create a new branch with the appropriate name. General branch name format should start with `hotfix/` and `feature/`. `hotfix` is for bug fix and `feature` is for addition of a new feature.


```shell
git checkout -b <NEW-BRANCH-NAME>
```
Expand All @@ -89,3 +86,15 @@ git push -u origin <NEW-BRANCH-NAME>
You can now create a pull request on the GitHub webpage of your repository. The source branch is `<NEW-BRANCH-NAME>` of your repository and the target branch should be `main` of `hpcaitech/Open-Sora`. After creating this pull request, you should be able to see it [here](https://github.com/hpcaitech/Open-Sora/pulls).

The Open-Sora team will review your code change and merge your code if applicable.

## FQA

1. `pylint` cannot recognize some members:

Add this into your `settings.json` in VSCode:

```json
"pylint.args": [
"--generated-members=numpy.* ,torch.*,cv2.*",
],
```
Loading

0 comments on commit 570be6e

Please sign in to comment.