stan-dev / stan-dev/docs

question - mismatch between SUG chapters

Open
#782 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
TeX
Stars
43
Forks
133
Avg merge
11h 32m
Merged PRs (30d)
4

Description

Summary:

question from Stan slack:

The section on Sparse data structures solves the problem of sparse data by converting the data to "long" format, and using a for-loop in the likelihood statement. It then goes on to state that using segment is better solving the related problem of ragged data structures, saying that "A full database type structure could be used, as in the sparse example, but this is inefficient, wasting space for unnecessary indices and not allowing vector-based density operations.". But, over in the section on multiple indexing, the example seems to be equivalent to the unvectorized Sparse data structure example. Am I missing something? Why can't we vectorize the likelihood for the sparse data example using multiple indexing?

Description:

Git blame shows that @bob-carpenter updated the multi-index chapter in 2021. sparse-ragged chapter is pretty much unchanged. should they both be updated?

Contributor guide

No contributing guide indexed for this repository

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 by comparing the linked Sparse data structures and multiple indexing sections, including their examples and claims about vectorization. Check the 2021 multi-index update against the largely unchanged sparse-ragged chapter. Done means the relationship is explained consistently and both chapters are updated if needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
tex
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.