Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

To define: is reference_cycle the right argument name? #716

Closed
tcompa opened this issue Apr 22, 2024 · 2 comments · Fixed by #719
Closed

To define: is reference_cycle the right argument name? #716

tcompa opened this issue Apr 22, 2024 · 2 comments · Fixed by #719
Assignees

Comments

@tcompa
Copy link
Collaborator

tcompa commented Apr 22, 2024

In the following task-function signature, should we replace reference_cycle with reference_acquisition?

@validate_arguments
def apply_registration_to_image(
    *,
    # Fractal parameters
    zarr_url: str,
    # Core parameters
    registered_roi_table: str,
    reference_cycle: int = 0,
    overwrite_input: bool = True,
):

During the preparation of acq_dict, we use image.acquisition for the keys of acq_dict:

        acquisition_dict = {}
        for image in self.well.images:
            if image.acquisition is None:
                raise ValueError(
                    "Cannot get acquisition paths for Zarr files without "
                    "'acquisition' metadata at the well level"
                )
            if image.acquisition not in acquisition_dict:
                acquisition_dict[image.acquisition] = []
            acquisition_dict[image.acquisition].append(image.path)
        return acquisition_dict
@jluethi
Copy link
Collaborator

jluethi commented Apr 22, 2024

Agreed!

@jluethi
Copy link
Collaborator

jluethi commented Apr 22, 2024

Same in the calculate registration & the find consensus then

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

2 participants