summaryrefslogtreecommitdiff
path: root/numpy/random
Commit message (Collapse)AuthorAgeFilesLines
...
* DOC: update docs and comments for move of mailing list to python.orgRalf Gommers2017-03-261-1/+1
|
* MAINT: Remove asbytes where a b prefix would sufficeEric Wieser2017-03-251-2/+1
| | | | | | | | Since we only need to support python 2, we can remove any case where we just pass a single string literal and use the b prefix instead. What we can't do is transform asbytes("tests %d" % num), because %-formatting fails on bytes in python 3.x < 3.5.
* Revert gh-8570.Charles Harris2017-03-132-42/+1
| | | | | | | | BUG: fix issue #8250 where np.random.permutation fail. This reverts commit 7a73bad2d9c04e4f16e87dbed9d7b627327fe814. Closes #8776.
* Merge pull request #8570 from evanlimanto/random-permutation-shuffle-fixEric Wieser2017-03-122-1/+42
|\ | | | | BUG: fix issue #8250 when np.array gets called on an invalid sequence
| * BUG: fix issue #8250 where np.random.permutation fails when np.array gets ↵Evan Limanto2017-03-102-1/+42
| | | | | | | | called on an invalid sequence.
* | BUG: Fix assert statements in random.choice testsMarein Könings2017-02-281-5/+5
|/ | | | Unless I am very much mistaken these 'assert_(x,y)' calls should really be 'assert_equal(x,y)'.
* TST: work around isfinite inconsistency on i386Julian Taylor2017-01-171-1/+3
| | | | | inlined isfinite on i386 does not work for DBL_MAX / 1e17 + DBL_MAX as with extended precision this is not smaller equal than DBL_MAX.
* TST: remove a duplicate test. Closes gh-8447.Ralf Gommers2017-01-061-4/+0
|
* single too argument + mention in release docs.Oscar Villellas2017-01-031-9/+5
|
* Documentation fix and proper handling of toleranceOscar Villellas2017-01-031-10/+15
|
* fixed merged testOscar Villellas2017-01-031-14/+8
|
* Merge remote-tracking branch 'numpy-org/master' into mult-normOscar Villellas2017-01-0314-840/+2145
|\
| * DOC: Fixed minor typoMikhail Pak2016-12-131-1/+1
| |
| * BUG: Better check for invalid bounds in np.random.uniform.Alistair Muldal2016-11-022-0/+6
| | | | | | | | Also check for invalid bounds when low= and high= are arraylike rather than scalar (closes #8226)
| * DOC: Clean up lomax and genpareto references.wrwrwr2016-10-281-3/+3
| |
| * MAINT, DOC: Update some scipy.stats references.wrwrwr2016-10-281-27/+27
| | | | | | | | Closes #5813.
| * Merge pull request #8173 from aixtools/issue8118Charles Harris2016-10-221-3/+6
| |\ | | | | | | BLD: Enable build on AIX
| | * STY: Fix indentation to follow PEP8Charles Harris2016-10-221-2/+2
| | |
| | * commit BLD: AIX uses the flag _LARGE_FILES to ensure proper prototype ↵Michael Felt2016-10-211-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | declarations The problem this fix resolves is to ensure that 32-bit and 64-bit functions (e.g., fclear() and fclear64()) to access/manipulate "large files" are defined properly - much as GNU and other platforms use one or more of the defines _FILE_OFFSET_BITS, _LARGEFILE_SOURCE, and _LARGEFILE64_SOURCE. Without this fix the numpy code only defines flags that are not recognized in the AIX environment and have no effect in anyway. The fix applies the AIX convention and does not "export" any of the flags currently exported. For all other platforms the current flags: _FILE_OFFSET_BITS, _LARGEFILE_SOURCE, and _LARGEFILE64_SOURCE are "exported". This fix should not have any impact or side-effect based on the version of python used. History: Starting around 1997 AIX started supporting so-called "large files", i.e., length > signed 32-bit. In the period 1997-1998 the flag _LARGE_FILES was established to simplify porting 32-bit applications to 64-bit. The convention is to define _LARGE_FILES before including any "system include files" either as an argument to ${CC} (e.g., in ${CFLAGS} or as the first #define in every source file. This is to ensure that that no relevant function calls would be redefined later in the build process.
| * | DOC: 'highest' is exclusive for randint()Ben North2016-10-201-2/+2
| |/
| * MAINT: Remove duplicate randint helpers code.gfyoung2016-09-231-277/+0
| | | | | | | | | | Continuation of gh-8071 by removing the duplicate randint Cython code that is not generated via Tempita.
| * MAINT: Add Tempita to randint helpersgfyoung2016-09-202-0/+78
| | | | | | | | | | | | Refactors the randint helpers to use a Tempita template. This will reduce technical debt in the long run.
| * DOC: change version references from x.y to x.y.zPierre de Buyl2016-09-071-1/+1
| |
| * DOC: change Numpy to NumPy in dosctrings and commentsPierre de Buyl2016-09-061-1/+1
| | | | | | | | The strings in error messages were left untouched
| * TST: Use new warnings context manager in all testsSebastian Berg2016-09-021-11/+15
| | | | | | | | | | | | | | | | In some places, just remove aparently unnecessary filters. After this, all cases of ignore filters should be removed from the tests, making testing (even multiple runs) normally fully predictable.
| * Merge pull request #5822 from anntzer/0-scale-distributionsNathaniel J. Smith2016-06-222-60/+88
| |\ | | | | | | Allow many distributions to have a scale of 0.
| | * Don't allow -0. as distribution shape parameter.Antony Lee2016-06-092-24/+34
| | | | | | | | | | | | At least the gamma generator doesn't support it.
| | * Allow many distributions to have a scale of 0.Antony Lee2016-04-062-60/+78
| | | | | | | | | | | | | | | | | | (in which case a stream of 0's is usually returned (or 1's)). See #5818.
| * | DOC: add reference to poisson rngJulian Taylor2016-06-131-0/+5
| | | | | | | | | | | | [ci skip]
| * | BUG: Fix segfaults in np.random.shuffleSimon Gibbons2016-06-102-1/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | np.random.shuffle will allocate a buffer based on the size of the first element of an array of strings. If the first element is smaller than another in the array this buffer will overflow, causing a segfault when garbage is collected. Additionally if the array contains objects then one would be left in the buffer and have it's refcount erroniously decrimented on function exit, causing that object to be deallocated too early. To fix this we change the buffer to be an array of int8 of the the size of the array's dtype, which sidesteps both issues. Fixes #7710
| * | DOC: fix incorrect Gamma distribution parameterization commentsstevenjkern2016-05-051-2/+2
| | |
| * | MAINT: Ignore DeprecationWarning for random_integers in tests.Charles Harris2016-04-101-9/+13
| | | | | | | | | | | | | | | | | | | | | | | | The warning turned up when the numpy/randome/tests were run using $ python runtests.py -t numpy/random/tests/ It doesn't show when all the tests are run.
| * | MAINT: Always use PyCapsule instead of PyCObject in mtrand.pyx.Charles Harris2016-04-104-98/+11
| |/ | | | | | | | | | | Python 2.7 has a backport of PyCapsule so we no longer need to support PyCObject. This PR makes that change and removes the no longer needed mt_compat.h file.
| * DOC: Clarify the valid range of integers passed to random.seed.Charles Harris2016-02-271-6/+6
| |
| * DOC: Update random.seed in mtrand.pyx.Oren Amsalem2016-02-271-1/+1
| | | | | | | | | | | | | | I know int is between 0 and 4294967295, but I think many people that do not know that will benefit from this comment. [ci skip]
| * Merge pull request #7279 from madphysicist/percentile-testsJulian Taylor2016-02-231-2/+5
| |\ | | | | | | TST: Fixed elements being shuffled
| | * TST: Fixed shuffle axis in tests.Joseph Fox-Rabinovitz2016-02-221-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | Since shuffle only works along the first dimension, it must be done before reshape to get reasonable looking data. Did not affect the current tests. I noticed while working on some scipy code. Also, made a couple of doc changes to np.random.shuffle.
| * | BUG: Remove data race in mtrand: two threads could mutate the state.Devin Jeanpierre2016-02-221-9/+27
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | E.g.: np.random.random_sample() uses the GIL for synchronization np.random.random_sample(1) releases the GIL and uses a separate lock. This means that both can run simultaneously, causing a data race when mutating the random number generator's state, which could lead to buffer overflow (from incrementing state->pos). The fix here is to always use the separate lock, so that exactly one thread at a time is mutating the random number generator's state.
| * BUG: Make randint backwards compatible with pandasgfyoung2016-02-192-9/+24
| | | | | | | | | | | | | | | | | | | | The 'pandas' library expects Python integers to be returned, so this commit changes the API so that the default is 'np.int' which converts to native Python integer types when a singleton is being generated with this function. Closes gh-7284.
| * BUG: Enforce dtype for randint singletonsgfyoung2016-02-162-9/+18
| | | | | | | | Closes gh-7203.
| * DOC: fix a number of reST formatting issues in docstrings.Ralf Gommers2016-02-131-3/+5
| |
| * Update Wikipedia references for mtrand.pyxArne de Laat2016-02-021-12/+12
| | | | | | | | Specifically the 'Logarithmic distribution' link is fixed. For others the links or article names are updated.
| * DOC: Clarify behavior in np.random.uniformgfyoung2016-01-251-0/+6
| | | | | | | | | | | | | | | | | | | | Although the arguments are specified as 'high' and 'low', it is possible to pass in values for 'low' and 'high' where 'low' >= 'high' and still obtain well-defined behavior. The documentation has been expanded to reflect this fact, with a note to discourage passing in arguments satisfying 'low' > 'high'.
| * BUG: One element array inputs get one element arrays returned in np.randomgfyoung2016-01-242-188/+274
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes bug in np.random methods that would return scalars when passed one-element array inputs. This is because one-element ndarrays can be cast to integers / floats, which is what functions like PyFloat_AsDouble do before converting to the intended data type. This commit changes the check used to determine whether the inputs are purely scalar by converting all inputs to arrays and checking if the resulting shape is an empty tuple (scalar) or not (array). Closes gh-4263.
| * DOC: Clarified output size for broadcastable mtrand.pyx functionsgfyoung2016-01-231-182/+243
| | | | | | | | | | | | | | Clarified the output size depending on whether scalar or non-scalar inputs are passed to functions in mtrand.pyx that can broadcast their arguments.
| * TST: Added broadcasting tests in test_random.pygfyoung2016-01-232-87/+644
| | | | | | | | | | | | Added a whole new suite of tests to ensure that functions in mtrand.pyx which are broadcastable actually broadcast their arguments properly.
| * MAINT: Simplified mtrand.pyx helpersgfyoung2016-01-201-104/+74
| | | | | | | | | | | | | | Refactored methods that broadcast arguments together by finding additional common ground between code in the if...else branches that involved a size parameter being passed in.
| * Revert to non-generative test.Antony Lee2016-01-161-5/+4
| |
| * Top shuffle speed for machine-sized ints/floats.Antony Lee2016-01-161-8/+18
| | | | | | | | | | | | Apparently gcc only specializes one branch (the last one) so I went for another 33% performance increase (matching #6776) in what's likely the most common use case.
| * MAINT: memcpy-based ~4x faster, typed shuffle.Antony Lee2016-01-162-40/+56
| | | | | | | | | | | | | | | | | | | | | | | | Only for 1d-ndarrays exactly, as subtypes (e.g. masked arrays) may not allow direct shuffle of the underlying buffer (in fact, the old implementation destroyed the underlying values of masked arrays while shuffling). Also handles struct-containing-object 1d ndarrays properly. See #6776 for an earlier, less general (but even faster: ~6x) improvement attempt, #5514 for the original issue.
View Lorry Controller Status