Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to get (and GIVE) career credit for software

How to get (and GIVE) career credit for software

Presented at Python in Astronomy 2018: http://openastronomy.org/pyastro/2018

Arfon Smith

May 02, 2018

More Decks by Arfon Smith

Other Decks in Science


  1. the skills required to be a successful scientific researcher are

    increasingly indistinguishable from the skills required to be successful in industry. Jake VanderPlas
  2. We must find a way to legitimize software as a

    form of scholarship. Phil Bourne, Director for Data Science, NIH
  3. Challenge Technical Cultural How do you cite software? ✔ ❌

    Software Citations aren’t allowed ❌ ✔ software isn’t citable ✔ ❌ Software citations aren’t indexed ✔ ✔ Software isn’t peer reviewed ❌ ✔ Software can’t cite other software ✔ ❌
  4. R > citation(‘ggplot2') To cite ggplot2 in publications, please use:

    H. Wickham. ggplot2: elegant graphics for data analysis. Springer New York, 2009. A BibTeX entry for LaTeX users is @Book{, author = {Hadley Wickham}, title = {ggplot2: elegant graphics for data analysis}, publisher = {Springer New York}, year = {2009}, isbn = {978-0-387-98140-6}, url = {http://had.co.nz/ggplot2/book}, }
  5. Python > import astroML as aml > aml.__citation__ @INPROCEEDINGS{astroML, author={{Vanderplas},

    J.T. and {Connolly}, A.J.and {Ivezi{\'c}}, {\v Z}. and {Gray}, A.}, booktitle={Conference on Intelligent Data Understanding (CIDU)}, title={Introduction to astroML: Machine learning for astrophysics}, month={Oct.}, pages={47 -54}, doi={10.1109/CIDU.2012.6382200}, year={2012} }
  6. AAS Journals welcome papers which describe the design and function

    of software of relevance to research in astronomy and astrophysics. Such papers should contain a description of the software, its novel features and its intended use. Such papers need not include research results produced using the software, although including examples of applications can be helpful. There is no minimum length requirement for software papers. http://journals.aas.org/policy/software.html ” “
  7. Tell me exactly what to do: Publish your code (and

    put a license on it) Make your code ‘citable’ by archiving in Zenodo or figshare Encourage people to cite you Write a short paper in e.g. RNAAS or JOSS Write a full paper for ApJ (or other venue)
  8. (i) In your research group/team (ii) As a reviewer (peer

    review, grant review panels) (iii) As a member of a search committee (iv) On a tenure review committee (v) When influencing policy (group, department, professional society, funding agency)