simonsobs / simonsobs/mnms

models from undowngraded data

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

Nobody has claimed this yet.

convenience science
Dominant language
Python
Stars
3
Forks
1
Avg merge
1m
Merged PRs (30d)
1

Description

pre-downgrading the data is kind of annoying and has potential issues, such as ringing from the edge and worrying about consistency of sims with the undowngraded data. this would incur a penalty but only at model-building time, which seems OK.

it also causes the production of sims on downgraded geometries, which is confusing to the end user. this would naturally solve that (at the possible penalty of disk-space usage). alternatively, inpainting white noise would solve this for pre-downgraded data too.

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

Review the model-building and simulation workflow to determine where downgraded data and geometries are introduced. Compare building models from undowngraded data with the stated inpainting alternative, including the consistency, ringing, disk-space, and performance trade-offs. Done means the selected approach produces simulations on undowngraded geometries with its costs understood.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.