Codacy warning fixes

[ghost]

• Fixes line width in python documentation
• Markdown bullet point spacing
• Default nonTOF_distance_threshold in consistency test to 0.f

[ghost]

@KrisThielemans, can you take a look and confirm these changes?

[KrisThielemans]

thanks! Looks good to me. Tests are running, but will work of course.

sadly, Codacy isn't running on this repo. Maybe you can run it manually through the markdown checker?

[ghost]

Maybe you can run it manually through the markdown checker?

I am not 100% sure what markdown checker you are referring too but Prettier should handle it. It also matched the results of this one https://webutility.io/markdown-beautifier.

[KrisThielemans]

great. thanks. Codacy recommended another one, but I'm sure this is fine.

[ghost]

This PR did not seem to resolve the issue. https://app.codacy.com/gh/UCL/STIR/pullRequest?prid=12651966

[ghost]

I don't understand why (1.)

- Test non-TOF ROOT and STIR consistency, particularly the rotation.

(line 12) fails because of "Spacing between a list item’s bullet and its content violates a given style" while (2.)

- `README.md`: This file.

(line 25) is okay... The only difference is the second example starts with a grave accent/ back tick, and maybe it is picking up on that? Previous is incorrect, because (3.)

- `SourceFiles/`: Contains 8 `generate_image` parameter files and GATE macro files for the emission source positions. One pair of files for each simulation.

fails for the same reason.

[KrisThielemans]

Ah well. Codacy is apprently using https://github.com/remarkjs/remark-lint

I see the following full message on Codacy

Reported by remark-lint
Time to fix: 5 minutes
These files are included to :

• Test non-TOF ROOT and STIR consistency, particularly the rotation.
• Test the TOF STIR implementation is correct.
  Why is this an issue?
  Warn when the spacing between a list item’s bullet and its content violates a given style.

Options: 'tab-size', 'mixed', or 'space', default: 'tab-size'.

Fix
remark-stringify uses 'tab-size' (named 'tab' there) by default to ensure Markdown is seen the same way across vendors. This can be configured with the listItemIndent option. This rule’s 'space' option is named '1' there.

See Using remark to fix your Markdown on how to automatically fix warnings for this rule.

So, I guess we could try and run remark offline, or configure it appropriately, or... ignore the rule, as it displays just fine. I'm ok with the latter option, as there's more important things in life, but let me know what you want to do.

[ghost]

IMO, it is being too strict on a trivial issue for a non pre-commit enforcing change. If this can be ignored, let's just. do that.

[KrisThielemans]

Looks like Codacy still isn't happy about the constructor either. Oh well. Not sure why. I'll ignore.

[ghost]

That one makes no sense to me because it's value is set with this PR and, if it wasn't, codacy should warn about some others too. I'm sorry, I don't understand.