Hi,
It seems like your code is working fine on SymPy's master branch.
Code
from sympy.stats import ContinuousRV, sample
from sympy import sqrt, exp, Symbol, Interval, oo, pi
mean, prec = 1, 4
x = Symbol('x')
pdf = sqrt(prec)/sqrt(2*pi) * exp(-prec*(x-mean)**2/2)
Z = ContinuousRV(x, pdf,
out to be quite useful to them.
> Other fixes/features are also appreciated because of its early stages. :-)
>
> Have an amazing week!
>
> Regards,
>
> --
>
>
>
>
> On Tue, Feb 16, 2021 at 1:52 PM Gagandeep Singh (B17CS021) <
> singh...@iitj.ac.in> wrote:
>
Hi,
Ideas for Probability and Statistics are updated. Please visit,
https://github.com/sympy/sympy/wiki/GSoC-Ideas#probability
Thanks.
On Sat, Feb 13, 2021 at 3:40 AM Psycho-Pirate
wrote:
> Hey Aaron,
> I would like to help clean up the ideas page. Please let me know how you
> want me to
Hi,
You may go through this link,
https://github.com/sympy/sympy/issues?q=is%3Aopen+is%3Aissue+label%3Astats
and previous year's GSoC reports,
https://github.com/sympy/sympy/wiki/GSoC-2020-Report-Smit-Lunagariya:-Improving-and-Extending-stats-module
On Mon, Feb 15, 2021 at 6:07 PM Kunal Singh
g
>> it to `False`. In the next release, it would be by default, `False`. See,
>> https://github.com/sympy/sympy/pull/20120 and hence your code worked on
>> the development version.
>>
>> On Sun, Oct 11, 2020 at 9:09 PM Gagandeep Singh (B17CS021) <
>> sing...@iitj.ac.in
, `False`. See,
https://github.com/sympy/sympy/pull/20120 and hence your code worked on the
development version.
On Sun, Oct 11, 2020 at 9:09 PM Gagandeep Singh (B17CS021) <
singh...@iitj.ac.in> wrote:
> IPython console for SymPy 1.7.dev (Python 3.6.9-64-bit) (ground types:
IPython console for SymPy 1.7.dev (Python 3.6.9-64-bit) (ground types:
python)
These commands were executed:
>>> from __future__ import division
>>> from sympy import *
>>> x, y, z, t = symbols('x y z t')
>>> k, m, n = symbols('k m n', integer=True)
>>> f, g, h = symbols('f g h', cls=Function)
Hi,
I think for creating RVs with custom distributions, one can use,
ContinuousRV, DiscreteRV Or FiniteRV depending on the type of distribution.
You can take a look at
https://docs.sympy.org/latest/modules/stats.html#examples
Note that the PDF/PMF should be a SymPy object.
With Regards,
Hi,
I read the original post and I think the idea of introducing SEPs seems to
be really useful. Since, I am quite involved with `stats` module and was
thinking to add some new features to it to make it more powerful and useful
to the people working in the area of statistics. I wanted to know
Hi,
May be, http://pysb.org/
With Regards,
Gagandeep Singh
Github - https://github.com/czgdp1807
LinkedIn - https://www.linkedin.com/in/czgdp1807
On Sat, 18 Jul, 2020, 5:15 AM Aaron Meurer, wrote:
> I am looking into potentially submitting a proposal for a CZI grant
> for SymPy at some point
Hi,
Is https://github.com/sympy/sympy/issues/5031 related to your work?
With Regards,
Gagandeep Singh
Github - https://github.com/czgdp1807
LinkedIn - https://www.linkedin.com/in/czgdp1807
On Wed, 27 May, 2020, 11:20 AM Jonathan Gutow, wrote:
> Dear SymPy Community,
>
> For use by my students
May be using `as_int` with the second argument in `RisingFactorial` should
solve the problem. Just an idea.
With Regards,
Gagandeep Singh
Github - https://github.com/czgdp1807
LinkedIn - https://www.linkedin.com/in/czgdp1807
On Thu, 7 May, 2020, 2:55 AM Aaron Meurer, wrote:
> Here is the error
t;.
>
> Jason
> moorepants.info
> +01 530-601-9791
>
>
> On Wed, May 6, 2020 at 10:39 AM Gagandeep Singh (B17CS021) <
> singh...@iitj.ac.in> wrote:
>
>> Hi,
>>
>> IMHO, the control systems should go as a separate repository under sympy
>> wit
Hi,
IMHO, the control systems should go as a separate repository under sympy
with the main sympy repository as a dependency.
In fact that should have happened with sympy.stats as well, as no other
module uses features of stats and the case is other way around but that is
a thing for another day.
n.b. https://github.com/sympy/sympy/pull/7555
On Fri, Apr 24, 2020 at 11:13 AM Arpan Chattopadhyay <
f20180...@pilani.bits-pilani.ac.in> wrote:
> Okay. Thank you.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group
Gagandeep Singh (B17CS021) <
singh...@iitj.ac.in> wrote:
> Probably this link, https://www.traviscistatus.com/incidents/rx6fhs3wqcln is
> related to the problem.
>
> On Wed, Apr 1, 2020 at 8:24 PM Chris Smith wrote:
>
>> Does anyone know why travis runs complete b
Probably this link, https://www.traviscistatus.com/incidents/rx6fhs3wqcln is
related to the problem.
On Wed, Apr 1, 2020 at 8:24 PM Chris Smith wrote:
> Does anyone know why travis runs complete but don't update the PR? e.g.
> https://github.com/sympy/sympy/pull/19024
>
> /c
>
> --
> You
> How will you do that? AFAIK, in symbolic computations results are
deterministic and making predictions of deterministic and verifiable
results would be a bit weird IMHO. Though, something like tree-to-tree
translations can be done.
On Sun, Mar 29, 2020 at 8:34 PM Saanidhya Vats
wrote:
> I was
ver, it
>>> could be used by the first to functionalities. For example, to find all
>>> states j that belong to the same class as i, we will have to find walks
>>> from the state i to the state j and from the state j to the state i.
>>>
>>>
>>> Lastly, I’m not suggesting c
Hi,
The drafts of PR policy and Issue policy have been added to sympy wiki,
1. https://github.com/sympy/sympy/wiki/Pull-Request-Policy
2. https://github.com/sympy/sympy/wiki/Issue-Policy
If you have any suggestions to improve them further then please reply to
this thread or just comment at
What about asking applicants to create issues on GitHub to discuss their
ideas.
On Fri, 27 Mar, 2020, 11:47 PM Oscar Benjamin,
wrote:
> I also wonder if the mailing list is the right place for all these
> GSOC discussions anyway. What is normally a low-volume list ramps up
> massively right now
t;
>These functionalities do not have to be a separate Graph module, but
> they can easily be a part of the current stochastic processes.
>
> Thank you very mach for the comments and your suggestions!
> All the best.
>
> Τη Πέμπτη, 26 Μαρτίου 2020 - 9:56:45 π.μ. UTC+2, ο χ
Currently, Markov chains use transition matrix with T[i][j] representing
the probability of the process going to state j from state i. Infact,
that's what we expect from user to give as an important information for
Markov chains on the basis of which computations will be performed. Most of
the
Hi,
I am unable to find out the links to your merged PRs to `sympy` or
`symengine` repositories. Have you provided the code in some other way? If
so, please add them under a separate heading in the first few pages of the
proposal so that it's easy to locate.
Please go through
> to the multivariate_rv function buts that's not the case for other classes.
> Is there a reason for it or it is something that has not yet been
> implemented?
>
> Thank you in advance!
>
> Τη Τρίτη, 17 Μαρτίου 2020 - 8:31:07 π.μ. UTC+2, ο χρήστης Gagandeep Singh
> (B17CS0
Hi Abhay,
For `sympy.stats` module please go through the following links,
1. GSoC, 2020 ideas for Probability/Statistics -
https://github.com/sympy/sympy/wiki/GSoC-2020-Ideas#probability
2. GSoC, 2020 report for Probability/Statistics -
Hi,
As far as I know, the "Probability" project is available for GSoC, 2020.
Please let me know of any questions regarding GSoC projects related to
`stats` module.
Best wishes.
On Tue, Mar 17, 2020 at 1:06 AM Basilis Kalos
wrote:
> Hi all
>
>
> The first project that i’m most interested to
The PR, https://github.com/sympy/sympy/pull/14701 might be of interest. It
implements an algorithm for computing hypergeometric sums.
On Fri, Mar 13, 2020 at 9:32 AM Neeraj Adhikari
wrote:
> I couldn't find any examples in open issues which require the generating
> function algorithm to solve.
Hi Sachin,
Though I am not very familiar with the series module. However, I
would suggest to describe the mathematics in your proposal behind the fix
if there is any.
And what have you thought about the community bonding period?
Regarding the sufficiency of the work, it's very difficult to
Hi Smit,
1. *Community Bonding - *It looks like many distributions are going to be
added in the stats module. I would suggest to reduce the number of new
distributions to at most 5. Instead you can include testing and improving
the joint distributions, multivariate distributions, the current
IMO, anyone can suggest more concretely if you can come up with the list of
issues you want to address with a brief explanation of your approach to fix
them.
You can also refer to previous discussions in the group.
With Regards,
Gagandeep Singh
Github - https://www.github.com/czgdp1807
LinkedIn -
IMO, Oscar is suggesting a nice idea. Using wrappers for the APIs already
existing for plotting just slows down the computation of overall results.
If the SymPy wrappers for plotting module aren't making any difference in
the algorithms for plotting then may be we can remove them though it would
Hi,
I think your idea will be more suitable for a repository like
https://github.com/Emmarex/Mathematical-Handwriting-recognition/blob/master/README.md
You can also take a look at our ideas list
https://github.com/sympy/sympy/wiki/GSoC-2020-Ideas
With Regards,
Gagandeep Singh
Github -
> machine and thinking of including a fix for it in my proposal. But after
> the application period has ended, suppose someone solves that issue during
> April, then including that issue in my proposal would be a waste.
>
>
>
> On Tue, 4 Feb, 2020, 3:47 PM Gagandeep Singh (B17CS02
Hi Sachin,
I think has Oscar has highlighted some very good points about your idea. I
would like to add a few points to it.
Fixing issues in GSoC project is nice though quite unpredictable, for
example an issue in stats module can be linked to probably integrals or
solvers module. However, there
IMO, adding new APIs to sympy which are present in other CAS is fine. In
fact, sometimes various bugs are discovered while adding new APIs and their
testing. For example `Range` now supports symbolic inputs to some extent
which was needed while making extensions to stats module.
Wolfram Alpha
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi, Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Well, a good starting point for the community bonding phase will be to test
the current implementation, especially the query handler of Markov Chain
and see if there is a scope of improvement, and implementing Random Walks.
In fact a rough plan, like division of various ideas across the complete
Hi,
I have observed that some contributors made efforts to add `control` module
to `sympy.physics`. Following are the related PRs,
1. https://github.com/sympy/sympy/pull/17866
2. https://github.com/sympy/sympy/pull/12189
Can we add this as a project for GSoC 2020?
Waiting to hear from the
GSoC project for anyone interested).
> >>
> >> Aaron Meurer
> >>
> >> On Tue, Jan 14, 2020 at 8:45 AM Chris Smith wrote:
> >> >
> >> > I have found that if you use "_" to refer to the last output it
> causes this problem. Fix: reload
u use "_" to refer to the last output it causes
>> this problem. Fix: reload and remember not to do that.
>> >
>> > On Monday, January 13, 2020 at 7:26:27 AM UTC-6, Gagandeep Singh
>> (B17CS021) wrote:
>> >>
>> >> Hi,
>> >&g
Hi,
I am facing some problems on SymPy Live. I tried executing the example
session on live.sympy.org and the following error was thrown,
```
>>> expr = (x + y)**5
Traceback (most recent call last): File "", line 1, in
File
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi, Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi, Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi, Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi, Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi, Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Please select any issue which you think you can solve. AFAIKA, we don't
assign issues.
Thanks for your interest in the project.
With Regards,
Gagandeep Singh
Github - https://www.github.com/czgdp1807
LinkedIn - https://www.linkedin.com/in/czgdp1807
On Wed, 11 Dec, 2019, 12:47 PM Shubham
Hi, Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Hi, Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
list(https://github.com/sympy/sympy/labels/Please%20take%20over) for
Is https://github.com/sympy/sympy/issues/17692 related?
With Regards,
Gagandeep Singh
Github - https://www.github.com/czgdp1807
LinkedIn - https://www.linkedin.com/in/czgdp1807
On Wed, 27 Nov, 2019, 5:48 PM Jaime Resano Aisa,
wrote:
> Hi, I made a commit which modified only a bit the polygon
More details about sponsorships is available at
https://www.outreachy.org/sponsor/
With Regards,
Gagandeep Singh
Github - https://www.github.com/czgdp1807
LinkedIn - https://www.linkedin.com/in/czgdp1807
On Tue, 19 Nov, 2019, 11:48 PM Gagandeep Singh (B17CS021), <
singh...@iitj.ac.in>
Meurer
>>
>> On Tue, Nov 19, 2019 at 10:31 AM Gagandeep Singh (B17CS021)
>> wrote:
>> >
>> >
>> > The eligibility criteria for FOSS communities are given at
>> https://www.outreachy.org/communities/cfp/
>> >
>> > I am unable to u
> time to do the work for it. But if we have enough people who able to
> do it then we should.
>
> Aaron Meurer
>
> On Tue, Nov 19, 2019 at 12:17 AM Gagandeep Singh (B17CS021)
> > wrote:
> >
> > Hi,
> >
> > I was going through some winter of
Hi,
I was going through some winter of code programs and came across Outreachy. The
registration for this year are closed but can we plan our participation next
year if we are eligible for it.
I want to know the views of the community on this.
--
You received this message because you are
Hi,
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
report(
*Hi, *
Please read the contributing guide(
https://github.com/sympy/sympy/wiki/Introduction-to-contributing). In
addition, also take a look at README(
https://github.com/sympy/sympy/blob/master/README.rst). Take a look at this
report(
When I skimmed through the paper, I had the following queries:
1. Is integration really a tree to tree translation? Because, neural
network is predicting the resulting expression tree for the input equation.
However, integration is not a predictive operation. Moreover, how can we
define that
ing and testing).
>
> I am sorry for the delay in responding because of some personal reasons. I
> will try to be quick from here now.
>
> On Monday, September 2, 2019 at 7:04:05 PM UTC+5:30, Gagandeep Singh
> (B17CS021) wrote:
>>
>> Can you please give a rough idea(na
Can you please give a rough idea(name of the topics from mathematics with
one or two line explanation) about the feature(S) you want to add to SymPy?
With Regards,
Gagandeep Singh
Github - https://www.github.com/czgdp1807
LinkedIn - https://www.linkedin.com/in/czgdp1807
On Mon, 2 Sep, 2019, 6:26
I think for website the issue can be raised at,
https://github.com/sympy/sympy.github.com/issues
Is it the case that you are not on github?
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from
Ah! I missed that.
Have you tried a matrix other than identity?
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sympy+unsubscr...@googlegroups.com.
To post to this
I believe the results are looking fine. Can you please let us know what you
actually expected?
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Is https://github.com/sympy/sympy/pull/17097 related to your doubt? If yes,
then I would say wait for this to be merged. Moreover, have you tried,
Eq(Mul(*[eq.lhs for eq in ()]), Mul(*[eq.rhs for eq in
(https://groups.google.com/group/sympy.
To view this discussion on the web visit
So you want to multiply the two equations?
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sympy+unsubscr...@googlegroups.com.
To post to this group, send email to
would not be necessary as a recursive evaluation is
> literally a copy of the original expression and so could be checked for
> upon execution of the doit at which point the original expression should be
> returned.
>
> On Monday, July 8, 2019 at 11:03:15 AM UTC-3, Gagandeep Sing
I personally believe that all doits should be called with one outer doit. May
be this can be efficiently implemented with a stack. Let's see what others have
to say.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and
I support `List` because it's intuitive to me have an analogous symbolic
unevaluated form of `list`. There are similar containers like `Dict` similar
`dict`. This argument is based on intuition. The point raised by Francesco is
also valid and should be taken into consideration.
One solution
80 matches
Mail list logo
