Document Strided Structured Material Sets
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 248
- Forks
- 72
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 15
Description
We should document the information here:
https://github.com/LLNL/conduit/blob/dffc5a6c7b433665399231aa537469be32bce865/src/libs/relay/conduit_relay_io_silo.cpp#L2655-L2665
specifically the fact that strided structured mesh material sets only provide material data for zones that are actually in use, not for all zones.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/libs/relay/conduit_relay_io_silo.cpp at lines 2655-2665 and identify the documentation location for strided structured mesh material sets. Document that material data is provided only for zones actually in use, not for all zones; done means this behavior is clearly recorded for users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100