this is for holding javascript data
Alyssa Goodman deleted file Linking Code.md
over 9 years ago
Commit id: 823397f382c4a7b60c0dbb68d25e71d947216fe5
deletions | additions
diff --git a/Linking Code.md b/Linking Code.md
deleted file mode 100644
index b246f4b..0000000
--- a/Linking Code.md
+++ /dev/null
...
## Code
In the modern practice of astronomy a paper is often linked to a swath of computer code that outputs both the numerical conclusions of the paper (e. g. parameter estimates and errors) and the associated figures. Since reproducibility is a bedrock principle of the scientific method, we believe that easy access to underpinning code is crucial part of future publications.
## Links to Software Programs
By combining tools discussed elsewhere in this document, once can "mint" digital object identifiers that point to a particular version of software, assuming it is stored in an organized repostitory. One example is given here: https://guides.github.com/activities/citable-code/, on a web page that shows how to mint a citable DOI for code using the [GitHub](http://github.com) and [Zenodo] (http://zenodo.org) services together. In a model more directly akin to publishing code in exactly the way one currently publishes a paper, services like the [Astrophysics Source Code Library (ASCL)](ascl.net) allow authors to publish a static version of a program, and to assign that version an identifier. At present, The ASCL is indexed by the SAO/NASA Astrophysics Data System (ADS) and is citable by using the unique ascl ID assigned to each program.
## Executable Figures
iPython Notebooks offer a nice modern example of how published figures can be made "executable." These notebooks act as code that can be annotated and executed on the web, allowing an interested reader to study and even modify a copy of the underpinning code, without contacting the authors or initiating a long investigation. the dust map of Ophiuchus inserted as a figure below (courtestsy of Hope Chen) offers an example of the iPython functionality.
