Open koflera opened 4 months ago
paramters should parameters, inital should be initial
before
should begrad_before
https://github.com/PTB-MR/mrpro/blob/250d0ad528406274c4b9b5f0a3f1d687f325aa55/tests/algorithms/test_optimizers.py#L82
FIXED
WASABI and WASABITI signal model classes should be defined as _WASABI and _WASABITI and then they should be imported via init here https://github.com/PTB-MR/mrpro/blob/250d0ad528406274c4b9b5f0a3f1d687f325aa55/src/mrpro/operators/models/__init__.py#L3
FIXED in #218
If c is coils then use coils rather than c in
and
remove print statement https://github.com/PTB-MR/mrpro/blob/250d0ad528406274c4b9b5f0a3f1d687f325aa55/src/mrpro/operators/models/_WASABITI.py#L91
FIXED
Imports in tests should be
from mrpro.operators.models import InversionRecovery
rather than
from mrpro.operators.models._InversionRecovery import InversionRecovery
https://github.com/PTB-MR/mrpro/blob/250d0ad528406274c4b9b5f0a3f1d687f325aa55/tests/operators/models/test_t1_models.py#L4 https://github.com/PTB-MR/mrpro/blob/250d0ad528406274c4b9b5f0a3f1d687f325aa55/tests/operators/models/test_wasabi.py#L4 https://github.com/PTB-MR/mrpro/blob/250d0ad528406274c4b9b5f0a3f1d687f325aa55/tests/operators/models/test_wasabiti.py#L4
FIXED in #218
In the latest commit f7c9ccb to #193 I enabled the typos pre-commit hook. The tool found and fixed all mentioned typos as far as I can tell.
IMO it's nicer to have an automated typo detection and correction than manually reporting them here.
Still, the "wrong" imports of the signal models etc. have to be corrected manually...
The tool found and fixed all mentioned typos as far as I can tell.
That's great!
I guess the tool will "only" fix typos in comments (which is a good thing) and there might still be typos in variable/function/class names which we could collect here.
we use max_iters
and max_iterations
in our code but I think it should be n_max_iterations
everywhere
superseded by #340
should we follow e.g. official numpydoc style for references: https://numpydoc.readthedocs.io/en/latest/format.html#references as we did here https://github.com/PTB-MR/mrpro/blob/0730e0608366b422c59c0c5ffa50a94fba671cf2/src/mrpro/utils/Rotation.py#L640
Sometimes we use Raises
and Returns
in the docstring sometimes we don't.
should we follow e.g. official numpydoc style for references: https://numpydoc.readthedocs.io/en/latest/format.html#references as we did here
Pulled this into its own seperate issue #351 to link the according PR
A collection of typos + formatting issues still present in the main branch which could address in a separate PR once the list becomes long enough...