-
Updated
Jul 22, 2021 - C
gravity
Here are 282 public repositories matching this topic...
-
Updated
Mar 30, 2021 - Go
-
Updated
Apr 20, 2021 - Go
-
Updated
Dec 2, 2017 - Objective-C
-
Updated
Aug 17, 2021 - C++
-
Updated
Aug 18, 2021 - Python
-
Updated
Oct 31, 2020 - Python
-
Updated
Jul 20, 2017 - Swift
-
Updated
Apr 8, 2021 - Python
-
Updated
Jul 24, 2021 - Kotlin
-
Updated
Aug 6, 2021 - Python
Description of the desired feature
Would be nice to have a simple example on how to use the DatasetAccessorPrismLayer class.
The example should use the prism_layer function to define a layer of prisms and then use the prism_layer accessor to use some of the methods and properties defined in the DatasetAccessorPrismLayer class.
It should be very similar to the one in the Example Ga
-
Updated
Apr 14, 2017 - Java
-
Updated
Mar 30, 2017 - HTML
-
Updated
Jan 4, 2021 - C#
-
Updated
Jul 25, 2017 - Kotlin
-
Updated
Jun 10, 2019 - C++
-
Updated
Jan 27, 2021 - Python
Hi possible contributors!
Something that would make for a great first issue is to download and compile SWIFT, and then check out the examples and try running a few. The majority of these examples currently use python2 scripts for initial conditions generation and analysis; it would be great if you could upgrade these to use python3 instead.
Thanks!
-
Updated
May 17, 2019 - Swift
-
Updated
Mar 23, 2020 - Python
-
Updated
Oct 28, 2018 - Java
-
Updated
Aug 12, 2021 - JavaScript
-
Updated
Jul 11, 2020 - Assembly
Improve this page
Add a description, image, and links to the gravity topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the gravity topic, visit your repo's landing page and select "manage topics."


castro.change_max = 1.0means that the timestep can only ever stay the same or decrease relative to its initial value. I think we should disallow this value, I have a hard time imagining a use case for this (if you want a fixed timestep, use fixed_dt, and if you want a timestep cap but still allow the timestep to decrease, use max_dt). It causes problems with the retry functionality.