IMCONJUGATE Function (Gnumeric)
Learn the IMCONJUGATE function in Gnumeric: Returns the complex conjugate of a complex number.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
The complex conjugate of a+bi is a-bi. In practical terms, Gnumeric’s IMCONJUGATE keeps the real coefficient and reverses the sign of the imaginary coefficient. The conjugate of 3+4i is mathematically 3-4i; the conjugate of 3-4j is 3+4j. This is often useful in complex-number multiplication, magnitude checks and engineering calculations [1, IMCONJUGATE].
Version-specific error distinction: The online 1.12 manual describes malformed complex inputs as
#VALUE!. The official 1.12.62 source instead returns#NUM!when parsing a malformed complex string; other unsupported value types can still return#VALUE!. Any#VALUE!expectations below are the manual’s older documented rule, not verified 1.12.62 output. No native error test was performed.
Availability and version history
- Introduced: Documented by 1.12.62; original introduction not established.
- Availability: Supported in Gnumeric 1.12.62, based on the function-specific registration.
- Scope: Desktop; the fn-complex function module must be included and enabled.
- Checked: October 14, 2026. Documentation/source check; no new native test in Gnumeric 1.12.62.
Exact Gnumeric syntax
=IMCONJUGATE(z)
| Argument | Required? | Purpose | Default |
|---|---|---|---|
z |
Yes | A valid complex number, as a recognized complex literal, cell reference or the output of COMPLEX or another complex function. |
None |
There is exactly one documented input. IMCONJUGATE is not the same as negation: -(3+4i)=-3-4i, while the conjugate is 3-4i. Nor does conjugation mean taking an absolute value. Gnumeric’s reference states that an invalid complex input yields #VALUE! and identifies the function as Excel compatible [1].
Try it in a worksheet
Create the following small table:
| Cell | Entry | Role |
|---|---|---|
| A1 | Real coefficient |
Header |
| B1 | Imaginary coefficient |
Header |
| C1 | Complex value |
Header |
| D1 | Conjugate |
Header |
| A2 | 3 |
Real component |
| B2 | 4 |
Imaginary component |
| C2 | =COMPLEX(A2,B2) |
Build 3+4i. |
| D2 | =IMCONJUGATE(C2) |
Build its conjugate. |
| A3 | 3 |
Real component |
| B3 | -4 |
Imaginary component |
| C3 | =COMPLEX(A3,B3,"j") |
Build 3-4j. |
| D3 | =IMCONJUGATE(C3) |
Build its conjugate. |
Mathematically expected D2 = 3-4i, D3 = 3+4j. The exact appearance of the complex string, including whether a suffix is preserved in every code path, must be confirmed in an installed Gnumeric release; this review did not capture native outputs. All argument names and documented invalid-value error come from the Gnumeric 1.12 manual [1].
More expected expressions
| Formula | Independently calculated result | Reason |
|---|---|---|
=IMCONJUGATE("3+4i") |
3-4i |
Reverse the sign of the imaginary coefficient. |
=IMCONJUGATE("3-4j") |
3+4j mathematically |
Alternative suffix; its exact rendered notation needs a native check. |
=IMREAL(IMCONJUGATE("3+4i")) |
3 | The real part is unchanged. |
=IMAGINARY(IMCONJUGATE("3+4i")) |
-4 | The imaginary coefficient changes sign. |
=IMCONJUGATE(IMCONJUGATE("3+4i")) |
3+4i |
Applying conjugation twice returns the starting value. |
=IMCONJUGATE("garbled") |
#VALUE! (documented rule) |
Invalid complex number; do not treat it as zero. |
The last error prediction relies on an explicit manual rule, while all other values are independent mathematical expectations, not executed application output.
Applied scenario: compare complex impedance magnitudes
Suppose an impedance estimate has real component 8 and imaginary component 6. Put 8 in A2, 6 in B2, =COMPLEX(A2,B2,"j") in C2 and =IMCONJUGATE(C2) in D2. The two complex quantities are 8+6j and 8-6j mathematically; both have modulus √(8²+6²)=10. Use =IMABS(C2) and =IMABS(D2) to check that the magnitudes match, even though the imaginary signs differ. This is a mathematical model illustrating complex conjugation; it is not a substitute for circuit-specific physical assumptions.
Advanced: multiply a value by its conjugate
For z=a+bi, the identity z × conjugate(z)=a²+b² yields a nonnegative real number. With z=3+4i, the product is (3+4i)(3-4i)=9+16=25 (because the imaginary cross terms cancel and i²=-1). In a Gnumeric worksheet with A2=3, B2=4:
C2: =COMPLEX(A2,B2)
D2: =IMCONJUGATE(C2)
E2: =IMREAL(IMPRODUCT(C2,D2))
F2: =A2^2+B2^2
G2: =IMABS(C2)^2
Expected E2=F2=G2=25. A useful additional check is =IMAGINARY(IMPRODUCT(C2,D2)), whose mathematically expected value is 0. If real and imaginary parts are mixed up, or if one term’s sign was typed incorrectly, comparing the multiple independently derived values helps flag the issue. These are proposed native checks, not tests already run; Gnumeric separately documents COMPLEX, IMPRODUCT, IMREAL, IMAGINARY, and IMABS [1].
Two further algebraic checks
Conjugation is an involution: conj(conj(z))=z. It also distributes over a sum: conj(z1+z2)=conj(z1)+conj(z2). For z1=3+4i, z2=1-2i, the sum is 4+2i and its conjugate is 4-2i. One can compare the documented function compositions =IMCONJUGATE(IMSUM("3+4i","1-2i")) and =IMSUM(IMCONJUGATE("3+4i"),IMCONJUGATE("1-2i")). Both mathematically represent 4-2i. This gives a stronger audit than assuming the first output must be correct.
Troubleshooting and constraints
| Problem | Resolution or evidence boundary |
|---|---|
#VALUE! |
Documented for invalid complex z; build the value through COMPLEX or correct the string [1]. |
Expecting -3-4i from 3+4i |
That is negation, not conjugation. Conjugation does not change the real coefficient. |
| Expecting a nonnegative numeric magnitude | Use IMABS, not IMCONJUGATE. The conjugate is still a complex number. |
| Unexpected suffix formatting | i and j are recognized within Gnumeric’s complex functions, but whether every composed operation preserves a chosen textual suffix is not established by the short manual note; verify natively. |
Source text contains unusual spacing, Unicode â…ˆ, mixed units or malformed signs |
The exact parser acceptance is not fully specified in the linked reference. Normalize input and test in the target application before asserting a result. |
| Blanks, booleans, error cells, imported strings | Coercion and error propagation beyond the invalid-complex #VALUE! rule were not executed or established. Avoid treating an empty input as 0+0i without tests. |
#NAME?, edit rejection or different separators |
Confirm Gnumeric version/function availability and the application’s locale. The examples use documented English comma syntax, not an assertion about every localized build. |
Gnumeric / Excel compatibility and release scope
The official Gnumeric 1.12 reference calls IMCONJUGATE Excel compatible [1], and the public function catalogue lists it as Complete / Basic [2]. Neither is evidence of identical result strings in all Excel builds, nor of native execution in Gnumeric here. Gnumeric 1.12.62’s announcement reports complex-function compatibility improvements [3]. Application-level validation should exercise negative/positive/purely imaginary numbers, both suffixes, conjugate-of-conjugate, multiplication-by-conjugate, malformed inputs, zeros and XLSX import/export on a current Gnumeric installation. The official download page says Linux/BSD distribution packages are preferred and Windows binaries are not currently distributed by the project [4].
Related Gnumeric guides
Software, version and evidence boundaries
This is a Gnumeric tutorial, not a formula transplanted from another spreadsheet. The Gnumeric 1.12 function manual documents the signature, argument meanings and listed errors [1]; the current official function catalogue lists this function as Complete / Basic (upstream status, not a test run here) [2]. The upstream 1.12.62 announcement describes improvements to complex-function Excel compatibility [3], but does not establish which older releases exhibit every behavior. The preferred distributed desktop environment is Linux/BSD; the project does not currently distribute Windows binaries [4].
All displayed results below are expected mathematical results independently checked, or directly documented error expectations. They are not observations from executing Gnumeric. Native tests, import/export round-trips and locale variants remain pending. The examples use the manual’s English function names, decimal points and comma argument separators; installed application locale/settings can affect formula entry and number display. Confirm your actual separators and formula editor on the target system before pasting formulas.
Official sources, checked 2026-10-13
- Gnumeric 1.12 Complex function reference — Gnumeric-specific syntax, descriptions, optional defaults and documented errors; function sections are identified inline.
- Gnumeric official function catalogue — catalogue presence and implementation/upstream test classifications, not runtime evidence for these worksheets.
- Gnumeric 1.12.62 upstream release announcement — release-level version and complex-compatibility context; no per-example validation claimed.
- Official Gnumeric download/platform guidance — supported distribution pathways as stated by maintainers.
Evidence boundary: The examples were independently calculated and checked against official documentation and the Gnumeric 1.12.62 source. Native execution, locale checks and file round-trips were not performed.