Frequently Asked Questions¶
What does DIRTY stand for?¶
DIRTY stands for DustI Radiative Transfer, Yeah!. The name was hatched at Chimes, a pub in Baton Rouge, Louisiana.
What is DIRTY?¶
DIRTY is a Monte Carlo dust radiative transfer/emission code that computes the radiative transfer and dust emission from arbitrary distributions of dust illuminated by arbitrary distributions of sources (usually stars).
Who wrote/writes DIRTY?¶
Mainly Karl Gordon (radiative transfer, optical dust emission, I/O) and Karl Misselt (dust grain model, thermal/IR dust emission). Additional coding help (fixing the Karl’s errors) has been given by Ka-Hei Law. Many others have helped by using the model and giving feedback.
DIRTY is a computationally intensive code and is written in C++. Speed is very much needed. Most (if not all) similar models are written in a language that can be compiled. Scripting languages like python and IDL are not well suited to such models.
No assumption of support should be made. Support is provide on the whim of the Karl’s. The Karl’s are interested in research using DIRTY and interesting (to them) research can get support.
Where do I find documentation on setting up the DIRTY parameter file?¶
Check out the (not yet complete) documentation at DirtyParameterFile. Feel free to add to the documentation if it is unclear. This would be greatly appreciated.
What do I do when DIRTY crashes/has an error?¶
Open an issue on the GitHub issue tracker with the parameter file and the error output from the DIRTY code (cut and paste from the terminal). Also include the version of the code you are using and any other information that you think might help us debug the problem.