Notes from 08 May 2023

[jsv1206]

Tests:
Right now, the tests are not run automatically. We need to change that to run the tests in the /tests directory

• Pytest
• Check.py is for USER
• Unit tests are for developers - which we should be running whenever we change the code

New Issues:

• Run /tests during code development

  • Look into Test action from Template Repo
  • Change poetry install to deeplenstronomy install

• Clean up checks.py. Move maps to a setting file which check.py pulls

Github Project Labels:

• Include low, medium, high priority (needed to make code work)
• Low - wishlist, stretch (ex: parallelize). Medium - features that are nice but not strictly required. High - Required to make code work or a strict requirement for the release (ex: unit tests)

To do

• Issue 57 : create git branch
• Include tests to check the output
• When creating a PR, address the issue # in the comments

Are we still doing the following in this version of deeplenstronomy?

Original refactor idea:
Module splits:

• IO: deeplenstronomy, input_reader, visualizer, check, io stuff from utils
• Physics “images”: image generator, special
• configuration: surveys class (sub class) , physics class (sub class), non-extant functions for working with the configuration file via base template class
• utisland