[AstroPy] ESA Summer of Code in Space 2013

[Éric Depagne]

Hi all, 

> Along similar lines, Emil and Adam (although I think Adam already
> knows about it), I'd *strongly* encourage you to take a look at the
> astropy modeling framework
> (http://docs.astropy.org/en/latest/modeling/index.html) - this will be
> in the next major release, and I'd hate to see you re-implementing all
> of that in an incompatible way. Or, if you don't like something about
> how that works for your needs, please help us make it better!
And for me, whose talent in coding won't be enough to be of real help in the 
coding, I'd be happy to help otherwise : providing things I'd like to see, 
features that may help (that's the obvious and easy part), but aslo, I'd be 
happy to help test and debug.

Éric.

> 
> 
> On Thu, Jun 20, 2013 at 8:42 AM, Slavin, Jonathan
> 
> <jslavin at cfa.harvard.edu> wrote:
> > Hi Adam,
> > 
> > I have used pyspeckit.  There are parts of it that are very useful, but I
> > found overall that it didn't do what I wanted.  For example, I wanted to
> > give it my spectrum, have it display it, allow me to manually (in the
> > gui) place my guesses for line centers (would probably need guesses for
> > widths as well) and then fit the lines (and continuum) and return the
> > fitted line centers, widths, and amplitudes, etc. along with error
> > estimates.  It's been a while now since I used it, but as I recall,
> > pyspeckit did not do all of those things.  There may have been other
> > reasons as well, but in the end I wrote my own fitting routines to work
> > with the data.  Am I wrong about the capabilities of pyspeckit?
> > 
> > Jon
> > ________________________________________________________
> > Jonathan D. Slavin                 Harvard-Smithsonian CfA
> > jslavin at cfa.harvard.edu       60 Garden Street, MS 83
> > phone: (617) 496-7981       Cambridge, MA 02138-1516
> > fax: (617) 496-7577            USA
> > ________________________________________________________
> > 
> > On Wed, Jun 19, 2013 at 5:21 PM, <astropy-request at scipy.org> wrote:
> >> Date: Wed, 19 Jun 2013 13:32:31 -0700 (PDT)
> >> From: Adam Ginsburg <keflavich at gmail.com>
> >> Subject: Re: [AstroPy] ESA Summer of Code in Space 2013
> >> To: astropy-dev at googlegroups.com
> >> Cc: astropy at scipy.org
> >> Message-ID: <44536fa7-b34e-4f05-941b-2cc05535bcc5 at googlegroups.com>
> >> Content-Type: text/plain; charset="utf-8"
> >> 
> >> 
> >> Emil and Jon - there is a package that fits exactly those requirements,
> >> called pyspeckit:
> >> pyspeckit.bitbucket.org
> >> 
> >> One of my major goals over the next year is to incorporate it into
> >> astropy bit by bit, i.e. make it work with astropy.models,
> >> astropy.units, and specutils.  Only a little progress in that direction
> >> has been made (in part
> >> because my coding efforts have been focused more on astroquery).
> >> 
> >> Emil - there is a scipy-dependent voigt profile implemented in
> >> pyspeckit.
> >> 
> >>  You can check that it agrees with yours:
> >> http://pyspeckit.bitbucket.org/html/sphinx/models.html#pyspeckit.spectru
> >> m.models.inherited_voigtfitter.voigt
> >> 
> >> I'm bringing this up on this particular thread because I had considered
> >> submitting pyspeckit as a SOCIS project, but I think focusing on
> >> specutils instead will be better for the community.  Nonetheless, there
> >> are some specific project ideas in place that may help support the case
> >> for a student working on specutils via SOCIS:
> >> pyspeckit.bitbucket.org/html/sphinx/projects.html
> > 
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
Un clavier azerty en vaut deux
----------------------------------------------------------
Éric Depagne                            eric at depagne.org