Skip to content

[Help Wanted] Refactor matching logic #1686

@kylesayrs

Description

@kylesayrs
  • There currently exist 17 different functions for matching modules/parameters. Let's consolidate this logic by using only the functions defined in utils/match.py
Function Used for/by Maps to
get_layer_by_name awq attrgetter(layer_name)(module)
get_layers_params pruning modifiers match_named_parameters
get_param None Delete
get_params get_layers_params , get_param Delete
set_layer Distillation modifier Module.set_submodule
get_layer None Delete
get_layers Lots match_named_modules
match_layers_params get_layers Delete
get_default_params match_layers_params Delete
match_targets Many match_named_modules
get_quantizable_layers match_layers_params Delete, use explicit targets
get_prunable_layers match_layers_params Delete, use explicit targets
get_terminal_layers match_layers_params Delete, use explicit targets
get_matching_layer Smoothquant match_modules_set
AWQ.set_resolved_mappings AWQ match_modules_set
match_modules sequential pipeline match_named_modules
get_linear_layers infer_sparsity_structure_from_model match_named_modules

Metadata

Metadata

Assignees

Labels

compressed-tensorsRelates to compressed-tensorsgood first issueA good first issue for users wanting to contribute

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions