Remove Usage Of npro In Favor Of Just numpyro

[AFg6K7h4fhy2]

There is, in some instances, the use of import numpyro as npro. This has not been a uniform behavior though, despite this syntax being more preferable to MSR developers than import numpyro. This PR changes all instances of import numpyro to import numpyro as npro and modifies the code correspondingly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.80%. Comparing base (4ea2e4b) to head (4777b58).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #316   +/-   ##
=======================================
  Coverage   92.80%   92.80%           
=======================================
  Files          39       39           
  Lines         904      904           
=======================================
  Hits          839      839           
  Misses         65       65           

Flag	Coverage Δ
unittests	92.80% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[damonbayer]

Thanks for working on this, @AFg6K7h4fhy2! Unfortunately, the current PR does the exact opposite of what I was hoping for. I would like to standardize on import numpyro.

[AFg6K7h4fhy2]

Thanks for working on this, @AFg6K7h4fhy2! Unfortunately, the current PR does the exact opposite of what I was hoping for. I would like to standardize on import numpyro.

Oof. That's kind of funny. My apologies, I do not know how I misread the issue title. I will fix once I finish up some more on #300

[AFg6K7h4fhy2]

@damonbayer Changes have been made appropriately.

[dylanhmorris]

@AFg6K7h4fhy2 can you merge in main now that #317 has landed? Will review once that's done.

[damonbayer]

Thanks @AFg6K7h4fhy2!

[damonbayer]

Rejecting my previous review. See @dylanhmorris's comment regarding #317. #316 (comment)