Published by
EDP Sciences
EDP Sciences Journals List
Free access
Issue A&A
Volume 497, Number 2, April II 2009
Page(s) 399 - 407
Section Interstellar and circumstellar matter
DOI http://dx.doi.org/10.1051/0004-6361/200810987
Published online 18 February 2009

A&A 497, 399-407 (2009)
DOI: 10.1051/0004-6361/200810987

The fidelity of the core mass functions derived from dust column density data

J. Kainulainen1, 2, C. J. Lada3, J. M. Rathborne3, and J. F. Alves4

1  TKK/Metsähovi Radio Observatory, Metsähovintie 114, 02540 Kylmälä, Finland
    e-mail: jouni.kainulainen@helsinki.fi
2  Observatory, PO Box 14, 00014 University of Helsinki, Finland
3  Harvard-Smithsonian Center for Astrophysics, Mail Stop 72, 60 Garden Street, Cambridge, MA 02138, USA
4  Calar Alto Observatory, Centro Astronomico Hispano, Alemán, C/q Jesús Durbán Remón 2-2, 04004 Almeria, Spain

Received 19 September 2008 / Accepted 29 January 2009

Abstract
Aims. We examine the recoverability and completeness limits of the dense core mass functions (CMFs) derived for a molecular cloud using extinction data and a core identification scheme based on two-dimensional thresholding. We study how the selection of core extraction parameters affects the accuracy and completeness limit of the derived CMF and the core masses, and also how accurately the CMF can be derived in varying core crowding conditions.
Methods. We performed simulations where a population of artificial cores was embedded in the variable background extinction field of the Pipe nebula. We extracted the cores from the simulated extinction maps, constructed the CMFs, and compared them to the input CMFs. The simulations were repeated using a variety of extraction parameters and several core populations with differing input mass functions and differing degrees of crowding.
Results. The fidelity of the observed CMF depends on the parameters selected for the core extraction algorithm for our background. More importantly, it depends on how crowded the core population is. We find that the observed CMF recovers the true CMF reliably when the mean separation of cores is larger than the mean diameter of the cores (f>1). If this condition holds, the derived CMF for the Pipe nebula background is accurate and complete above $M \ga 0.8\dots 1.5~M_\odot$, depending on the parameters used for the core extraction. In the simulations, the best fidelity was achieved with the detection threshold of 1 or 2 times the rms-noise of the extinction data, and with the contour level spacings of 3 times the rms-noise. Choosing a higher threshold and wider level spacings increases the limiting mass. The simulations also show that, when $f \ga 1.5$, the masses of individual cores are recovered with a typical uncertainty of $25\dots 30$%. When $f\approx 1$, the uncertainty is ~60%. In very crowded cases where f< 1 the core identification algorithm is unable to recover the masses of the cores adequately, and the derived CMF is unlikely to represent the underlying CMF. For the cores of the Pipe nebula $f \approx 2.0$ thereby justifying the use of the method in that region.


Key words: dust, extinction -- ISM: clouds -- ISM: structure -- stars: formation -- stars: luminosity function, mass function



© ESO 2009

What is OpenURL?

The OpenURL standard is a protocol for transmission of metadata describing the resource that you wish to access. An OpenURL link contains article metadata and directs it to the OpenURL server of your choice. The OpenURL server can provide access to the resource and also offer complementary services (specific search engine, export of references...). The OpenURL link can be generated by different means.
  • If your librarian has set up your subscription with an OpenURL resolver, OpenURL links appear automatically on the abstract pages.
  • You can define your own OpenURL resolver with your EDPS Account. In this case your choice will be given priority over that of your library.
  • You can use an add-on for your browser (Firefox or I.E.) to display OpenURL links on a page (see http://www.openly.com/openurlref/). You should disable this module if you wish to use the OpenURL server that you or your library have defined.