The editors of the ASCL actively seek codes used in astrophysics research for inclusion in the ASCL. Have a code that should be included? Please post the following information below or send it to the editor:
- Code name
- Description of the code
- Names of the code author(s)
- URL from which the code can be downloaded
Note: ASCL can house an archive file of a code if no download website exists - Link to a research paper for which the code was used
Code does not have to be in the public domain for inclusion. The ASCL includes codes with any licensing scheme, ranging from public domain to any open source (e.g., BSD, GPL) to copyrighted codes.
Thank you!
Name of the code: Diffusion Subroutine
Author: Anne Thoul
Description: Diffusion.f is an exportable subroutine to calculate the diffusion of elements in stars. The routine solves exactly the Burgers equations and can include any number of elements as variables. The code has been used successfully by a number of different groups; applications include diffusion in the sun and diffusion in globular cluster stars. There are many other possible applications to main sequence and to evolved stars. The use of the subroutine is explained in the README file. For additional information, please contact Dr. A. Thoul, anne.thoul@ulg.ac.be.
The routine is based on the calculations developed in the following paper:
Thoul, A. A., Bahcall, J. N., and Loeb, A. 1994, Ap.J. 421, 828.
To access the code from the web page, follow the link “solar neutrinos”, “software and data”.
Thanks very much! I will email you when it’s been added to the ASCL.
Hellow! Some months ago I posted a message about my programs, but seems they were not added to ascl. I will post them again here with more complete data.
My programs (Tomás Alonso Albi) are a set of tools in Java for any operating system based on a library called JPARSEC. Download page is http://conga.oan.es/~alonso/doku.php?id=jparsec. A manager program (very easy/quick to install with the provided instructions) allows to install the tools that depends on this core. Main tools for research are SEDFit, DataCube, and 30mExplorer, and a brief description is given on that page. Source code is completely free under GPL license, and the documentation and code quality is well above the average in any code usually developed and released by scientists. In addition, in http://conga.oan.es/~alonso/doku.php?id=data it is possible to download observational data and input files for the software tools for all sources I’ve worked on, so any result in my publications can easily be reproduced.
Some papers that use these tools:
SEDFit:
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2008ApJ…680.1289A&db_key=AST&link_type=ABSTRACT&high=4e09b3300608118
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2009A%26A…497..117A&db_key=AST&link_type=ABSTRACT&high=4e09b3300608118
DataCube
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2006ApJ…649L.119F&db_key=AST&link_type=ABSTRACT&high=4e09b3300608118
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2010A%26A…518A..52A&db_key=AST&link_type=ABSTRACT&high=4e09b3300608118
30mExplorer
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2012A%26A…543A..27G&db_key=AST&link_type=ABSTRACT&high=4e09b3300608118
A large program work with the IRAM 30m telescope is currently undertaken using this tool
Thanks very much! We’ll take a look at these.
Thank you for your effort, may you are listened.
I would like to add a suggestion: I think it would be nice to have the language in which it is written. A code is even more interesting if I can program in that language, or if I have the required software (as, for example, happens with MATLAB code).
David, thanks for your kind words and suggestion!
We do sometimes list the language within the entry, but in general, I think that information is better kept on the code’s website, as codes are sometimes rewritten in a different language. The metadata on the ASCL site is deliberately light to reduce the data curation effort needed, as the ASCL is an unfunded, volunteer effort. The way I have put it before is more codes lightly described beats fewer codes more robustly described.
If there’s “py” in a code’s title, however, the chances are excellent the code is written in Python!