# Init progress bar gone?

**URL:** <https://discourse.pymc.io/t/init-progress-bar-gone/863>\
**Category:** Questions\
**Created:** [February 15, 2018, 8:26pm UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863 "2018-02-15T20:26:25Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![madanh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/madanh/32/500_2.png) [@madanh](https://discourse.pymc.io/u/madanh)\
**Post date:** [February 15, 2018, 8:26pm UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863/1 "2018-02-15T20:26:25Z")

</div>

I just installed pymc3 from conda-forge on a different computer and don’t see progress bar during init. Is this intentional?

---

<div class="post-metadata">

**Author:** ![junpenglao](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/junpenglao/32/8_2.png) [@junpenglao](https://discourse.pymc.io/u/junpenglao)\
**Post date:** [February 15, 2018, 8:27pm UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863/2 "2018-02-15T20:27:49Z")

</div>

There is not progressbar for the current defautl initiualization `jitter+adapt_diag`

---

<div class="post-metadata">

**Author:** ![madanh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/madanh/32/500_2.png) [@madanh](https://discourse.pymc.io/u/madanh)\
**Post date:** [February 15, 2018, 8:33pm UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863/3 "2018-02-15T20:33:43Z")

</div>

Uhm, I was using ‘advi+adapt\_diag’… 😕… double checking…

---

<div class="post-metadata">

**Author:** ![madanh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/madanh/32/500_2.png) [@madanh](https://discourse.pymc.io/u/madanh)\
**Post date:** [February 15, 2018, 8:55pm UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863/4 "2018-02-15T20:55:46Z")

</div>

OK, confirmed. In fact init\_nuts is never entered. I’m investigating if the fact that I initialize the step before calling sample could be the cause

```auto
        step = pm.NUTS()
        trace = pm.sample(draws=conf.block_size,
                          chains=1,
                          njobs=njobs,
                          discard_tuned_samples=conf.discard_tuned_sample,
                          tune=tune,
                          init ='advi+adapt_diag',#conf.init,
                          step=step)

```

---

<div class="post-metadata">

**Author:** ![madanh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/madanh/32/500_2.png) [@madanh](https://discourse.pymc.io/u/madanh)\
**Post date:** [February 15, 2018, 9:02pm UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863/5 "2018-02-15T21:02:37Z")

</div>

OK, seems to be by design. If I want to use NUTS this way probably have to init it manually using a call to init\_nuts.

---

<div class="post-metadata">

**Author:** ![junpenglao](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/junpenglao/32/8_2.png) [@junpenglao](https://discourse.pymc.io/u/junpenglao)\
**Post date:** [February 16, 2018, 6:29am UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863/6 "2018-02-16T06:29:28Z")

</div>

Yeah if you are passing `step` to `pm.sample` it turns off the initialization. If you have specific kwarg wants to pass to `pm.NUTS()` you should try `nuts_kwarg=dict(......)`.

---

<div class="post-metadata">

**Author:** ![madanh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/madanh/32/500_2.png) [@madanh](https://discourse.pymc.io/u/madanh)\
**Post date:** [February 16, 2018, 1:22pm UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863/7 "2018-02-16T13:22:24Z")

</div>

Oh, that was not to supply kwargs but for my ad-hoc save-to-disk and peek-while-you-sample framework. I need to have a name for step instance in the scope of my module in order to pickle it 🙂 Maybe I’ll add a PR later today to have pm.sample optionally spit out step instance along with the trace. That would enable peeking during sampling for compound steps as well.

---

<div class="post-metadata">

**Author:** ![junpenglao](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/junpenglao/32/8_2.png) [@junpenglao](https://discourse.pymc.io/u/junpenglao)\
**Post date:** [February 16, 2018, 1:37pm UTC](https://discourse.pymc.io/t/init-progress-bar-gone/863/8 "2018-02-16T13:37:25Z")

</div>

I see. Yeah that part of the code is not very exposed. When you say peek while sample do you mean peeking the parameters in the sampler? Like kernel size etc? Maybe it is easier to cherry pick the code from pm.sample and call pm.sampling.\_iter\_sample directly.