Fix: Preserve model device in model_summary method

[GiuseTripodi]

Summary

The 'model_summary()' method was resetting the model device from MPS or CUDA back to CPU after calling 'torchinfo.summary()'. By adding explicitly 'device' parameter to torchinfo.summar() the model stays on its original device throughout the summary operation.

Fixes #542

Describe your changes

Modified 'model_summary()' method by adding the 'device' parameter and setting it to the current device.

Checklist before assigning a reviewer (update as needed)

• Self-review code
• Ensure submission passes current tests
• Add tests
• Update relevant docs
• Update changelog

Reviewer checklist

Please add anything you want reviewers to specifically focus/comment on.

• Everything looks ok?

[rwood-97]

Hi, the tests are failing but I think this is a problem on my side.

I will fix this in the MapReader repo and then you will need to sync the changes from MapReader into your fork and then rebase your branch using git rebase main. You can then force push to update your branch on github using git push --force.

[rwood-97]

Hi @GiuseTripodi , I have (hopefully) now fixed the tests in the main MapReader repo, can you do the steps above and then let me know when you've done it and I'll review/approve the PR.

The changelog test checks whether you've updated the changelog. You'll need to add a Fixes subheading under the pre-releases section and add this fix and link to the PR. Docs are here.

[GiuseTripodi]

Hi @rwood-97, I have done the steps above. Please let me know if there is anything else I should do.

[rwood-97]

Can you re-add the _Add new changes here_ line so future contributors can still see where to add in the changelog

[GiuseTripodi]

Sure, done it.

[rwood-97]

Great, thanks for this.

I've added one comment re keeping the _Add new changes here_ line in the changelog. Otherwise looks good to me.

I've also noted that one of the tests is still failing but I think thats a separate issue (i.e. not for you to fix in this PR). I've created an issue on the repo to track it -> #576