generate quantities method always reports completion of chains in 0s

[mike-lawrence]

Not a big deal, but thought it worth reporting. When running the generate quantities method, compute indeed takes time but the printed progress always reports completion in 0.0s:

Running standalone generated quantities after 6 MCMC chains, 1 chain at a time ...

Chain 1 finished in 0.0 seconds.
Chain 2 finished in 0.0 seconds.
Chain 3 finished in 0.0 seconds.
Chain 4 finished in 0.0 seconds.
Chain 5 finished in 0.0 seconds.
Chain 6 finished in 0.0 seconds.

All 6 chains finished successfully.
Mean chain execution time: 0.0 seconds.
Total execution time: 106.2 seconds.

Current Version:

v2.35.0

[WardBrian]

@mike-lawrence what is this the output of? I believe all of the messages you're showing come from cmdstanr, not cmdstan

[mike-lawrence]

Ah, yes, I would have been using cmdstanR here.

[jgabry]

Thanks for moving the issue @WardBrian, I hadn't seen this. This isn't at the highest priority on my todo list, but it would be good to figure out why that's happening when I have some time. Thanks for reporting it @mike-lawrence.

[avehtari]

Thee messages come from cmdstanr, but the timing information missing from csv is due to missing functionality in stan services. I made another issue stan#3372. After that has been fixed, CmdStanR can be fixed to show the timing information from csv produced by CmdStan

[avehtari]

PR for Stan services writing the timing information for generated quantities has been merged stan-dev/stan#3373, so we are one step closer to fixing this also in CmdStanR