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

change: Split Behaviour #70

Closed
mathysgrapotte opened this issue Jan 30, 2025 · 0 comments · Fixed by #86
Closed

change: Split Behaviour #70

mathysgrapotte opened this issue Jan 30, 2025 · 0 comments · Fixed by #86
Assignees

Comments

@mathysgrapotte
Copy link
Owner

mathysgrapotte commented Jan 30, 2025

Currently, split_csv is expected to work with a sub-config. Which is different from the overall nextflow design (split once - perform experiments after).

Two possibilities :

implement sub-splits, would look like this :

full_yaml -> yaml_with_split_1 ; yaml_with_split_2
yaml_with_split_1 -> subconfigs
yaml_with_split_2 -> subconfigs (pipeline ran twice)

re-run split with every sub-config (could be expensive).

Only allow one split option

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

Successfully merging a pull request may close this issue.

2 participants