-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #32 from fspiga/devel-gpu
Releasing QE-GPU v1.0
- Loading branch information
Showing
249 changed files
with
22,248 additions
and
20,573 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| .github/ISSUE_TEMPLATE.md export-ignore | ||
| .github/PULL_REQUEST_TEMPLATE.md export-ignore | ||
| *.github export-ignore | ||
| .gitignore export-ignore |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| ### Version of QE-GPU | ||
|
|
||
| Write here (refer to git TAG or git hash) | ||
|
|
||
| ### Expected behavior/result | ||
|
|
||
| Write here... | ||
|
|
||
| ### Actual behavior/result | ||
|
|
||
| Write here... | ||
|
|
||
| ### Steps to reproduce behavior/result | ||
|
|
||
| Together with instructions how to reproduce the problem and where input files and pseudo-potentials are located), please report: | ||
| * architecture of your machine (e.g. x86, POWER, CRAY) | ||
| * type of GPU you are using (remember, Tesla P100 are recommended) | ||
| * version and flavor of MPI (e.g. Open MPI 1.x.y, 2.x.y, 3.x.y, MVAPICH2, MVAPICH2-GDR, Spectrum MPI) | ||
| * PGI compiler (both major and minor version, e.g. 17.4, specify also if it is the _Community_ version) | ||
| * the full ``DFLAGS`` line as specified in the make.inc | ||
| * how you run the code (number of MPI/GPU, number of threads) | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| Thank you for creating a pull request to contribute to QE-GPU code! Before you open the request please review the following guidelines and tips to help it be more easily integrated: | ||
| * Describe the scope of your change -- i.e. what the change does and what parts of the code were modified. This will help us understand any risks of integrating the code. | ||
| * Describe any known limitations with your change. For example if the change doesn't apply to a supported platform of the library please mention it. | ||
| * Please run any tests or examples that can exercise your modified code. We strive to not break users of the code and running tests/examples helps with this process. | ||
|
|
||
| Thank you again for contributing! Testing and integration of any change will occur as soon as possible, but be aware it is impossible to immediately respond to every request. There is no need to bump or check in on a pull request (it will clutter the discussion of the request). | ||
|
|
||
| After reviewing the guidelines above you can delete this text from the pull request and proceed further | ||
|
|
||
|
|
||
| ### Description of the Pull Request (PR) | ||
|
|
||
| Write your description of the PR here. Be sure to include as much background, | ||
| and details necessary for the reviewers to understand exactly what this is | ||
| fixing or enhancing. | ||
|
|
||
|
|
||
| ### This fixes or addresses the following GitHub issues | ||
|
|
||
| - Ref: # |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| *.a | ||
| *.o | ||
| *.mod | ||
| *_tmp.f90 | ||
| *.x | ||
| *.so | ||
| *.pyc | ||
| .github/ISSUE_TEMPLATE.md | ||
| .github/PULL_REQUEST_TEMPLATE.md | ||
| *.github |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,109 @@ | ||
| # Contributing | ||
|
|
||
| When contributing to QE-GPU, it is important to properly communicate the | ||
| gist of the contribution. If it is a simple code or editorial fix, simply | ||
| explaining this within the GitHub Pull Request (PR) will suffice. But if this | ||
| is a larger fix or Enhancement, it should be first discussed with the project | ||
| leader or developers. | ||
|
|
||
| Please note we have a code of conduct, described below. Please follow it in | ||
| all your interactions with the project members and users. | ||
|
|
||
| ## Pull Request Process | ||
|
|
||
| 1. Bug fix and feature enhancements PRs should be sent to only to be submitted | ||
| against devel-gpu or other developmen branches. | ||
| 2. Follow the existing code style precedent. This does not need to be strictly | ||
| defined as there are many thousands of lines of examples. Note the lack | ||
| of tabs anywhere in the project, parentheses and spacing, curly bracket | ||
| locations, source code layout, variable scoping, etc. and follow the | ||
| project's standards. | ||
| 3. Ensure any install or build dependencies are removed before doing a build | ||
| to test your PR locally. | ||
| 4. The project's default copyright and header have been included in any new | ||
| source files. | ||
| 5. All (major) changes to QE-GPU must be documented somewhere. If your PR | ||
| changes a core functionality, please include clear description of the | ||
| changes in your PR so that the docs can be updated, or better, submit a | ||
| sister PR to update the docs directly. | ||
| 6. Is the code human understandable? This can be accomplished via a clear code | ||
| style as well as documentation and/or comments. | ||
| 7. The pull request will be reviewed by others, and the final merge must be | ||
| done by the QE-GPU project lead, @fspiga (or approved by him). | ||
|
|
||
|
|
||
| # Code of Conduct | ||
|
|
||
| ## Our Pledge | ||
|
|
||
| In the interest of fostering an open and welcoming environment, we as | ||
| contributors and maintainers pledge to making participation in our project and | ||
| our community a harassment-free experience for everyone, regardless of age, body | ||
| size, disability, ethnicity, gender identity and expression, level of experience, | ||
| nationality, personal appearance, race, religion, or sexual identity and | ||
| orientation. | ||
|
|
||
| ## Our Standards | ||
|
|
||
| Examples of behavior that contributes to creating a positive environment | ||
| include: | ||
|
|
||
| * Using welcoming and inclusive language | ||
| * Being respectful of differing viewpoints and experiences | ||
| * Gracefully accepting constructive criticism | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| * The use of sexualized language or imagery and unwelcome sexual attention or | ||
| advances | ||
| * Trolling, insulting/derogatory comments, and personal or political attacks | ||
| * Public or private harassment | ||
| * Publishing others' private information, such as a physical or electronic | ||
| address, without explicit permission | ||
| * Other conduct which could reasonably be considered inappropriate in a | ||
| professional setting | ||
|
|
||
| ### Our Responsibilities | ||
|
|
||
| Project maintainers are responsible for clarifying the standards of acceptable | ||
| behavior and are expected to take appropriate and fair corrective action in | ||
| response to any instances of unacceptable behavior. | ||
|
|
||
| Project maintainers have the right and responsibility to remove, edit, or | ||
| reject comments, commits, code, wiki edits, issues, and other contributions | ||
| that are not aligned to this Code of Conduct, or to ban temporarily or | ||
| permanently any contributor for other behaviors that they deem inappropriate, | ||
| threatening, offensive, or harmful. | ||
|
|
||
| ## Scope | ||
|
|
||
| This Code of Conduct applies both within project spaces and in public spaces | ||
| when an individual is representing the project or its community. Examples of | ||
| representing a project or community include using an official project e-mail | ||
| address, posting via an official social media account, or acting as an appointed | ||
| representative at an online or offline event. Representation of a project may be | ||
| further defined and clarified by project maintainers. | ||
|
|
||
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the project leader ([email protected]. All | ||
| complaints will be reviewed and investigated and will result in a response | ||
| that is deemed necessary and appropriate to the circumstances. The project | ||
| team is obligated to maintain confidentiality with regard to the reporter of | ||
| an incident. Further details of specific enforcement policies may be posted | ||
| separately. | ||
|
|
||
| Project maintainers, contributors and users who do not follow or enforce the | ||
| Code of Conduct in good faith may face temporary or permanent repercussions | ||
| with their involvement in the project as determined by the project's leader(s). | ||
|
|
||
| ## Attribution | ||
|
|
||
| This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
| available at [http://contributor-covenant.org/version/1/4][version] | ||
|
|
||
| [homepage]: http://contributor-covenant.org | ||
| [version]: http://contributor-covenant.org/version/1/4/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.