reusing flats/darks from a different scan

[dkazanc]

Enables reusing flats/darks coming from a different scan by providing an additional image_key_path parameter.

Checklist

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have made corresponding changes to the documentation

[dkazanc]

@yousefmoazzam I've got few test failures (6) in this branch that are related to the output filename changes. Specifically the error is:

AssertionError: assert 2 == 1
 +  where 2 = len(['/tmp/pytest-of-algol/pytest-0/test_recon_method_output_filen3/some-recon.h5', '/tmp/pytest-of-algol/pytest-0/test_recon_method_output_filen3/some-recon.h5-3056533504-35197.lock'])
 

Have you seen this one? I reckon it counts the lock file being temporarily there.

[yousefmoazzam]

@yousefmoazzam I've got few test failures (6) in this branch that are related to the output filename changes. Specifically the error is:

AssertionError: assert 2 == 1
 +  where 2 = len(['/tmp/pytest-of-algol/pytest-0/test_recon_method_output_filen3/some-recon.h5', '/tmp/pytest-of-algol/pytest-0/test_recon_method_output_filen3/some-recon.h5-3056533504-35197.lock'])
 

Have you seen this one? I reckon it counts the lock file being temporarily there.

I have indeed seen this when running tests locally, but not in recent CI jobs.

If CI were to also report the error then I'd be inclined to think that a dependency's version has been updated which breaks things, but that isn't the case. So unfortunately I'm not yet sure what to make of it.

[yousefmoazzam]

Just one comment for now about clarifying types, will keep looking

[yousefmoazzam]

Looks good overall, a few comments about making the new test a bit clearer, and some bits about docs.