stan-dev / stan-dev/cmdstanpy

documentation for CmdStanPy optimization

Open
#629 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
Python
Stars
198
Forks
81
PR merge metrics
No merged PRs in 30d

Description

Summary:

A bunch of suggestions for making the optimization doc easier to understand.

  • User's Guide: Maximum Likelihood Estimation

    • we should indicate that (a) we get penalized MLEs as well as MLE in the title and description, (b) explain that this means turning the Jacobian adjustment off, and (c) that with Jacobian adjustment off we do not get the posterior mode, aka the max a posteriori (MAP) estimate a Bayesian is likely to expect
    • we should indicate _np suffix is NumPy ndarray and _pd is a pandas data frame
    • we should break the output for running optimize, printing the _dict, printing the _np, and printing the _pd values
    • we should indicate the result is on the constrained scale
  • API Docs

    • indicate that results are on the constrained scale in CmdStanMLE
    • replace forward apostrophes with back ticks to get rendered quotes (both here and above)
Current Version:

1.0.7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the User's Guide section titled “Maximum Likelihood Estimation” and the API documentation for CmdStanMLE. Review each checklist item against the current wording and examples, including the NumPy and pandas result descriptions. Done means the guide and API docs explain the requested scales, estimates, suffixes, output steps, and rendered quotes.

Written by the indexing model from the issue text.

Assessment

Tech stack
numpy, pandas, python
Domain
api, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.