[AstroPy] Best practices for Python sample code in journal articles

[Michele Bannister]

Wes Fraser put together a supplemental iPython notebook for our recent photometry-technique paper: http://arxiv.org/abs/1604.00031
https://github.com/fraserw/trippy
https://github.com/fraserw/trippy/blob/master/tutorial/trippytutorial.ipynb

Cheers,

Michele.

------------------------------------------------------
Dr Michele Bannister
Postdoctoral Fellow, Outer Solar System Origins Survey
Dept. of Physics and Astronomy, University of Victoria
Victoria BC, Canada
http://www.astro.uvic.ca/~micheleb/
http://www.ossos-survey.org/

On Apr 28, 2016, at 7:00 AM, Singer, Leo P. (GSFC-661.0)[UNIVERSITIES SPACE RESEARCH ASSOCIATION] <leo.p.singer at nasa.gov<mailto:leo.p.singer at nasa.gov>> wrote:

Hi,

I am working on an ApJ submission that I would like to pair with a supplement paper that contains (among other things) some Astropy-based sample/tutorial Python code to acquaint the reader with an accompanying data release. Are there any established best practices for including Python in journal articles? Should code and output be presented docstring-style or should it look like an IPython session? Does anyone have nice examples of astronomy papers that include supplemental IPython notebooks?

If anyone is interested, this is the article and data release:
https://arxiv.org/abs/1603.07333
http://asd.gsfc.nasa.gov/Leo.Singer/going-the-distance/

Cheers,
Leo


Dr. Leo P. Singer
NASA Postdoctoral Program Fellow
Goddard Space Flight Center
8800 Greenbelt Rd., B34, Room S239
Greenbelt, MD 20771
_______________________________________________
AstroPy mailing list
AstroPy at scipy.org
https://mail.scipy.org/mailman/listinfo/astropy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20160428/0bc3c118/attachment.html>