introducing DBlock, working it into the ATMC simulator, see #1371 #1411
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.
This PR works towards #1371 , namely to align HARK's modeling capabilities with the needs of the 'DYNARK' language, as anticipated based on last year's research sprint.
This PR introduces a new modeling component, a
DBlock
, which can include:This is a trivial change on top of the earlier generic monte carlo functionality, just repackaging the data into a 'block' unit. But this PR updates the GMC simulator, and introduces new automated testing of the model and block objects.
This is a necessary step towards future work, which is reserved for other PRs, including:
The 'DBlock' construct is based on Matt's original spec from some time ago. It admittedly does not have all the bells and whistles of the notional
nohablo
style block. However, it captures all of the currently available simulator functionality. The purpose of this step is to begin the co-development of the block definition with the monte carlo simulator, which determines its semantics.This PR is ready for review.