log
Generic Description
Computes the natural logarithm in Nexyron expression evaluation. It is documented separately because numeric transforms change ranking, thresholds, and buckets in ways planner tools must not guess.
Simple example:
RETURN log(10.0) AS value
Consumer-Level Explanation
Use it as a readable log transform for positive values before comparing highly skewed magnitudes. Prefer this function when the transformation is a deliberate part of the model or report, and name the derived value in a WITH stage when it will be reused.
More Detailed Explanation
log is scalar math, so it is evaluated per row after graph patterns, procedure output, or map projections have produced values. Keep it close to the query when thresholds, ranking, and derived fields need to be auditable and reproducible.
Advanced Example
This example applies log to a named score component after matching graph data, making the derived metric reviewable before ordering.
MATCH (d:Document)
WITH d, properties(d).prize + 1.0 AS adjusted_priority
RETURN d.title AS document,
log(adjusted_priority) AS log_priority
ORDER BY log_priority DESC
Real Use Cases
- distance-from-target scoring
- numeric bucketing and normalization before
ORDER BYor aggregation - making scoring formulas visible to query review and assistant tooling
Real Limitations And Tradeoffs
- invalid numeric inputs produce null-like results rather than a repaired value
- math functions do not fix poor feature scaling; choose transformations intentionally
- nondeterministic functions such as random sampling are not appropriate for persisted decisions