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

(Pipeline Implementation) Points to clarify with devbio #4273

Open
islean opened this issue Mar 7, 2025 · 5 comments
Open

(Pipeline Implementation) Points to clarify with devbio #4273

islean opened this issue Mar 7, 2025 · 5 comments

Comments

@islean
Copy link
Contributor

islean commented Mar 7, 2025

We have in our codebase certain parts of the code which are unclear to us system developers. The intent should be documented and the code rewritten in some instances. This issue will be used to gather points to discuss with the devbio people.

@islean
Copy link
Contributor Author

islean commented Mar 7, 2025

There is awhile True loop in the analysis api:

def replace_values_in_params_file(self, workflow_parameters: dict) -> dict:
        replaced_workflow_parameters = copy.deepcopy(workflow_parameters)
        """Iterate through the dictionary until all placeholders are replaced with the corresponding value from the dictionary"""
        while True:

@islean
Copy link
Contributor Author

islean commented Mar 10, 2025

Could we name the variables in servers a bit more explicitly? Params -> parameters_file and type hint it as path in cg for example?

@islean
Copy link
Contributor Author

islean commented Mar 10, 2025

The get_sex_code method returns ints as a string but the intent seem to be to use them as ints. We should consider clearing this up.

@islean
Copy link
Contributor Author

islean commented Mar 10, 2025

_extract_read_files should only have a single boolean input, not two.

@islean
Copy link
Contributor Author

islean commented Mar 10, 2025

Maybe move def _get_data_analysis_type(self, case_id: str) -> str: to the store

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

No branches or pull requests

1 participant