> For the complete documentation index, see [llms.txt](https://slmetrics-docs.gitbook.io/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://slmetrics-docs.gitbook.io/v1/reference/regression-metrics/root-mean-squared-logarithmic-error/rmsle.md).

# rmsle.md

|       |                 |
| ----- | --------------: |
| rmsle | R Documentation |

### Root Mean Squared Logarithmic Error

#### Description

A generic S3 function to compute the *root mean squared logarithmic*\
*error* score for a regression model. This function dispatches to S3\
methods in `rmsle()` and performs no input validation. If you supply NA\
values or vectors of unequal length (e.g. `length(x) != length(y)`), the\
underlying `C++` code may trigger undefined behavior and crash your `R`\
session.

**Defensive measures**

Because `rmsle()` operates on raw pointers, pointer-level faults (e.g.\
from NA or mismatched length) occur before any `R`-level error handling.\
Wrapping calls in `try()` or `tryCatch()` will *not* prevent `R`-session\
crashes.

To guard against this, wrap `rmsle()` in a "safe" validator that checks\
for NA values and matching length, for example:

{% code overflow="wrap" lineNumbers="true" %}

```r
safe_rmsle <- function(x, y, ...) {
  stopifnot(
    !anyNA(x), !anyNA(y),
    length(x) == length(y)
  )
  rmsle(x, y, ...)
}
```

{% endcode %}

Apply the same pattern to any custom metric functions to ensure input\
sanity before calling the underlying `C++` code.

#### Usage

```r
## Generic S3 method
## for Root Mean Squared Logarithmic Error
rmsle(...)

## Generic S3 method
## for weighted Root Mean Squared Logarithmic Error
weighted.rmsle(...)
```

#### Arguments

| `...` | <p>Arguments passed on to <code>rmsle.numeric</code>,<code>weighted.rmsle.numeric</code></p><p><code>actual,predicted</code></p><p>A pair of \<double> vectors of length <code>n</code>.</p><p><code>w</code></p><p>A \<double> vector of sample weights.</p> |
| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

#### Value

A \<double> value

#### References

James, Gareth, et al. An introduction to statistical learning. Vol. 112.\
No. 1. New York: springer, 2013.

Hastie, Trevor. "The elements of statistical learning: data mining,\
inference, and prediction." (2009).

Virtanen, Pauli, et al. "SciPy 1.0: fundamental algorithms for\
scientific computing in Python." Nature methods 17.3 (2020): 261-272.

#### Examples

```r
## Generate actual
## and predicted values
actual_values    <- c(1.3, 0.4, 1.2, 1.4, 1.9, 1.0, 1.2)
predicted_values <- c(0.7, 0.5, 1.1, 1.2, 1.8, 1.1, 0.2)

## Evaluate performance
SLmetrics::rmsle(
   actual    = actual_values, 
   predicted = predicted_values
)
```

```

</div>

```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://slmetrics-docs.gitbook.io/v1/reference/regression-metrics/root-mean-squared-logarithmic-error/rmsle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.