[v2][_commonspeckle] SAXS.py not strictly for XPCS or speckles
Open
Nobody has claimed this yet.
_commonspeckle
discussion
Q-space
V2
- Dominant language
- Jupyter Notebook
- Stars
- 8
- Forks
- 12
- Avg merge
- 2h 53m
- Merged PRs (30d)
- 6
Description
This is for static SAXS analysis as noted by module author. Seems good to keep this in common, but if we stick it in an XPCS repo, I am not sure that it would be under utilized.
Also @danielballan mentioned something about a common scattering repo in previous meetings so I am also asking in this context. We could decide on a two-phase plan regarding this.
1 """
2 Sep 10 Developed by Y.G.@CHX
3 yuzhang@bnl.gov
4 This module is for the static SAXS analysis, such as fit form factor
5 """
Contributor guide
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 by reviewing SAXS.py and its module docstring, which describes static SAXS analysis. Resolve whether it should remain in pyCHX/common or move to a common scattering repository, and document the agreed two-phase plan and final location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100