Refine error message when user has a subsampling scheme conflict
This message asks the user to first check whether they defined conflicting
attributes before checking whether they have a conflicting subsampling scheme
name.
@@ -287,7 +287,7 @@ def _get_subsampling_settings(wildcards):
# throw an error instead of assuming the user prefers one setting over
# another by default.
if subsampling_settings.get("max_sequences") and subsampling_settings.get("seq_per_group"):
- raise Exception(f"The subsampling scheme '{subsampling_scheme}' for build '{wildcards.build_name}' defines both `max_sequences` and `seq_per_group`, but these arguments are mutually exclusive. This could be caused by using the same subsampling scheme name as a default scheme. If so, try renaming your subsampling scheme, '{subsampling_scheme}', to a unique name (e.g., 'custom_{subsampling_scheme}').")
+ raise Exception(f"The subsampling scheme '{subsampling_scheme}' for build '{wildcards.build_name}' defines both `max_sequences` and `seq_per_group`, but these arguments are mutually exclusive. If you didn't define both of these settings, this conflict could be caused by using the same subsampling scheme name as a default scheme. In this case, rename your subsampling scheme, '{subsampling_scheme}', to a unique name (e.g., 'custom_{subsampling_scheme}') and run the workflow again.")
# If users have supplied neither `max_sequences` nor `seq_per_group`, we
# throw an error because the subsampling rule will still group by one or
