# Uncertainty shock implementations

**URL:** <https://forum.dynare.org/t/uncertainty-shock-implementations/19857>\
**Category:** Stochastic simulations\
**Created:** [23 February 2022 04:22 UTC](https://forum.dynare.org/t/uncertainty-shock-implementations/19857 "2022-02-23T04:22:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jpfeifer](https://forum.dynare.org/user_avatar/forum.dynare.org/jpfeifer/32/5044_2.png) [@jpfeifer](https://forum.dynare.org/u/jpfeifer)\
**Post date:** [25 February 2022 08:07 UTC](https://forum.dynare.org/t/uncertainty-shock-implementations/19857/3 "2022-02-25T08:07:00Z")

</div>

1. I am not sure I understand the question. For `sigOstar*epsPOstar`, `sigOstarss` only gives you the standard deviation if `epsPOstar` has standard deviation 1. As a sidenote, see point 1 of

> [@Shock to standard deviation](https://forum.dynare.org/t/shock-to-standard-deviation/16857/7):
>
> Mostly yes. But You are using a log-log-specification, whose moments do not exist. [See Andreasen (2010)](https://doi.org/10.1016/j.econlet.2010.03.007) I would recommend against GIRFs. See [https://github.com/JohannesPfeifer/DSGE\_mod/blob/master/Basu\_Bundick\_2017/Basu\_Bundick\_2017.mod](https://github.com/JohannesPfeifer/DSGE_mod/blob/master/Basu_Bundick_2017/Basu_Bundick_2017.mod) for an alternative.

1. To shut off uncertainty, you can simply set its standard deviation to 0.
2. What do you mean with “turning epsPOstar off”? You usually just want to keep it to 0 on average in GIRFs as in [DSGE\_mod/Basu\_Bundick\_2017/Basu\_Bundick\_2017.mod at master · JohannesPfeifer/DSGE\_mod · GitHub](https://github.com/JohannesPfeifer/DSGE_mod/blob/master/Basu_Bundick_2017/Basu_Bundick_2017.mod)

---

_[View the full topic](https://forum.dynare.org/t/uncertainty-shock-implementations/19857)._
