[{"_1":2,"_165":-5,"_166":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_140":141},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_131":-5,"_132":11,"_133":17,"_134":11,"_135":-5,"_136":11,"_137":-5,"_138":139},"canonicalUrl","https://hub.docker.com/r/devries/infall/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","devries","reponame","infall","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-06-21T14:17:13.487256Z","description","Infall Models from De Vries & Myers (2005). ","is_private","last_updated","2020-10-28T17:34:25.303227Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",1000,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Analytic Infall Models\nHere is the software for the analytic infall models presented in [De Vries & Myers (2005)](http://adsabs.harvard.edu/abs/2005ApJ...620..800D). This software now allows you to run the HILL5 model on all the spectra in a FITS cube. It also checks to see if each line profile can be better fit by a thin, symmetric line and provides the best fit. Feel free to use this software to analyze the asymmetric line profiles in your maps.\n\n## Using the Container\nFirst install docker, then you can get the container, which contains the compiled code and all the required libraries to use the code, by running the command:\n```\ndocker pull devries/infall:1.5\n```\n\n## Execution\nTo execute the code in this container I recommend changing into the directory in which your data is stored and running the command:\n```\ndocker run --rm -ti --user $(id -u):$(id -g) -v $PWD:/data devries/infall:1.5 bash\n```\n\nYou will then be presented a prompt within the container's ubuntu environment. Change into the `/data` directory by typing `cd /data`. You can now use the executables (`hill5_hybrid`, `hill5map`, etc...) on your data.\n\nAlthough all the models from the paper are included in this distribution, we conclude that the `HILL5` model is most accurate for estimating infall speeds. You can fit individual spectra represented as a multicolumn table, where the first column is the velocity in km/s and the second column is the brightness temperature in Kelvins. You can include comment lines that start with a `#` character. The program which fits this performs a fit to this file is `hill5_hybrid`. The more interesting program is `hill5map` which will fit all the spectra in a 3-D FITS cube.\n\n### hill5map\nThis program attempts to fit both an infall model spectrum and a symmetric thin line model to each spectrum in a FITS cube. The program retains the best fit and produces several output FITS cubes and images with fit parameters. The `HILL5` model proved to be the most accurate model discussed in [De Vries & Myers (2005)](http://adsabs.harvard.edu/abs/2005ApJ...620..800D). For each spectrum, should there be an asymmetric line profile, a model spectrum is produced, the reduced chi-squared between the observed and modeled spectrum is calculated, and the 5 parameters of the `HILL5` model are tabulated and placed in separate FITS images. This parameters are sigma, LSR velocity, line center optical depth, infall velocity, and peak excitation temperature. For more information on each parameter and the equations involved please see the paper. Should a symmetric, optically thin line be the best fit, the infall velocity is set to 0, the excitation temperature is set to a specified constant, and the line center optical depth, LSR velocity, and sigma are fit to the observed line profile.\n\nIn order to use `hill5map` you must have a 3-D FITS file. The first two dimensions should be spatial dimensions and the third dimension should be the spectral dimension. The spectral dimension should have units of velocity in m/s. The FITS map units should be brightness temperature in Kelvins. A couple of notes: GILDAS routinely creates 4-D FITS cubes with one blank dimension. If you contact me I can provide a script which removes this additional dimension. Some observatories use the IRAF convention of using the first dimension as the spectral dimension, and the next two as spatial dimensions. I also have a script, designed for FCRAO data, which rotates the cube to make the third dimension the spectral one. \n\nOnce you have a cube which `hill5map` will understand, you will find that `hill5map` has a bewildering number of command line options:\n```\nUsage: hill5map \n```\nI will take you through all of these options, with recommendations for each option.\n\n * `infile`: The input FITS file with the spectra you would like to fit.\n * `frequency`: The line frequency in Hz! If you select 0 here, you will be using the low frequency approximation (Rayleigh-Jeans approximation for brightness temperature).\n * `thin_tex`: This is the excitation temperature you choose for thin lines in Kelvins. You must specify an excitation temperature and the program will fit for the optical depth. Only the combination of excitation temperature and optical depth is well determined on an optically thin line, but not both.\n * `vmin`, `vmax`: The velocity range to fit on each spectrum. This should include the entire line and a little bit of baseline. The fewer channels it is, and the more well bracketed the line is, the faster it will fit.\n * `popingen`: This is a parameter used by the differential evolution fitting algorithm. It defines the number of independent random solutions in each fitting generation. The higher it is, the more likely you are not to end up in a local minimum and find the global minimum. I recommend choosing an integer between 200 and 300 for this parameter.\n * `genpercheck`: This is the number of generations to calculate before checking for the best fit. I recommend choosing 300 for this parameter.\n * `checkperconv`: As the solution converges, the chi-squared parameter will plateau or begin converging very slowly using the differential evolution algorithm. This parameter sets the number of checks that the program should make with little or no change in the chi-squared parameter before switching to the faster Simplex minimization algorithm. I recommend choosing an integer between 3 and 5 here.\n * `x1`, `y1`: These integers specify the x- and y-coordinates of a spectrum on the map with a good infall asymmetry. (The lower left-hand corner of the map is coordinate 1,1). This will be the first spectrum fit by the program and the remaining spectra will be fit using a fast simplex minimization based upon the best-fit parameters from this first spectrum.\n * `minpeak`: Every map usually has some spectra with no signal. This paramter specifies a threshold signal level at which to attempt fitting in Kelvins. If there is at least one channel within the velocity range that has intensity above `minpeak` it will be fit, otherwise the program will assume there is no signal in that spectrum.\n * `outbase`: This program creates several FITS files. `outbase` is a string specifying the prefix to use on all these files.\n\nFor example, let's assume I have a CS 2-1 map of TMC1-1C called `tmc1-1c_cs2-1_cube.fits`. The spectrum at coordinate (15,21) has a good infall asymmetry. The spectral lines are confined to a velocity range of 4.0 to 6.5 km/s, and the noise is restricted to less that 0.4 K in each channel. I could fit this map with the command line\n```\nhill5map tmc1-1c_cs2-1_cube.fits 97.980950e+9 5.0 4.0 6.5 200 300 4 15 21 0.4 tmc1-1c-hill5\n```\nNote that I have picked the CS J=2-1 frequency of 97.980950e+9 Hz, an excitation temperature for thin likes of 5 K, and `popingen`,`genpercheck`, and `checkperconv` values of 200, 300, and 4 respectively. After a short wait, which includes some output to let you know what's happening, the following files will be written out:\n\n * `tmc1-1c-hill5-fits.fits`: A FITS cube of the modeled spectra.\n * `tmc1-1c-hill5-chisq.fits`: A FITS image of the reduced chi-squared fit of each modeled spectrum to each data spectrum.\n * `tmc1-1c-hill5-sigma.fits`: A FITS image of the line width (sigma) in km/s for each model spectrum.\n * `tmc1-1c-hill5-tau.fits`: A FITS image of the optical depth at line center of each modeled spectrum.\n * `tmc1-1c-hill5-tpeak.fits`: A FITS image of the modeled peak excitation temperature along each line of sight. For thin lines this will be 5 K.\n * `tmc1-1c-hill5-vin.fits`: A FITS image of the modeled infall velocity along each line of sight in km/s. For thin lines this will be exactly 0.0 km/s.\n * `tmc1-1c-hill5-vlsr.fits`: A FITS image of the modeled line center velocity along each line of sight in km/s.\n\nNow you can use your favorite FITS tools to analyze the results.\n\nPlease feel free to [contact me](https://github.com/devries) if you have any problems, questions, to report any bugs, or submit any fixes. ","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",381254176,"orgData","recentTags",[87,125],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},"content_type","creator",22572,"full_size",136384054,"id",59679121,"images",[97],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:b4ef9da94c9c21cc76cbe940aba8edb3ca8d7666e10d9c2b0afe5a141a01ea8d","features","","last_pulled","2026-09-21T19:30:06.929382394Z","last_pushed","2020-10-28T17:31:52Z","os","linux","os_features","os_version","size","variant","2020-10-28T17:34:18.040805Z","last_updater","last_updater_username","media_type","latest","repository",7300224,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_88":40,"_89":90,"_91":92,"_93":126,"_95":127,"_46":129,"_115":90,"_116":29,"_117":52,"_53":130,"_119":120,"_121":105,"_122":129,"_123":62,"_124":17},59677853,[128],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"2020-10-28T17:34:24.782618Z","1.5","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":142,"_149":150,"_138":163,"_164":11},{"_36":143,"_38":144,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":145,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":146,"_75":11,"_76":148,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":147},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_151":152,"_153":-5,"_154":-5,"_155":156},"count",2,"next","previous","results",[157,160],{"_88":40,"_89":90,"_91":92,"_93":126,"_95":158,"_46":129,"_115":90,"_116":29,"_117":52,"_53":130,"_119":120,"_121":105,"_122":129,"_123":62,"_124":17},[159],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},{"_88":40,"_89":90,"_91":92,"_93":94,"_95":161,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},[162],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},[],"canDeleteTags","actionData","errors"]

devries/infall

Tags for devries/infall