dev.ASCL.net

Astrophysics Source Code Library

Making codes discoverable since 1999

Citing ASCL code entries

The ASCL's main goal is transparency of research; one avenue to this is advocating for code citations in papers. Citing codes increases transparency (assuming one can examine the codes), but is also good for code authors, providing a way the value of their work can be demonstrated.

Some codes are described in a paper that can be cited. Those that are, it makes sense to cite that paper, and some code authors offer direction as to how they prefer their codes be cited on their code websites. However, many codes do not have a code paper that describes the code. The ASCL makes codes citable even when they do not have such a paper; most of the citations to ASCL entries I've seen are in the format:

author, year, in Astrophysics Source Code Library, record ascl ID

For example:

Barnes, J. E., 2011, Astrophysics Source Code Library, record ascl:1102.027

It may be helpful to the reader to include the name of the code as well:

    Barnes, J. E., 2011, ZENO, Astrophysics Source Code Library, record ascl:1102.027

The BibTeX ADS provides for the code entry above is:

@MISC{2011ascl.soft02027B,
author = {{Barnes}, J.~E.},
title = "{ZENO: N-body and SPH Simulation Codes}",
howpublished = {Astrophysics Source Code Library},
year = 2011,
month = feb,
archivePrefix = "ascl",
eprint = {1102.027},
adsurl = {http://adsabs.harvard.edu/abs/2011ascl.soft02027B},
adsnote = {Provided by the SAO/NASA Astrophysics Data System}
}

Please use the entire ascl ID (ascl:xxxx.xxx) in the reference, as that enables ADS to pick up the citation.

If you are submitting a paper which uses a new code you have developed to a refereed journal, you can request the code be added to the ASCL and assigned an ascl ID so this unique identifier can be included in your paper by contacting the editors at editor@ascl.net.

Please note: Some BibTeX styles (.bst), especially old ones, don't support the eprint field, which ADS uses when generating the BibTeX for ASCL and arXiv entries. The lack of support for the eprint field results in a citation that formats the ascl ID incorrectly; for ADS to be able to find and count the citation, the ascl ID needs to be formatted just as it appears in the code entry, e.g. ascl:1010.051 for NEMO. The arXiv site has a list of BibTeX styles that have been updated to support the eprint field, and Norman Gray's nice urlbst code can add this functionality to existing .bst files. Many journals have updated their BibTeX style files to provide support for the eprint field; please consider checking to ensure the style files you use are up-to-date. (Updated 09/04/2013; 03/02/2016)
http://dev.ascl.net/wordpress/?page_id=351
dev.ascl.net
crawl=CC-MAIN-2019-47
10338
application/http; msgtype=response
sha1:YPELX2WX5HBGUJ3BM5DMUVP7LIAOX5QR
<urn:uuid:09a393ca-1d43-41d4-850d-02de24e5963e>
2019-11-21T07:51:31Z
141.219.70.80
text/html
sha1:PMBKV2VKL5QCVVHIHA4YFJWD45BDENIK
<urn:uuid:191109fc-c025-4a5e-a908-53b6887f97d6>
http://dev.ascl.net/wordpress/?page_id=351
response
<urn:uuid:45b64699-be3d-4e45-88c7-5034ab3df415>
isPartOf: CC-MAIN-2019-47
publisher: Common Crawl
description: Wide crawl of the web for November 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-211.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/