water
Here are 367 public repositories matching this topic...
-
Updated
Mar 26, 2020 - JavaScript
-
Updated
Aug 15, 2019 - HLSL
-
Updated
Aug 23, 2018 - JavaScript
-
Updated
Jun 17, 2020 - C#
-
Updated
Sep 23, 2019 - C++
Hello,
Is there documentation on exactly how share-weights are calculated in GCAM or a portion of code that lays out the logic for how this is done? @rjplevin are working on implementing policies for electrification, and part of this process requires ensuring that the share-weights for the electric technologies are high enough to ensure the standard can be met. I have a basic understanding of h
-
Updated
Nov 14, 2019 - C++
-
Updated
Jul 19, 2018 - R
-
Updated
Jun 6, 2020 - C++
-
Updated
Jan 10, 2019 - C
The people publishing to the blog post are not necessarily going to be technical.
We need a README that documents in detail how to go about publishing a blog post.
This should likely be in two steps:
- How to set the project up locally so you can write posts
- How to actually write a post (and what the process is for it to end up on the blog)
For the second we'll likely need to expl
-
Updated
May 13, 2020 - Swift
-
Updated
Jan 11, 2018 - QML
-
Updated
Nov 20, 2019 - Java
-
Updated
Jun 24, 2020 - R
-
Updated
Jul 10, 2020 - Python
A simple example when audit is enabled:
- User (1) does a mistake inserting nodes without elevation or with a bad touple sector/expl
- Later, another user (2) is dealing with an EPA model and the export control functions checks it
- Using audit it is possible to identify who did the mistake
- Using notify, a message could be sended and promted on QGIS (1) with something like this:
`INFO: S
Here is a list of things that could be improved in the documentation:
- Use Napoleon to improve the readability of Google-style docstrings and code pages.
- Add the version number somewhere that shows up on every page.
- Collect all of the todo's in the code into a page. [sphinx.ext.todo](http://www.sphinx-doc.org/en/master/
-
Updated
May 5, 2020 - C
From the pyOpenSci review:
Maybe pydocstyle can help to check static docstrings (you also can ignore erros you think any one doesn't apply for pydov). If you want to check dynamic docstrings you can use numpydoc --validate (https://numpydoc.readthedocs.io/en/latest/validation.html#validating-numpydoc-docstrings) you can check one example
Improve this page
Add a description, image, and links to the water topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the water topic, visit your repo's landing page and select "manage topics."
The caustics texture is currently being sampled without taking flow into account. This could be something worth playing aroud with and seeing if we could get good results.
A good place to look would be how flow affects the sampling of the foam texture in the Ocean Shader.