|
casacore
|
All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Groups Pages
|
casacore
|
defines physical units More...
#include <Unit.h>
Public Member Functions | |
| Unit () | |
| Default empty string constructor. More... | |
| Unit (const Unit &other) | |
| Copy constructor. More... | |
| ~Unit () | |
| Destructor. More... | |
| Unit & | operator= (const Unit &other) |
| Bool | operator== (const Unit &other) const |
| Comparisons. More... | |
| Bool | operator!= (const Unit &other) const |
| Bool | empty () const |
| Fast check for "" units. More... | |
| const UnitVal & | getValue () const |
| Get the unit value. More... | |
| const String & | getName () const |
| Get the unit name. More... | |
| void | setValue (const UnitVal &in) |
| Set the unit value. More... | |
| void | setName (const String &in) |
| Set the unit name. More... | |
| Unit (const std::string &other) | |
| String based constructors. More... | |
| Unit (const Char *other) | |
| Unit (Char other) | |
| Unit (const Char *other, Int len) | |
Private Member Functions | |
| void | check () |
| Check format of unit string. More... | |
Private Attributes | |
| String | uName |
| UnitVal | uVal |
defines physical units
Public interface
Physical units are basically used as quantities (see the Quantum class), i.e. a value and a dimension. The Unit class, or one of its subsidaries, will in general not be called separately. The only reason to make use of these classes is to generate additional 'tagged' units, i.e. units with a special name, e.g. 'beam' for a telescope beam, or 'JY', a non-SI name for Jy.
A Unit is a String, and can be defined as either a Unit or a String everywhere where a Unit is required.
If defined as a Unit, the format of the string will be checked for a legal definition and its value will be stored. If defined as a String, the checking and determination of the value will be done each time the string is encountered when a Unit is expected.
Tip: The use of a separate Unit variable will give a tremendous speed increase, if compared to using the String representation in e;g; Quantity(5,"deg")
Caution: If using an explicit Unit variable (e;g; Unit a("5Bolton/beam")), the check on the legality of the given string, and the conversion to the cached canonical value in the variable 'a', is only done at creation time; This means that if the user changes the value of a unit involved by the putUser() method, the unit using it should be re-created ( a = Unit("5Bolton/beam"););
A unit is a string of one or more fields separated by 'space' or '.' or '*' (FITS option) (to indicate multiply) or '/' (to indicate divide). Multiple separators are acted upon (i.e. m//s == m.s). Separators are acted upon left-to-right (i.e. m/s/A == (m/s)/A; use () to indicate otherwise (e.g. m/(s/A))).
A field is a name, or a unit enclosed in (), optionally followed by an, optionally signed, decimal constant. The decimal constant may be proceeded by '**' or '^' (FITS option)
E.g. m.(m/s)-2 == m-1.s2)
Tip: A 'space' or ';' before an opening '(' can be omitted;
A name can consist of case-sensitive letters, '_', ''', ':', '"' and '0' ('0' not as first character). Digits 1-9 are allowed if preceded with an '_'.
Possible legal names are e.g. Jy, R0, R_1, "_2.
Tip:
' is used for arcmin '' or " for arcsec
Caution: The standard naming conventions for SI units are that they are all in lowercase, unless derived from a person's name, when they start with a capital letter; Notable exceptions are some of the astronomical SI related units (e;g; AU);
A name can be preceded by a (standard) decimal prefix.
A name must be defined in a Unit map before it can be used.
All SI units and some customary units are part of the classes. User defined names can be added by the UnitMap::putUser() function (see the UnitMap class).
Example: km/s/(Mpc.s)2 is identical to km.s-1.Mpc-2.s-2
There are 5 name lists in the UnitMap, which are searched in reverse order:
All known names can be viewed by running the tUnit test program, or using the MapUnit::list() routine. They are also (at least the 1999/09/15 values) available in the Quanta module documentation.
Caution: There is a difference between units without a dimension (non-dimensioned I will call them), and undimensioned units; Non-dimensioned examples are "", "%"; undimensioned examples: "beam", "pixel";
The Unit class is not directly based on the String class, but Strings and Units are interchangeable in all Unit and Quantum related calls. (But notice the earlier note on speed if using explicit Strings often.)
To calculate with Units (or Strings representing units), use the UnitVal class. To use dimensioned values, use the Quantum (cq Quantity) class.
Using Unit i.s.o. String will give an immediate check of the legality of the unit string. In addition the UnitVal class contains a check facility to determine the legality of a unit string:
Make basis for all dimensioned values the SI system of units
| casacore::Unit::Unit | ( | ) |
Default empty string constructor.
| casacore::Unit::Unit | ( | const Unit & | other | ) |
Copy constructor.
| casacore::Unit::Unit | ( | const std::string & | other | ) |
| casacore::Unit::Unit | ( | const Char * | other | ) |
|
explicit |
| casacore::Unit::~Unit | ( | ) |
Destructor.
|
private |
| Bool casacore::Unit::empty | ( | ) | const |
Fast check for "" units.
| const String& casacore::Unit::getName | ( | ) | const |
Get the unit name.
Referenced by casacore::ScalarQuantColumn< Double >::getUnits().
| const UnitVal& casacore::Unit::getValue | ( | ) | const |
Get the unit value.
Comparisons.
Comparisons are done on the basis of the inherent units. I.e. m/s are identical to AU/cy.
| void casacore::Unit::setName | ( | const String & | in | ) |
Set the unit name.
| void casacore::Unit::setValue | ( | const UnitVal & | in | ) |
Set the unit value.
1.8.5