simonsobs / simonsobs/sotodlib
Overhead to read the sparce weight map
Open
@chervias is already working on this.
Since Jul 3, 2024.
- Dominant language
- Python
- Stars
- 19
- Forks
- 23
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 14
Description
I found it takes long to read pixel weight file.
It is just because we are saving weight with shape of (3, 3, ny, nx) although non-diagonal parts of
weight are all zero by definition of filter-bin mapmaking.
As shown in the screen shot of test, of course though, it takes 3 times longer to read weight than to read map.
Yuji pointed me out that must be painfull when we do null tests. So I suggest that we save the diagonal part of weight in map making and pad the off-diagonal part in using the weight.
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.
Assessment
This issue has not been assessed yet.