Skip to content
#

computational-physics

Here are 214 public repositories matching this topic...

PavelBlend
PavelBlend commented Dec 21, 2019

Hello.

I often use python api documentation.
And I noticed that the descriptions of the accepted parameters of the classes were gone.
You have to look for these parameters in the source code in the src\python\ folder.
It is advisable to make sure that there is no need to look for information in the source code.
For all Python API information to be available here:
https://fluidenginedevel

freud
joostvanzwieten
joostvanzwieten commented Aug 28, 2018

We currently use numpy.testing.assert_array_almost_equal and friends over a hundred times in the test suite. While this works with the unittest framework it's more elegant to add support for comparing arrays to (our own subclass of) unittest.TestCase, e.g. by redefining the methods assertEqual and assertAlmostEqual. The methods should produce helpful error messages indicating where array

arm61
arm61 commented Aug 26, 2018

Currently the marker size for the particles in the mpl plots is deteremined based on the size of the simulation cell. However, with the release 1.1, it is now possible to change the forcefield and the values of A and B, therefore requiring the particle marker size to scale with both the simulation cell size and the nature of the potential model.

I reckon it is best to have the marker size be d

Improve this page

Add a description, image, and links to the computational-physics topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the computational-physics topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.