Fixes observer attachment to model based on config for wanda sparsifier

[agrawal-aka]

This PR fixes the issue https://github.com/pytorch/ao/issues/1133 by only attaching the observers to the layers passed in the sparse config.
Earlier irrespective of the layers being defined in sparse config, the observer was being attached to the entire model, leading to runtime errors as mentioned in the issue.

cc: @jcaip

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/1265

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• [DomainsOnly] Jobs fail with GLIBC version not found

❌ 10 New Failures

As of commit 07b842a with merge base ccd883b ():

NEW FAILURES - The following jobs have failed:

• Code Analysis with Ruff / build (3.9) (gh)
  ##[error]Process completed with exit code 1.
• PR Label Check / Check PR Labels (gh)
  ##[error]This PR requires at least one topic label. Please add a topic from: https://github.com/pytorch/ao/labels?q=topic
• Run Regression Tests / test (CPU 2.3, linux.4xlarge, torch==2.3.0 --index-url https://download.pytorch.org/whl/cpu, cpu) / linux-job (gh)
  test/sparsity/test_wanda.py::TestWandaSparsifier::test_two_layer_mlp_unstructured
• Run Regression Tests / test (CPU 2.4, linux.4xlarge, torch==2.4.0 --index-url https://download.pytorch.org/whl/cpu, cpu) / linux-job (gh)
  test/sparsity/test_wanda.py::TestWandaSparsifier::test_two_layer_mlp_unstructured
• Run Regression Tests / test (CPU 2.5.1, linux.4xlarge, torch==2.5.1 --index-url https://download.pytorch.org/whl/cpu, cpu) / linux-job (gh)
  test/sparsity/test_wanda.py::TestWandaSparsifier::test_two_layer_mlp_unstructured
• Run Regression Tests / test (CPU Nightly, linux.4xlarge, --pre torch==2.6.0.dev20241101 --index-url https://download.pyt... / linux-job (gh)
  test/sparsity/test_wanda.py::TestWandaSparsifier::test_two_layer_mlp_unstructured
• Run Regression Tests / test (CUDA 2.3, linux.g5.12xlarge.nvidia.gpu, torch==2.3.0, cuda, 12.1) / linux-job (gh)
  test/sparsity/test_wanda.py::TestWandaSparsifier::test_two_layer_mlp_unstructured
• Run Regression Tests / test (CUDA 2.4, linux.g5.12xlarge.nvidia.gpu, torch==2.4.0, cuda, 12.1) / linux-job (gh)
  test/sparsity/test_wanda.py::TestWandaSparsifier::test_two_layer_mlp_unstructured
• Run Regression Tests / test (CUDA 2.5.1, linux.g5.12xlarge.nvidia.gpu, torch==2.5.1 --index-url https://download.pytorch... / linux-job (gh)
  test/sparsity/test_wanda.py::TestWandaSparsifier::test_two_layer_mlp_unstructured
• Run Regression Tests / test (CUDA Nightly, linux.g5.12xlarge.nvidia.gpu, --pre torch==2.6.0.dev20241101 --index-url http... / linux-job (gh)
  test/sparsity/test_wanda.py::TestWandaSparsifier::test_two_layer_mlp_unstructured

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

Hi @agrawal-aka!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!