The default values supplied for many SpecFrameSpecFrame attributes will depend on the value of the SpecFrame's SystemSystem attribute. In practice, this means that there is usually little need to specify many of these attributes explicitly unless you have some special requirement. This can be illustrated by using astShowastShow to examine a SpecFrame, as follows:
The output from this might look like the following:
Note that the defaults (indicated by the “#
” comment
character at the start of the line) for attributes such as the TitleTitle,
axis Labels and Unit specifiers are all set to values appropriate
for the particular velocity system that the SpecFrame represents.
These choices would be appropriate for a System value of “Vopt”,
but if a different System value were set, the defaults would be
correspondingly different. For example, by default frequency is measured in
units of GHz, not , so setting “System=freq”
would change the appropriate line above from:
to
Of course, if you do not like any of these defaults, you may always over-ride them by setting explicit attribute values yourself. For instance, you may choose to have your frequency axis expressed in “kHz” rather than “GHz”. To do this simply set the attribute value as follows:
No error will be reported if you accidentally set an inappropriate Unit value (say "J" - Joules)—after all, AST cannot tell what you are about to do, and you may be about to change the System value to “Energy”. However, an error will be reported if you attempt to find a conversion between two SpecFrames (for instance using astConvertastConvert ) if either SpecFrame has a Unit value which is inappropriate for its System value.
SpecFrame attributes, like all other attributes, all have default value. However, be aware that for some attributes these default values can never be more than “a legal numerical value” and have no astronomical significance. For instance, the RefRARefRA and RefDecRefDec attributes (which give the source position) both have a default value of zero. So unless your source happens to be at that point (highly unlikely!) you will need to set new values. Likewise, the RestFreqRestFreq (rest frequency) attribute has an arbitrary default value of 1.0E5 GHz. Some operations are not affected by inappropriate values for these attributes (for instance, converting from frequency to wavelength, changing axis units, etc), but some are. For instance, converting from frequency to velocity requires a correct rest frequency, moving between different standards of rest requires a correct source position. The moral is, always set explicit values for as many attributes as possible.