The main class would be
class IntegralTranforms(Function)
def generaltransform(parameters would be two functions)
//algo for computing wrt to the input kernel
intergrate(f(x)*K(a,x))
if (kernel = Fourier)
call Fourier Transform
and similarly for other kernels.
def prop(input : kernel function)
check (Fourier or not)
check (Millin or not)
check (symmetric)
check asymmetic)
Similarly other properties.
I know it is vague and I am still working on it and this is an idea of
making it general.I hope it was clear.Thanks.
On Wed, Mar 27, 2013 at 5:06 AM, Aaron Meurer <asmeu...@gmail.com> wrote:
> I'm still not clear what exact things this module would compute. Can you
> give some example pseudocode of what the final module might look like?
>
> Aaron Meurer
>
> On Mar 26, 2013, at 4:22 PM, Amit Jamadagni <bitsjamada...@gmail.com>
> wrote:
>
> As per my understanding goes we have the cases where the kernel is
> specific to certain transforms.
> So here the basic math behind the theory is as follows :
>
> I[f(a)] = integral(f(x).k(a,x)) where k(a,x) is the kernel.
>
> So the most general case would be giving a function of two variables and
> the function to be transformed.
>
> So applying conditions on the kernel would end up in different transform
> spaces .
> For example the Fourier Kernel .
>
> It is symmetric kernel the kernels which result in same effect on
> interchanging k(a,x) and I[f(a)]. This is the base but by using this we end
> up with a condition on k(a,x) in mellins space
>
> where in k(a,x) is a fourier kernel if mellins transform of k(s) (where s
> is some variable) is some K(s) then it should satisfy K(s).K(1-s) = 1.
>
> This can be even extended to asymmetric kernels.I am still in the process
> of learning and this is the basic framework I would like to develop upon.
>
> This implementation may not cater to the needs of a GSoC project.So my
> idea was to implement this and improve the spin module as suggested
> earlier.Is this valid and if so as the implementation of both is medium can
> I include both in the proposal so that it would end up being a long
> project.Hope I was clear in delivering my idea across.Thanks.
>
> On Wed, Mar 27, 2013 at 1:41 AM, Aaron Meurer <asmeu...@gmail.com> wrote:
>
>> Can you give a specific example of the sort of thing that the integral
>> transformations code might be able to do?
>>
>> Aaron Meurer
>>
>> On Mon, Mar 25, 2013 at 1:00 AM, Amit Jamadagni <bitsjamada...@gmail.com>
>> wrote:
>> > I would request someone to let me know if the above mentioned cases are
>> > possible.And is there any other requirement for SoC.Thanks.
>> >
>> >
>> > On Sun, Mar 24, 2013 at 4:37 PM, Amit Jamadagni <
>> bitsjamada...@gmail.com>
>> > wrote:
>> >>
>> >> It would be great if someone comments on the other ideas too.Thanks.
>> >>
>> >>
>> >> On Sat, Mar 23, 2013 at 2:26 AM, Amit Jamadagni <
>> bitsjamada...@gmail.com>
>> >> wrote:
>> >>>
>> >>> >The dirac notation stuff is basically done. But the position and
>> >>> >momentum stuff needs a lot of work. There was a bunch of work done
>> >>> >previously and there is an open pull request that has some additional
>> >>> >work. This is an important part of the code base, but just a
>> warning:
>> >>> >it is extremely difficult and you will have to have a very good
>> >>> >understanding of quantum mechanics (probably at the graduate level or
>> >>> >close to it) and know python well. If you are interested in this I
>> >>> >would just start to dig into the code and the open pull request on
>> the
>> >>> >topic and see what you think needs to be done.
>> >>>
>> >>> I would like to add that it might be possible for me to understand
>> >>> (though not completely sure) but if it is a combination of some
>> graduate
>> >>> maths and intermediate physics(in an attempt on reading Sakurai for
>> QM) I
>> >>> can give it a try. If there can be an hint of what level of physics
>> we are
>> >>> dealing with then I can decide so I would like to know a little about
>> >>> this.And I would like to know if there is an implementation of quantum
>> >>> related group theory (SU(2) SU(3) groups).Even though my knowledge
>> about
>> >>> these is pretty elementary I would like to know whether any work is
>> possible
>> >>> in this direction.Thanks.
>> >>>
>> >>> On Sat, Mar 23, 2013 at 2:03 AM, Amit Jamadagni <
>> bitsjamada...@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Thanks, for the ideas on what to implement in the respective
>> sectors.I
>> >>>> would like to know about the implementation of the first topic that I
>> >>>> posted. I guess the patch requirement(pull request numbered 1834 and
>> 1900)
>> >>>> has been done so I would like to know if there is any other
>> requirement to
>> >>>> satisfy to apply for SoC. And yes I would start off as soon as
>> possible and
>> >>>> come up with something by the end this or the beginning of the next
>> month.
>> >>>>
>> >>>>
>> >>>> On Sat, Mar 23, 2013 at 1:39 AM, Brian Granger <elliso...@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> Amit,
>> >>>>>
>> >>>>> Hi, welcome to SymPy!
>> >>>>>
>> >>>>> > 2.Quantum Mechanics module :
>> >>>>> > (i) Adding more features to spin section (Sean Vig has
>> given
>> >>>>> > a lead
>> >>>>> > on this and I am working my way out on what can be done).(Will
>> come
>> >>>>> > out with
>> >>>>> > some ideas by the end of the month)
>> >>>>>
>> >>>>> OK great, Sean is definitely the person to work with on the spin
>> >>>>> stuff. He would know exactly what needs to be done.
>> >>>>>
>> >>>>> > (ii) From the ideas page I find three topics interesting
>> but
>> >>>>> > have
>> >>>>> > to work on this to get the understanding of what is going on
>> >>>>> > Dirac Delta Notation, position and momentum basis (I
>> >>>>> > have tried
>> >>>>> > to understand the code in the pull request) symbolic quantum
>> >>>>> > computing.
>> >>>>>
>> >>>>> The dirac notation stuff is basically done. But the position and
>> >>>>> momentum stuff needs a lot of work. There was a bunch of work done
>> >>>>> previously and there is an open pull request that has some
>> additional
>> >>>>> work. This is an important part of the code base, but just a
>> warning:
>> >>>>> it is extremely difficult and you will have to have a very good
>> >>>>> understanding of quantum mechanics (probably at the graduate level
>> or
>> >>>>> close to it) and know python well. If you are interested in this I
>> >>>>> would just start to dig into the code and the open pull request on
>> the
>> >>>>> topic and see what you think needs to be done.
>> >>>>>
>> >>>>> > Even the tensor module sounds pretty interesting but my
>> understanding
>> >>>>> > would
>> >>>>> > be not be that mathematical as I have just used them in physics (I
>> >>>>> > can work
>> >>>>> > upon on it).
>> >>>>> >
>> >>>>> > Coming to the background I have in the subject I have been
>> >>>>> > doing a
>> >>>>> > course on Integral transforms back at the university and have
>> done a
>> >>>>> > course
>> >>>>> > in quantum computation and have been guided by the professors in
>> the
>> >>>>> > area of
>> >>>>> > Quantum Physics.I know this is very much not in place but I would
>> >>>>> > work on
>> >>>>> > the Quantum Physics part and would move through the code and
>> figure
>> >>>>> > out how
>> >>>>> > it has to be done.I would like to know your view on this topic as
>> >>>>> > there
>> >>>>> > would be medium work done to both the modules (would like to know
>> the
>> >>>>> > take
>> >>>>> > on the first one and is it possible to squeeze a project by
>> >>>>> > contributing
>> >>>>> > evenly to two modules rather than one (since neither both ideas
>> would
>> >>>>> > stand
>> >>>>> > alone as a single long project).Thanks.
>> >>>>>
>> >>>>> There is additional work to be done on the quantum computing stuff:
>> >>>>>
>> >>>>> * Quantum error correction
>> >>>>> * Quantum circuit simplification/optimization
>> >>>>> * Better circuit drawing
>> >>>>> * Use numba/cython/julia to generate fast code for simulating
>> quantum
>> >>>>> circuits.
>> >>>>>
>> >>>>> Hope this gives you an idea of where to start.
>> >>>>>
>> >>>>> Cheers,
>> >>>>>
>> >>>>> Brian
>> >>>>>
>> >>>>> > --
>> >>>>> > 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 sympy@googlegroups.com.
>> >>>>> > Visit this group at http://groups.google.com/group/sympy?hl=en.
>> >>>>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >>>>> >
>> >>>>> >
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Brian E. Granger
>> >>>>> Cal Poly State University, San Luis Obispo
>> >>>>> bgran...@calpoly.edu and elliso...@gmail.com
>> >>>>>
>> >>>>> --
>> >>>>> 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 sympy@googlegroups.com.
>> >>>>> Visit this group at http://groups.google.com/group/sympy?hl=en.
>> >>>>> For more options, visit https://groups.google.com/groups/opt_out.
>> >>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>> > --
>> > 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 sympy@googlegroups.com.
>> > Visit this group at http://groups.google.com/group/sympy?hl=en-US.
>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>>
>> --
>> 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 sympy@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sympy?hl=en-US.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
> --
> 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 sympy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sympy?hl=en-US.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
> --
> 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 sympy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sympy?hl=en-US.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
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 sympy@googlegroups.com.
Visit this group at http://groups.google.com/group/sympy?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
