COT in Collabora Office: Calculate Cotangents and Triangle Ratios

• Introduced: original Collabora release and launch date are not established by the sources reviewed.
• Availability: documented in Collabora Office 26.04 help, scoped to the desktop-help release.
• Platform scope: support in every online or mobile deployment is not inferred from desktop documentation.
• Checked: October 14, 2026. Function-specific documentation and independent numerical examples; no native Collabora test was performed.

=COT(number)

number is an angle in radians. If A2 contains degrees, use =COT(RADIANS(A2)). RADIANS converts the angle before COT evaluates it. Do not convert an input that is already in radians a second time.

The official reference describes the relationship with TAN. COT is a reciprocal function, not an inverse function that returns an angle. ACOT performs that different inverse-angle operation.

Enter 15, 30, 45, 60, 75 in A2:A6. In B2 enter and fill down:

=COT(RADIANS(A2))

The result is a dimensionless ratio. As an acute angle grows through this particular interval, its cotangent decreases. Do not generalize that trend across every angle without accounting for the function’s periodic branches.

These are rounded display values. Keep the original calculated cell value for later formulas rather than retyping nine displayed decimal places.

=COT(PI()/4)
=COT(RADIANS(45))
=1/TAN(RADIANS(45))

Expected results: 1, 1 and 1, within numerical precision. These controls agree because PI()/4 radians and 45 degrees specify the same angle.

=COT(45) instead supplies 45 radians. A formula can be syntactically valid and still describe the wrong physical angle. Put a unit label above the input column, especially when importing data.

In a right triangle, let the vertical opposite side be 8 units and let the angle above the horizontal be in A2. The horizontal adjacent side is:

=8*COT(RADIANS(A2))

For angles 35, 45 and 60 degrees, expected distances are approximately 11.425184054, 8 and 4.618802154 units.

For this geometric model, restrict angles to the acute interval between 0 and 90 degrees and keep the length positive. Although COT has mathematical values for other angles, a negative signed ratio would not automatically represent an ordinary positive side length in this particular triangle.

Check the 45-degree case first: equal opposite and adjacent sides make the ratio one. This simple control catches many unit and side-label mistakes before a larger table is filled down.

=COT(RADIANS(-45))
=COT(RADIANS(135))
=COT(RADIANS(225))

Expected results: −1, −1 and 1, within numerical precision. Cotangent repeats after 180 degrees, so 45 and 225 degrees share the same ratio.

Consequently, =DEGREES(ACOT(COT(RADIANS(225)))) is expected to return approximately 45, not 225. The forward function discarded information about which repeated branch supplied the angle. Collabora’s ACOT returns its documented principal angle between 0 and PI radians.

Store the original angle separately if the full rotation matters. A ratio alone is insufficient to recover it.

Mathematically, cotangent is undefined at integer multiples of PI radians, where sine is zero. At nearby angles its magnitude can be very large. For example, COT of 10 degrees is approximately 5.671281820, while COT of 5 degrees is approximately 11.430052303.

A floating-point representation of PI is not an exact symbolic multiple of PI. Do not infer that every formula representing a nominal singular angle will display the same error, or that a very large finite output is automatically a valid measurement. The help section reviewed does not supply a complete client-specific error table for these cases.

Use domain rules appropriate to the worksheet, retain unrounded inputs and inspect angles near excluded boundaries. No native singularity or extreme-angle benchmark was performed for this guide.

• Collabora Office 26.04: COT.
• Editorial testing standards.

The official section supplies the product-specific definition and angle-unit guidance where applicable. Worked models, identities and rounded outputs are independently calculated expectations. Native execution and broader client compatibility remain unverified.