{"id":1643,"date":"2015-02-09T12:05:27","date_gmt":"2015-02-09T22:05:27","guid":{"rendered":"http:\/\/www.eaobservatory.org\/jcmt\/?page_id=1643"},"modified":"2022-07-05T11:05:08","modified_gmt":"2022-07-05T21:05:08","slug":"velocity-considerations","status":"publish","type":"page","link":"https:\/\/www.eaobservatory.org\/jcmt\/instrumentation\/heterodyne\/velocity-considerations\/","title":{"rendered":"Velocity Considerations"},"content":{"rendered":"<p>For a typical galactic object, the velocity is assumed to be given with respect to the kinematical local standard of rest (`LSR&#8217;), and to be defined according to the radio astronomy standard. In such cases, these are the system defaults, so if you really want something else, it is worth knowing what we can offer you, and understanding the distinctions.<\/p>\n<h2><b>Velocity reference frame<\/b><\/h2>\n<p>That is, the frame of reference with respect to which your velocities are to be defined. The JCMTOT understands the following velocity reference frames:<\/p>\n<ul>\n<li>LSR &#8212; with respect to the kinematical Local Standard of Rest (and as noted above, the default)<\/li>\n<li>HELIOCENTRIC &#8212; for velocities defined with respect to a frame in which the Sun is at rest; some optical velocities are reduced to this reference frame, particularly those for galaxies<\/li>\n<li>BARYCENTRIC &#8212; with respect to the solar system centre of mass; this is not used at all at the JCMT<\/li>\n<li>GEOCENTRIC &#8212; with respect to the centre of the Earth; this is not used at all at the JCMT<\/li>\n<li>TOPOCENTRIC &#8212; measured in a frame in which the telescope is at rest; at the JCMT this is used for planets and comets, and for observations of the Earth&#8217;s atmosphere<\/li>\n<\/ul>\n<h2><b>The velocity definition<\/b><\/h2>\n<p>This is how the velocity is defined from the resultant wavelength or frequency shifts (most astronomical velocity data is just the doppler shift represented as a velocity &#8212; and that can be done in several ways). In what follows the velocity of the source (in the reference frame of your choice) is given by v, and the remainder of the symbols are pretty self-explanatory. There are three different definitions that the JCMTOT can handle:<\/p>\n<ul>\n<li>RADIO &#8212; This is the default for JCMT observations. In this, the frequency, nu, for a velocity (with respect to the given frame of reference) is given by \u03bd = \u03bd<sub>rest<\/sub>(1 &#8211; v\/c)as is traditional in radio astronomy. Here, \u03bd<sub>rest<\/sub> is the rest frequency, and c the velocity of light.<br \/>\nThis corresponds tov\/c = (\u03bd<sub>rest<\/sub> &#8211; \u03bd)\/\u03bd<sub>rest<\/sub>.<\/li>\n<li>OPTICAL &#8212; The `optical&#8217; definition is more easily related to<br \/>\nredshift z and wavelength \u03bb. Thus the resultant \u03bb = \u03bb<sub>rest<\/sub>(1 + z).<br \/>\nThis then corresponds tov\/c = z = (\u03bb &#8211; \u03bb<sub>rest<\/sub>)\/\u03bb<sub>rest<\/sub>.<\/li>\n<li>RELATIVISTIC &#8212; Relativistic definition. Defined by \u03bd = sqrt((1 &#8211; v\/c)\/(1 + v\/c)).Alternatively, this can be rewritten asv = c[(1-(\u03bd\/\u03bd<sub>rest<\/sub>)<sup>2<\/sup>)\/(1+(\u03bd\/\u03bd<sub>rest<\/sub>)<sup>2<\/sup>)].This is the relativistic doppler shift if you assume that the shift is due only to a velocity along the line of sight in the special relativistic sense. It is not true for partly transversal velocities, cosmological redshifts or other reasons for redshifts such as gravitation. It has been argued that this definition of velocity scale (as computed from redshift data) was invented to further confuse the issue &#8212; one more possible definition. There is no guarantee that it will give a more correct velocity than the other scales.<\/li>\n<\/ul>\n<p>Note that for large velocities is it important to make sure that you are using the right velocity definition. The difference can easily cause your line to fall partly or wholly outside the spectrometer window. For instance the<br \/>\ndifference between the radio and optical definition for a velocity of 10000km\/s is 250MHz. This is half the typical spectrometer bandwidth.<\/p>\n<p>If one is observing highly redshifted objects it is important to know the redshift accurately. Using the redshift definition given above a small uncertainty Delta-z in the redshift translates into a uncertainty \u03b4\u03bd in the redshifted frequency via the relation<\/p>\n<p>\u03b4z = -(z+1)<sup>2<\/sup>\u03b4\u03bd\/\u03bd<sub>rest<\/sub>.<\/p>\n<p>So, for example, if you are using a 1000-MHz spectrometer window, you need to know the frequency to better than, say, 250MHz, which for a redshifted frequency of 350GHz and a redshift of 2.0, means that the maximum tolerable redshift error is <span style=\"text-decoration: underline\">+<\/span>0.0021. In general the redshift needs to be known accurately to at least three decimal places.<\/p>\n<h2>How to convert data between velocity frames<\/h2>\n<p>to convert processed data from the <a href=\"http:\/\/www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca\/en\/jcmt\/\">JCMT Science Archive<\/a>, which is in Barycentric frequency, into radio line-of-sight velocity (<img src=\"https:\/\/www.eaobservatory.org\/cgi-bin\/mathtex.cgi?v_{lsr}\" border=\"0px\" \/>) in LSRK. You can use the following <a href=\"http:\/\/starlink.eao.hawaii.edu\">Starlink<\/a> commands to do this, assuming you have started with a file named \u2018archive_file.fits\u2019. These would be copied into a terminal, after setting up the Starlink software within that terminal. The lines starting with a # symbol are comments.<\/p>\n<pre># Load the convert package to enable conversion from FITS to NDF\r\nconvert\r\n\r\n# Convert your archive file into Starlink Data Format (NDF)\r\nfits2ndf archive_file.fits archive_file.sdf\r\n\r\n# Load the KAPPA package (contains many useful routines)\r\nkappa\r\n\r\n# Set the 3rd axis of the coordinate system to be in units of radio velocity\r\nwcsattrib ndf=archive_file.sdf mode=set name=system\\(3\\) newval=vrad\r\n\r\n# Set the standard of rest to be the LSRK\r\nwcsattrib ndf=archive_file.sdf mode=set name=StdofRest newval=LSRK\r\n\r\n# OPTIONAL: if fits output is required, convert the file back to fits\r\nndf2fits archive_file.sdf archive_file_radiovelocity.fits\r\n<\/pre>\n<p>Sometimes it is also needed to add together spectral data from moving targets (eg comets) onto a \u2018source\u2019 (\u2018cometocentric\u2019) velocity scale: this can be done by doing:<\/p>\n<pre>makecube &lt;rawdatafile00099&gt; system=GAPPT alignsys=TRUE out=out99.sdf\r\nwcsattrib out99.sdf set alignoffset 1\r\nwcsattrib out99.sdf set skyrefis origin\r\nwcsattrib out99.sdf set sourceVRF topocentric\r\nwcsattrib out99.sdf set stdofrest source\r\nwcsattrib out99.sdf set alignstdofrest source\r\nwcsattrib out99.sdf set SourceVel &lt;velocity&gt;\r\n\r\nwcmosaic out*.dat . . .<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>For a typical galactic object, the velocity is assumed to be given with respect to the kinematical local standard of rest (`LSR&#8217;), and to be defined according to the radio astronomy standard. In such cases, these are the system defaults, so if you really want something else, it is worth\u2026 <a class=\"continue-reading-link\" href=\"https:\/\/www.eaobservatory.org\/jcmt\/instrumentation\/heterodyne\/velocity-considerations\/\">Continue reading<\/a><\/p>\n","protected":false},"author":10,"featured_media":0,"parent":162,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages\/1643"}],"collection":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/comments?post=1643"}],"version-history":[{"count":19,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages\/1643\/revisions"}],"predecessor-version":[{"id":12628,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages\/1643\/revisions\/12628"}],"up":[{"embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages\/162"}],"wp:attachment":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/media?parent=1643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}