Dear all,<div><br></div><div>Just want to say this is a terrific idea</div><div>and it will be of great value to people who</div><div>are stuck in IDL, like me :-)</div><div><br></div><div>Thank you</div><div>Guangtun<br><div>
<br><div class="gmail_quote">On Sat, Jan 7, 2012 at 5:59 PM, Taro Sato <span dir="ltr"><<a href="mailto:taro@ap.smu.ca">taro@ap.smu.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi there. I have not been diligently following the astropy discussion<br>
lately, so I may sound totally ignorant but please bear with me.<br>
<br>
I've written a Python wrapper for kcorrect by Michael Blanton, a<br>
popular IDL/C tool for k-correction, photo-z, and all that cool stuff<br>
people love to do with spectral-energy distribution fitting for high-z<br>
galaxies these days. I needed it for research recently and updated<br>
the Python version to work with the most recent version/data available<br>
(@ <a href="http://howdy.physics.nyu.edu/index.php/Kcorrect" target="_blank">http://howdy.physics.nyu.edu/index.php/Kcorrect</a>).<br>
<br>
I just got a permission from Michael to distribute the package<br>
(conditions of use being to cite his tool paper), and was going to<br>
make it available somewhere (likely github) and announce it here.<br>
That handy IDL tool now available on Python, only that you pay $19.99<br>
USD to me upon each instantiation of KCorrect object! (...just<br>
kidding)<br>
<br>
But I actually wondered if this sort of thing can be considered for<br>
inclusion in astropy.<br>
<br>
I had no intention of forking Michael's work, just wrote a<br>
SWIG-extension for the core library and translated just a few of the<br>
most useful IDL routines in (hopefully) Pythonic ways. For inclusion<br>
into astropy, however, I presume that there are some styles,<br>
interfaces and such to follow, which I'm willing to make changes now<br>
but wish to make sure it is going to be worth it, not to mention an<br>
additional permission from the original library writer would be<br>
necessary.<br>
<br>
So my question is, will an independently developed tool like kcorrect<br>
be considered at all for an astropy module eventually? If so, how<br>
should I go about this?<br>
<br>
Thank you for your time.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Taro Sato<br>
Department of Astronomy & Physics<br>
Saint Mary's University email: <a href="mailto:taro@ap.smu.ca">taro@ap.smu.ca</a><br>
Halifax, NS B3H 3C3 phone: <a href="tel:%28902%29420-5018" value="+19024205018">(902)420-5018</a><br>
Canada web: <a href="http://ap.smu.ca/~taro" target="_blank">http://ap.smu.ca/~taro</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>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Guangtun Benjamin Zhu, PhD<br>Postdoc Fellow, Physics and Astronomy Department<br>Johns Hopkins University<br>
</div></div>