Contact

IMARCSEC Function (Gnumeric)

Engineering Intermediate Gnumeric

Use IMARCSEC in Gnumeric to invert a complex secant response. Learn the syntax, branch limits and reproducible examples.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: =IMARCSEC("1+2i") has expected value approximately 1.384478273 + 0.39656823i. It finds a complex inverse of secant, not the reciprocal of another inverse function.

Availability and version history

  • Introduced: 1.1.6, according to the official release history. This was a development-series release.
  • 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. Official source and independent mathematical examples checked; Gnumeric 1.12.62 was not run.

What IMARCSEC calculates

For nonzero z, the release computes acos(1/z), using the principal branch of IMARCCOS. Both real and imaginary coefficients matter. The forward relationship is IMSEC(IMARCSEC(z))ā‰ˆz for finite nonsingular inputs. Function reference; release algorithm.

An inverse returns one representative because the forward function is not one-to-one. Applying the functions in the reverse order need not recover an arbitrary original argument. ā€œInverseā€ does not mean 1/IMSEC(z).

Syntax and inputs

=IMARCSEC(z)

There is one required argument and no optional flag. Use a quoted complex literal such as "1+2i", a cell containing complex text, or COMPLEX(real,imaginary). A real numeric input represents a complex number with zero imaginary part. COMPLEX has an optional "i"/"j" suffix; its default is "i".

=IMARCSEC(COMPLEX(1,2))
=IMARCSEC(A2)

Do not type an unquoted 1+2i arithmetic expression. The examples use decimal points and commas inside multi-argument functions; use your installation’s formula conventions.

Reproducible examples

Enter each formula in its stated row. The expected values below are independent mathematical references rounded to nine decimal places. Use =IMREAL(B2) and =IMAGINARY(B2) to compare coefficients rather than formatted strings.

Row Formula in A Formula in B Expected value, approximately
2 =COMPLEX(1,2) =IMARCSEC(A2) 1.384478273 + 0.39656823i
3 =COMPLEX(2,1) =IMARCSEC(A3) 1.169209935 + 0.215612419i
4 =COMPLEX(3,4) =IMARCSEC(A4) 1.452045595 + 0.160445534i
5 =COMPLEX(1,1) =IMARCSEC(A5) 1.11851788 + 0.530637531i
6 =COMPLEX(0.5,0.2) =IMARCSEC(A6) 0.439322126 + 1.260309917i
7 =COMPLEX(2,0) =IMARCSEC(A7) 1.047197551 + 0i
8 =COMPLEX(1,0) =IMARCSEC(A8) 0 + 0i
9 =COMPLEX(0.25,-0.5) =IMARCSEC(A9) 1.161532911 āˆ’ 1.322933165i

Branches and special inputs

The parent arccosine cuts map to real-axis intervals between āˆ’1 and +1, with zero excluded. The endpoints ±1 are branch points. A real input whose magnitude is less than 1 generally has a complex inverse secant; do not discard its imaginary coefficient.

Zero cannot be used in the reciprocal definition. Near zero, numerical range and branch sensitivity require extra care, especially when measurements have been rounded. Pinned implementation.

The mapped cut descriptions follow the reciprocal algorithm and the parent inverse’s documented branches. They do not establish every exact-cut or signed-zero display convention in every installed build. Compare values just to either side when a model crosses a cut.

Worked model and reconstruction check

For a model R=sec(Īø), put 1+2i in A2 and =IMARCSEC(A2) in B2. The output is a candidate complex angle in radians. Cosine is even and periodic, so ±θ+2Ļ€k are alternative solutions. Use the model’s sign and continuity conditions to choose one.

In a separate scratch area, use these formulas with that A2/B2 example:

=IMCOS(B2)
=IMSEC(B2)
=IMABS(IMSUB(IMSEC(B2),A2))

The cosine should equal 1/z. Compare this cell with =IMDIV("1",A2), not with the unmodified response. The second formula reconstructs z, and the final formula measures the residual. The independent calculation for 1+2i reconstructs both coefficients within 1eāˆ’12. Select a tolerance appropriate to the scale and input uncertainty; a correct identity does not validate a physical model.

Errors and practical checks

The release parser maps malformed complex strings to #NUM!. The web manual’s generic invalid-input note instead says #VALUE!; use the pinned source when diagnosing this release. Unsupported types can reach a value error, and argument coercion before the helper can affect empty cells or Booleans. Start with explicit COMPLEX inputs when troubleshooting.

Check that the response is dimensionless where the model requires it, preserve both coefficients, and avoid replacing a branch-sensitive complex input with its magnitude. These Gnumeric-specific names and branch conventions should be checked separately when transferring a workbook to another program.

Official sources