Contact

IMARGUMENT Function (Calligra Sheets)

Engineering Intermediate Calligra Sheets

Find complex phase angles in radians with Calligra IMARGUMENT, with quadrant examples, degree conversion and zero-input/help corrections.

Verification status: Selected formulas were executed through the Calligra Sheets 25.04.2 calculation engine library. Complex outputs are reported as components, not GUI-cell display. Version 26.08.2 was source-checked only. How formula examples are checked

Quick answer: =IMARGUMENT(COMPLEX(3;4)) gives 0.927295218002 in the tested Calligra calculation engine. The result is numeric.

Availability and version history

  • Introduced: First release not established; the name is present in Calligra 2.4.0 source.
  • Supported in: Calligra Sheets 26.08.2, with no retirement established.
  • Scope: Desktop Sheets with the Engineering module. Examples use English semicolon-separated formulas.
  • Checked: October 14, 2026. Formulas were executed through the official 25.04.2 engine library and checked against source and independent mathematics. This is not GUI-cell or workbook-import evidence; 26.08.2 was source-checked, not executed.

What IMARGUMENT returns

IMARGUMENT returns the phase angle of a complex value a+b·i. For a nonzero value, the angle is determined by both components, like atan2(b,a), rather than by ATAN(b/a) alone. The result is numeric radians; quadrant information is essential when the real component is negative. Function help.

Syntax and arguments

=IMARGUMENT(complexValue)

Exactly one argument is required. Use a native COMPLEX value or a tested complex text representation. The implementation delegates to the standard complex argument operation. A positive real value has angle 0; the tested real value −1 has angle π. Values on a branch boundary can be sensitive to signed zero. Registration and implementation, with versioned help.

Reproducible engine examples

Noninteger results are rounded to twelve decimal places. The formulas construct the input components explicitly, making each case reproducible.

Formula Engine result
=IMARGUMENT(COMPLEX(3;4)) 0.927295218002
=IMARGUMENT(COMPLEX(3;-4)) -0.927295218002
=IMARGUMENT(COMPLEX(-3;4)) 2.214297435588
=IMARGUMENT(COMPLEX(0;4)) 1.570796326795
=IMARGUMENT(COMPLEX(3;0)) 0
=IMARGUMENT(COMPLEX(0;0)) 0
=IMARGUMENT(COMPLEX(-1;-1)) -2.356194490192
=IMARGUMENT(COMPLEX(0.5;0.25)) 0.463647609001

Practical worksheet

With 3 in A2 and 4 in B2, =IMARGUMENT(COMPLEX(A2;B2)) gives about 0.927295218002 radians. The recorded =IMARGUMENT(COMPLEX(3;4))*180/PI() gives about 53.130102354156 degrees. State the unit in the result column; formatting a radian value does not convert it to degrees.

Advanced interpretation and checks

Compare 3+4i with −3+4i. Their magnitudes are both 5, but their phases are about 0.927295218002 and 2.214297435588 radians. The second lies in the upper-left quadrant. A plain ratio b/a loses the information needed to distinguish those directions.

At the origin the phase is mathematically undefined, even though the tested IMARGUMENT(COMPLEX(0;0)) returns 0. Treat that as an implementation result, not an observed direction. In an analysis sheet, test the magnitude against an appropriate model-specific threshold before interpreting the phase.

Input boundaries and cautions

Two versioned-help examples disagree with the inspected implementation and the engine tests: IMARGUMENT("1.2+5i") gives about 1.335251346074, and IMARGUMENT("12") gives 0, rather than the help’s listed 0.6072 and division error. The current function returns a numeric angle despite the help’s string-type label.

Invalid text “abc” and empty text also returned 0 because the shared complex converter substitutes zero on failed parsing. Validate source text separately; an angle of zero cannot distinguish a valid positive real input from those failures. A missing argument returned #VALUE!.

Formula Engine result
=IMARGUMENT("3+4i") 0.927295218002
=IMARGUMENT("3+4j") 0.927295218002
=IMARGUMENT("abc") 0
=IMARGUMENT("") 0
=IMARGUMENT(-1) 3.14159265359
=IMARGUMENT() #VALUE!

Conversion evidence

The complex conversion helper explains the text and Boolean cases above. The inspected Engineering module and complex converter are byte-identical between 25.04.2 and 26.08.2. That source comparison does not establish every locale, import path or extreme-value case.