# Codomain

In mathematics, the **codomain** or **target set** of a function is the set Template:Mvar into which all of the output of the function is constrained to fall. It is the set Template:Mvar in the notation *f*: *X* → *Y*. The codomain is also sometimes referred to as the range but that term is ambiguous as it may also refer to the image.

The codomain is part of a function Template:Mvar if it is defined as described in 1954 by Nicolas Bourbaki,^{[1]} namely a triple (*X*, *Y*, *F*), with Template:Mvar a functional subset^{[2]} of the Cartesian product *X* × *Y* and *X* is the set of first components of the pairs in Template:Mvar (the *domain*). The set Template:Mvar is called the *graph* of the function. The set of all elements of the form *f*(*x*), where Template:Mvar ranges over the elements of the domain Template:Mvar, is called the image of Template:Mvar. In general, the image of a function is a subset of its codomain. Thus, it may not coincide with its codomain. Namely, a function that is not surjective has elements Template:Mvar in its codomain for which the equation *f*(*x*) = *y* does not have a solution.

An alternative definition of *function* by Bourbaki [Bourbaki, *op. cit.*, p. 77], namely as just a functional graph, does not include a codomain and is also widely used.^{[3]} For example in set theory it is desirable to permit the domain of a function to be a proper class Template:Mvar, in which case there is formally no such thing as a triple (*X*, *Y*, *F*). With such a definition functions do not have a codomain, although some authors still use it informally after introducing a function in the form *f*: *X* → *Y*.^{[4]}^{[5]}^{[6]}^{[7]}^{[8]}

## Examples

For a function

defined by

the codomain of Template:Mvar is , but Template:Mvar does not map to any negative number. Thus the image of Template:Mvar is the set ; i.e., the interval Template:Closed-open.

An alternative function Template:Mvar is defined thus:

While Template:Mvar and Template:Mvar map a given Template:Mvar to the same number, they are not, in this view, the same function because they have different codomains. A third function Template:Mvar can be defined to demonstrate why:

The domain of Template:Mvar must be defined to be :

The compositions are denoted

On inspection, *h* ∘ *f* is not useful. It is true, unless defined otherwise, that the image of Template:Mvar is not known; it is only known that it is a subset of . For this reason, it is possible that Template:Mvar, when composed with Template:Mvar, might receive an argument for which no output is defined – negative numbers are not elements of the domain of Template:Mvar, which is the square root function.

Function composition therefore is a useful notion only when the *codomain* of the function on the right side of a composition (not its *image*, which is a consequence of the function and could be unknown at the level of the composition) is the same as the domain of the function on the left side.

The codomain affects whether a function is a surjection, in that the function is surjective if and only if its codomain equals its image. In the example, Template:Mvar is a surjection while Template:Mvar is not. The codomain does not affect whether a function is an injection.

A second example of the difference between codomain and image is demonstrated by the linear transformations between two vector spaces – in particular, all the linear transformations from to itself, which can be represented by the 2×2 matrices with real coefficients. Each matrix represents a map with the domain and codomain . However, the image is uncertain. Some transformations may have image equal to the whole codomain (in this case the matrices with rank 2) but many do not, instead mapping into some smaller subspace (the matrices with rank 1 or 0). Take for example the matrix Template:Mvar given by

which represents a linear transformation that maps the point (*x*, *y*) to (*x*, *x*). The point (2, 3) is not in the image of Template:Mvar, but is still in the codomain since linear transformations from to are of explicit relevance. Just like all 2×2 matrices, Template:Mvar represents a member of that set. Examining the differences between the image and codomain can often be useful for discovering properties of the function in question. For example, it can be concluded that Template:Mvar does not have full rank since its image is smaller than the whole codomain.

## See also

## Notes

- ↑ {{#invoke:citation/CS1|citation |CitationClass=book }}
- ↑ A set of pairs is
*functional*iff no two distinct pairs have the same first component [Bourbaki,*op. cit.*, p. 76] - ↑ Template:Harvnb, [[[:Template:Google books]] pages 10–11]
- ↑ Template:Harvnb, [[[:Template:Google books]] quote 1], [[[:Template:Google books]] quote 2]
- ↑ Template:Harvnb, [[[:Template:Google books]] page 8]
- ↑ Mac Lane, in Template:Harvnb, [[[:Template:Google books]] page 232]
- ↑ Template:Harvnb, [[[:Template:Google books]] page 91]
- ↑ Template:Harvnb, [[[:Template:Google books]] page 89]

## References

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}

- {{#invoke:citation/CS1|citation

|CitationClass=citation }}