^
@ads $NEMO/man/man1/*.1
@ads 2005A&A...433...57T
This reference should then be resolvable via the ADS on:
https://ui.adsabs.harvard.edu/abs/2005A&A...433...57T
The idea is that (apart from using grep(1) ) we will have tools that extract these doxygen-like tags and summarize them. Currently the man page entries will have to manually followed up in the usual "FILES" section of the man page to find the source code from the man page. In the case of CGS, this would be in $NEMO/usr/trenti/CGS/
Related to this is how to link software by its name, as suggested in the AASTeX guide for publishing in AAS journals:
\software{Astropy \citep{astropy:2013, astropy:218}}
The name of a code is not always uniquely determined, but a growing list is available on https://github.com/teuben/ascl-tools/blob/master/asclKeywords.txt
An alternative could be a @doi, which for the CGS would be: 10.1051/0004-6361:20041705
During a manual update, the compiled version of all codes with papers
will be on https://teuben.github.io/nemo/man_html/bibcode.html
In amuse each contributed code as the metadata containing a reference to the original author.
In astropy the astropy.__citation__ returns a string
containing the bibtex entry
https://teuben.github.io/nemo/man_html/bibcode.html - generated by NEMO ASCL: https://ascl.net Papers with Code: https://paperswithcode.com/ - see also https://blog.arxiv.org/2020/12/10/instant-access-to-code-for-any-arxiv-paper/
10-apr-2021 written PJT 15-jan-2023 added URL PJT