Fix: multichain does not use any init file besides the first #1191
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Submisison Checklist
./runCmdStanTests.py src/test
Summary:
Currently, if you are using
num_chains
with initialization files for each chain, only the first is actually used. This was found by investigating a (similar, but unique) bug in cmdstanpy: stan-dev/cmdstanpy#687The bug ultimately comes down to one character,
files_1
vsfiles_i
, and has existed since the original implementation in #987Intended Effect:
Allow multiple chains to use separate init files
How to Verify:
New test added
Side Effects:
This also unifies the behavior of init files with the outputs etc, such that the chain ID is used rather than hardcoding numbers started at 1.
Documentation:
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses: