stan-dev / stan-dev/pystan

Tuple datatype io

Open
#394 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
366
Forks
61
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

Stan 2.33 brings us Tuple datatype. I think we need to handle this with a custom numpy dtype depending on the tuple type.

How can we access tuple type and pack incoming data correctly? And how should user give out the data for inits / data.

Custom numpy dtypes are easy to create and also support access to individual components, but we probably should either have small example how to work with them or a functionality to unpack them.

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

No files, tests, or entry points are named. First clarify how Stan 2.33 tuple types should be accessed and how tuple data should be packed or unpacked for inits and data, including whether custom NumPy dtypes or examples are expected; done means the supported representation and user-facing behavior are defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
numpy, python
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.