Downsampling script for tadpoles

[alessandrofelder]

Description

What is this PR

• Bug fix
• Addition of a new feature
• Other

Why is this PR needed?

Keep track of how we downsampled the tadpole data.

What does this PR do?

Add script for tadpole downsampling and organising (to go from "sourcedata" to "rawdata")

References

\

How has this PR been tested?

Visual inspection of tadpole data. Downsampling functionality added with tests in #21

Is this a breaking change?

No

Does this PR require an update to the documentation?

Not yet

Checklist:

• The code has been tested locally
• Tests have been added to cover all new functionality (unit & integration)
• The documentation has been updated to reflect any changes
• The code has been formatted with pre-commit

[niksirbi]

I think this is good to go as is, but I'm slightly confused as to why certain arguments are hard-coded in the functions (e.g. in_plane_resolution), while others are supplied as CLI arguments (e.g. target_isotropic resolution).

Is the logic that some factors - like in-plane resolution - are intrinsic to the source images themselves, and hence unchanging, while the arguments supplied through the CLI can be used to run the downsampling in different ways (e.g. send results to a different path, or change the downsampling factor)?

This discussion is largely moot, since we are planning to anyway refactor and possible used a config, but I'm just curious.

[alessandrofelder]

but I'm just curious.

I was being a minimalist, and for our current purpose we needed to downsample to different target isotropic resolutions, but all our images had the same (anisotropic) resolution?