# Priorsense 1.0 is now on CRAN

**URL:** <https://discourse.mc-stan.org/t/priorsense-1-0-is-now-on-cran/35635>\
**Category:** Publicity\
**Created:** [June 25, 2024, 9:45am UTC](https://discourse.mc-stan.org/t/priorsense-1-0-is-now-on-cran/35635 "2024-06-25T09:45:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![n-kall](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@n-kall](https://discourse.mc-stan.org/u/n-kall)\
**Post date:** [June 25, 2024, 9:45am UTC](https://discourse.mc-stan.org/t/priorsense-1-0-is-now-on-cran/35635/1 "2024-06-25T09:45:48Z")

</div>

priorsense 1.0 has been released and is now available on [CRAN](https://cran.r-project.org/web/packages/priorsense/index.html).

priorsense is an R package for efficiently checking whether the posterior is sensitivity to changes to the prior or likelihood (see the [website](https://n-kall.github.io/priorsense) and [paper](https://link.springer.com/article/10.1007/s11222-023-10366-5) for details). It works with Stan (brms, rstan or cmdstanr) fits, or just posterior draws, as long as the log prior density and log likelihood evaluations (at the locations of the posterior draws) are available.

For Python users, the primary diagnostic is also available in [ArviZ](https://python.arviz.org/en/latest/api/generated/arviz.psens.html).

While reaching 1.0 and releasing on CRAN represents a significant milestone, development continues. If there are any suggestions for features, issues or bug reports, don’t hesitate to make an issue on the [GitHub issue tracker](https://github.com/n-kall/priorsense/issues) or get in touch directly.

---

<div class="post-metadata">

**Author:** ![mhollanders](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mc-stan.org/mhollanders/32/17623_2.png) [@mhollanders](https://discourse.mc-stan.org/u/mhollanders)\
**Post date:** [June 25, 2024, 11:18am UTC](https://discourse.mc-stan.org/t/priorsense-1-0-is-now-on-cran/35635/2 "2024-06-25T11:18:47Z")

</div>

Congratulations, this looks incredibly useful! FYI I think it could be worthwhile to highlight which variables should be included in the Stan program. It appears that it’s `log_lik` and `lprior`? Thanks!

---

<div class="post-metadata">

**Author:** ![jonah](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mc-stan.org/jonah/32/200_2.png) [@jonah](https://discourse.mc-stan.org/u/jonah)\
**Post date:** [June 25, 2024, 2:49pm UTC](https://discourse.mc-stan.org/t/priorsense-1-0-is-now-on-cran/35635/3 "2024-06-25T14:49:41Z")

</div>

Looks great!

---

<div class="post-metadata">

**Author:** ![avehtari](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mc-stan.org/avehtari/32/5935_2.png) [@avehtari](https://discourse.mc-stan.org/u/avehtari)\
**Post date:** [June 25, 2024, 5:13pm UTC](https://discourse.mc-stan.org/t/priorsense-1-0-is-now-on-cran/35635/4 "2024-06-25T17:13:17Z")

</div>

> [@mhollanders](#):
>
> It appears that it’s `log_lik` and `lprior`?

Yes. Although you can also use other names, and you can have several variables for different parts of prior

---

<div class="post-metadata">

**Author:** ![Nirajan\_bam](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mc-stan.org/nirajan_bam/32/15586_2.png) [@Nirajan\_bam](https://discourse.mc-stan.org/u/Nirajan_bam)\
**Post date:** [July 17, 2024, 1:13am UTC](https://discourse.mc-stan.org/t/priorsense-1-0-is-now-on-cran/35635/5 "2024-07-17T01:13:31Z")

</div>

Congratulations!!