In the ScientificConstants package, the term ScientificConstants object refers to the objects returned by the Constant command applied to a physical constant or by the Element command applied to a property and an element (or isotope) of the periodic table.

•

There is a subset of commands that accept both physical constants and elements (or isotopes). However, some commands can be used with only physical constants and others with only elements and isotopes. The following sections give brief descriptions of the functionality available for physical constants in the ScientificConstants package. For more information on these commands, see:

To obtain the value of a ScientificConstants object, use the evalf command with a physical constant object.

>

evalf( Constant( c ) );

2.99792458&InvisibleTimes;108

(2)

>

Units:-UsingSystem();

SI

(3)

The preceding physical constant object was constructed without any reference to a system of units. Thus, when evaluated, it returns the physical constant value in the current system of units. For more information about checking the current system of units, see Units[UsingSystem]. To evaluate it in a different system, first change the system of units with Units[UseSystem].

>

Units:-UseSystem( CGS );

>

evalf( Constant( c ) );

2.997924580&InvisibleTimes;1010

(4)

•

To obtain a unit object that contains the units of a ScientificConstants object, use the GetUnit command. For more information about unit objects, see Units[Unit].

>

GetUnit( Constant( c ) );

kyne

(5)

>

Units:-UseSystem( SI );

>

GetUnit( Constant( c ) );

ms

(6)

Again, the preceding physical constant object is constructed without any reference to a system of units. Thus, it returns its units in the current system of units.

•

To construct a physical constant object that always evaluates in a particular system of units, use the 'system' option.

>

Constant( c, system=FPS );

ConstantFPS&ApplyFunction;c

(7)

>

evalf( (7) ), GetUnit( (7) );

9.835710564&InvisibleTimes;108&comma;fts

(8)

Notice that the preceding physical constant object has the system of units in which it evaluates displayed in index notation.

•

By using the 'units' option, the physical constant object is multiplied by the appropriate unit object. This is intended for use in the Standard Units environment.

>

Constant( c, units );

ConstantSI&ApplyFunction;c&InvisibleTimes;ms

(9)

>

evalf( (9) );

2.99792458&InvisibleTimes;108&InvisibleTimes;ms

(10)

>

Constant( c, system=FPS, units );

ConstantFPS&ApplyFunction;c&InvisibleTimes;fts

(11)

If the 'units' option is specified and the 'system' option is not specified, the current system is used.

•

Unlike c, which is exact, most physical constants have an associated uncertainty or error, which is a measure of the precision to which their values have been measured experimentally. For example, the gravitational constant (usually represented by G):

>

GetError( Constant( G ) );

1.0&InvisibleTimes;10-13

(12)

The error returned for a ScientificConstants object is of constant type and in absolute (not relative) form. That is, the magnitude depends on the system of units. For more information about uncertainties, see GetError.

Some physical constants return an error of undefined, which indicates the error is implicit in the figures of the central value.

•

Because the objects in ScientificConstants have central values with associated uncertainties, they are also recognized by the ScientificErrorAnalysis package.

•

To view information for a physical constant in the ScientificConstants package, use the GetConstant command.

Note that a physical constant can be identified by its full name (the first item in the sequence) or symbol. The name can be used in the Constant constructor, but is most useful as a brief description of the constant.

•

To list the physical constants in the ScientificConstants package, use the GetConstants command.

Some physical constants have their values determined to more than 10 significant figures. Hence, access of these values at the default setting of Digits may result in a loss of precision. For more precision, set Digits to a higher value, for example, 15.