<div dir="ltr">Dear Tom and Adam, <div><br></div><div>Those were convincing replies. I stand corrected. I learned some things from your reply, however, as I need to check (again) flux conservation in the Scipy routine I'm using. I checked a long time ago, but things get 'improved' sometimes the wrong way. I am thinking of getting on the dev list just for the reason of knowing issues like this (though I see coding more as a thing that comes with getting the science done than a thing in itself.) I kind of felt bad for Guang Yang, who offered a piece of code he wrote, and would not like to see him driven into using IDL. Some 25 years ago I thought IDL was great, but with the commercialisation came problems and I think one is better off with open source.</div>
<div><br></div><div>Another issue altogether is that it would be good to have the endorsement of the IAU. At the moment the IAU is renewing itself, and I think the union would benefit from having members involved who are both astronomer/astrophysicist and software developer. I think that either of you would benefit the community. Why do this? The IAU needs to go with the times. Astropy is in much the same position for astronomy as FITS was in the early 1990-ies. I think it gives visibility, focus, and legitimises asking for support. At the moment the astronomical software is part of Commission 5 (which is being revamped as everything else in the IAU), and there are several software related things going on in other divisions. </div>
<div><br></div><div>Cheers, </div><div><br></div><div> Paul</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 3, 2014 at 8:18 AM, Adam Ginsburg <span dir="ltr"><<a href="mailto:adam.g.ginsburg@gmail.com" target="_blank">adam.g.ginsburg@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree with Tom's points, but I'd also like to clarify that the<br>
variety of replies were not all to the same question.<br>
<br>
The scipy.map_coordinates+astropy.wcs, pyAST, and montage utilities<br>
that I, Ray, and Sophie mentioned solve the problem of image<br>
regridding and reprojection, which as Tom points out belongs in<br>
astropy-core eventually.<br>
<br>
The montage approach uses a wrapper to an underlying C program called<br>
montage that needs to be installed independently. The scipy approach<br>
is more purely python, but it requires interpolation and is not flux<br>
conserving (montage is). The pyAST approach wraps another underlying<br>
C library and implements its own resampling that can be flux<br>
conserving depending on certain flags chosen (but Dave Berry, correct<br>
me if I've gotten something wrong here):<br>
<a href="http://dsberry.github.io/starlink/node1.html#Resample" target="_blank">http://dsberry.github.io/starlink/node1.html#Resample</a><br>
<a href="http://www.starlink.rl.ac.uk/docs/sun210.htx/node371.html" target="_blank">http://www.starlink.rl.ac.uk/docs/sun210.htx/node371.html</a><br>
These routines could probably live in something called<br>
astropy.reprojection or something similar.<br>
<br>
<br>
<br>
The second class of problems addressed is image registration, which I<br>
think is being treated in ccdproc, SRPAstro, and the methods that Ray<br>
mentioned. I think these are each niche codes with a different role;<br>
image registration based on star matching is very different from that<br>
based on FFTs and extended emission matching. For a summary of the<br>
codes available for extended emission registration, have a look at<br>
<a href="http://image-registration.readthedocs.org/en/latest/#programs-implementing-these-methods-in-various-languages" target="_blank">http://image-registration.readthedocs.org/en/latest/#programs-implementing-these-methods-in-various-languages</a>.<br>
<br>
I hope this is useful clarification, but please correct me if I<br>
misrepresented anyone's code here.<br>
<div><div class="h5"><br>
On Thu, Jul 3, 2014 at 8:10 AM, Thomas Robitaille<br>
<<a href="mailto:thomas.robitaille@gmail.com">thomas.robitaille@gmail.com</a>> wrote:<br>
> Paul Kuin wrote:<br>
>> Reading all this, I think that part of the success of the IDL Astro<br>
>> library is due to having one head, Wayne Landsman, put it all together.<br>
>> This reads like a conversation on the tower of Babel. Everyone their own<br>
>> method. Someone should take the time to check and compare all the<br>
>> different implementations. Some funding for such work would be very<br>
>> useful and save on duplication. I think this is a task that the IAU<br>
>> could(should?) be involved in.<br>
><br>
> Reducing duplication is precisely the goal of the Astropy project - in<br>
> fact, we have a rule that 'affiliated' packages should not duplicate<br>
> functionality from the core, and also avoid duplication amongst one<br>
> another. See the original vision document:<br>
><br>
> <a href="http://docs.astropy.org/en/stable/development/vision.html" target="_blank">http://docs.astropy.org/en/stable/development/vision.html</a><br>
><br>
> If you are interested in getting involved, you can join the astropy-dev<br>
> mailing list. As part of the Astropy project, there have already been a<br>
> number of successes in merging existing packages to provide a core<br>
> implementation (for example the cosmology routines).<br>
><br>
> On the more specific topic of re-projection - this is clearly a highly<br>
> requested feature, and I think it should be targeted as something that<br>
> should have an implementation in the core astropy package that then gets<br>
> used by all other packages.<br>
><br>
> As a side note, the fact there was more than one reply to the original<br>
> question is a testimony to the strength of the development community in<br>
> Python - people are clearly not just waiting for one person to just<br>
> write it all. Yes, we need to all make an effort to not duplicate things<br>
> needlessly, but on the other hand, having two different ways of<br>
> approaching the same problem is not always bad.<br>
><br>
> Cheers,<br>
> Tom<br>
><br>
>> Paul<br>
>><br>
>><br>
>> On Wed, Jul 2, 2014 at 6:15 AM, Guang Yang <<a href="mailto:yg1991@mail.ustc.edu.cn">yg1991@mail.ustc.edu.cn</a><br>
>> <mailto:<a href="mailto:yg1991@mail.ustc.edu.cn">yg1991@mail.ustc.edu.cn</a>>> wrote:<br>
>><br>
>> Thank all of you for giving those advices. I think I won't bother to<br>
>> switch between python and IDL in my next project. ^^<br>
>><br>
>> Best wishes,<br>
>> Guang<br>
>><br>
>><br>
>> -----Original email-----<br>
>> *From:* "Sofia Lianou" <<a href="mailto:slianou@uwo.ca">slianou@uwo.ca</a> <mailto:<a href="mailto:slianou@uwo.ca">slianou@uwo.ca</a>>><br>
>> *Sent Time:* Jul 2, 2014 5:14:53 AM<br>
>> *To:* "Astronomical Python mailing list" <<a href="mailto:astropy@scipy.org">astropy@scipy.org</a><br>
>> <mailto:<a href="mailto:astropy@scipy.org">astropy@scipy.org</a>>>, "Adam Ginsburg"<br>
>> <<a href="mailto:adam.g.ginsburg@gmail.com">adam.g.ginsburg@gmail.com</a> <mailto:<a href="mailto:adam.g.ginsburg@gmail.com">adam.g.ginsburg@gmail.com</a>>><br>
>> *Cc:* "Pauline Barmby" <<a href="mailto:pbarmby@uwo.ca">pbarmby@uwo.ca</a> <mailto:<a href="mailto:pbarmby@uwo.ca">pbarmby@uwo.ca</a>>><br>
>><br>
>> *Subject:* Re: [AstroPy] Some Feedbacks about Astropy<br>
>><br>
>> Hello,<br>
>><br>
>> This is something that imagecube is doing, too, and the package<br>
>> is hosted here:<br>
>> <a href="http://sophiathl.github.io/imagecube/" target="_blank">http://sophiathl.github.io/imagecube/</a><br>
>><br>
>> Beta release to follow soon, along with proper documentation.<br>
>><br>
>> Cheers,<br>
>> Sophia, Pauline, and Jeff<br>
>><br>
>> On 07/01/14, *Adam Ginsburg * <<a href="mailto:adam.g.ginsburg@gmail.com">adam.g.ginsburg@gmail.com</a><br>
>> <mailto:<a href="mailto:adam.g.ginsburg@gmail.com">adam.g.ginsburg@gmail.com</a>>> wrote:<br>
>>> > 1. I find no tools to align two images, i.e. to uniform<br>
>>> their astrometry, pixel scale, image size and etc.<br>
>>> <a href="http://hastrom.pro" target="_blank">hastrom.pro</a> <<a href="http://hastrom.pro" target="_blank">http://hastrom.pro</a>><br>
>>> (<a href="http://idlastro.gsfc.nasa.gov/ftp/pro/astrom/hastrom.pro" target="_blank">http://idlastro.gsfc.nasa.gov/ftp/pro/astrom/hastrom.pro</a>) is<br>
>>> a good example to perform such a task.<br>
>>><br>
>>> I've written a tool to do that:<br>
>>> <a href="https://github.com/keflavich/FITS_tools/blob/master/FITS_tools/hcongrid.py" target="_blank">https://github.com/keflavich/FITS_tools/blob/master/FITS_tools/hcongrid.py</a><br>
>>> ...I think it does what hastrom does, not hcongrid, which means I<br>
>>> should change the name.<br>
>>><br>
>>> Otherwise, you can use the montage wrapper:<br>
>>> <a href="http://www.astropy.org/montage-wrapper/" target="_blank">http://www.astropy.org/montage-wrapper/</a><br>
>>><br>
>>><br>
>>> --<br>
>>> Adam Ginsburg<br>
>>> Fellow, European Southern Observatory<br>
>>> <a href="http://www.adamgginsburg.com/" target="_blank">http://www.adamgginsburg.com/</a><br>
>>> _______________________________________________<br>
>>> AstroPy mailing list<br>
>>> <a href="mailto:AstroPy@scipy.org">AstroPy@scipy.org</a> <mailto:<a href="mailto:AstroPy@scipy.org">AstroPy@scipy.org</a>><br>
>>> <a href="http://mail.scipy.org/mailman/listinfo/astropy" target="_blank">http://mail.scipy.org/mailman/listinfo/astropy</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> AstroPy mailing list<br>
>> <a href="mailto:AstroPy@scipy.org">AstroPy@scipy.org</a> <mailto:<a href="mailto:AstroPy@scipy.org">AstroPy@scipy.org</a>><br>
>> <a href="http://mail.scipy.org/mailman/listinfo/astropy" target="_blank">http://mail.scipy.org/mailman/listinfo/astropy</a><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> * * * * * * * * <a href="http://www.mssl.ucl.ac.uk/~npmk/" target="_blank">http://www.mssl.ucl.ac.uk/~npmk/</a> * * * *<br>
>> Dr. N.P.M. Kuin (<a href="mailto:n.kuin@ucl.ac.uk">n.kuin@ucl.ac.uk</a> <mailto:<a href="mailto:n.kuin@ucl.ac.uk">n.kuin@ucl.ac.uk</a>>)<br>
>> phone +44-(0)1483 (prefix) -204927 (work)<br>
>> mobile <a href="tel:%2B44%280%297806985366" value="+447806985366">+44(0)7806985366</a> skype ID: npkuin<br>
>> Mullard Space Science Laboratory – University College London –<br>
>> Holmbury St Mary – Dorking – Surrey RH5 6NT– U.K.<br>
>><br>
>> _______________________________________________<br>
>> AstroPy mailing list<br>
>> <a href="mailto:AstroPy@scipy.org">AstroPy@scipy.org</a><br>
>> <a href="http://mail.scipy.org/mailman/listinfo/astropy" target="_blank">http://mail.scipy.org/mailman/listinfo/astropy</a><br>
> _______________________________________________<br>
> AstroPy mailing list<br>
> <a href="mailto:AstroPy@scipy.org">AstroPy@scipy.org</a><br>
> <a href="http://mail.scipy.org/mailman/listinfo/astropy" target="_blank">http://mail.scipy.org/mailman/listinfo/astropy</a><br>
<br>
<br>
<br>
--<br>
Adam Ginsburg<br>
Fellow, European Southern Observatory<br>
<a href="http://www.adamgginsburg.com/" target="_blank">http://www.adamgginsburg.com/</a><br>
_______________________________________________<br>
AstroPy mailing list<br>
<a href="mailto:AstroPy@scipy.org">AstroPy@scipy.org</a><br>
</div></div><a href="http://mail.scipy.org/mailman/listinfo/astropy" target="_blank">http://mail.scipy.org/mailman/listinfo/astropy</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><br>* * * * * * * * <a href="http://www.mssl.ucl.ac.uk/~npmk/" target="_blank">http://www.mssl.ucl.ac.uk/~npmk/</a> * * * *<br>Dr. N.P.M. Kuin (<a href="mailto:n.kuin@ucl.ac.uk" target="_blank">n.kuin@ucl.ac.uk</a>) <br>
phone +44-(0)1483 (prefix) -204927 (work) <br>mobile +44(0)7806985366 skype ID: npkuin<br>Mullard Space Science Laboratory – University College London –<br>Holmbury St Mary – Dorking – Surrey RH5 6NT– U.K.</div>
</div>