generated from allenai/python-package-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Description
🚀 The feature, motivation and pitch
Release of code, with enough flexibility for DR1 analysis
Alternatives
No response
Additional context
- Run w0wa notebook with ext input files in CFP and check results same @santiagocasas
- Then copy DR1 specs into EC gitlab and run also the notebook above with DR1 and check @santiagocasas
- Split numbers to contain ngal and area and others for spectro (one sample), photo (lenses and sources) @santiagocasas
- Generalize the config.py, removing hardcoded numbers, moving them to their respective classes and provide optionality of passing them through the specs yaml @santiagocasas
- Do this bias generalization until Q-bias can be properly implemented @santiagocasas
- Point above, requires for instance to generalize the spectro .dat files into .yaml files
- Look into the config yaml files and how to install them in the package, create a configs module (folder) @Sefa76
- Look into data files like n(z) or lumratio, which are large. For instance users should download files themselves or we provide a small download script. Maybe even in python. @Sefa76
- For lumratio, make something like ignoring beta, if this download hasn't happened @Sefa76
- Test suite
- Reach 50% coverage
Metadata
Metadata
Assignees
Labels
No labels