Improve readability by packing frequently used variables into namedtuples.

[zoj613]

closes #67

Here are a few important guidelines and requirements to check before your PR can be merged:

• There is an informative high-level description of the changes.
• The description and/or commit message(s) references the relevant GitHub issue(s).
• pre-commit is installed and set up.
• The commit messages follow these guidelines.
• The commits correspond to relevant logical changes, and there are no commits that fix changes introduced by other commits in the same branch/BR. If your commit description starts with "Fix...", then you're probably making this mistake.
• There are tests covering the changes introduced in the PR.

Don't worry, your PR doesn't need to be in perfect order to submit it. As development progresses and/or reviewers request changes, you can always rewrite the history of your feature/PR branches.

If your PR is an ongoing effort and you would like to involve us in the process, simply make it a draft PR.

[zoj613]

@rlouf could you please help diagnose the one failed test test_nuts_mcse? It appears that the MCSE fails for one of the cases in the NUTS sampler. The changes seem fine and do not appear to change behavior so i'm a little confused.

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (75fd205) 100.00% compared to head (53f8f8b) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #99   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           13        13           
  Lines          544       565   +21     
  Branches        31        31           
=========================================
+ Hits           544       565   +21     

Impacted Files	Coverage Δ
aehmc/algorithms.py	100.00% <100.00%> (ø)
aehmc/hmc.py	100.00% <100.00%> (ø)
aehmc/integrators.py	100.00% <100.00%> (ø)
aehmc/nuts.py	100.00% <100.00%> (ø)
aehmc/proposals.py	100.00% <100.00%> (ø)
aehmc/step_size.py	100.00% <100.00%> (ø)
aehmc/termination.py	100.00% <100.00%> (ø)
aehmc/trajectory.py	100.00% <100.00%> (ø)
aehmc/window_adaptation.py	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[brandonwillard]

These changes look great!

[brandonwillard]

What are these comments indicating?

[zoj613]

The dual averaging state's "iterates" is represented by the log_step_size variable and the "shrinkage_pts" is represented by the mu variable in the context of this function. Is this correct, @rlouf ?

[brandonwillard]

These updates look great; I'm ready to move forward with them.

[zoj613]

These updates look great; I'm ready to move forward with them.

I will still need to look into updating the docstrings. @rlouf any thoughts on these changes?

[brandonwillard]

Merged, because these changes are already very helpful. We can add follow-ups for the docstrings and anything else.