Allowing strictly inf bandwidth for gwr/mgwr #104
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR allows strictly global bandwidths (inf) in both GWR/MGWR.
Users can force the bandwidth to be inf by calling:
The result will be exactly the same to OLS's.
In bandwidth selection users can allow to try global bandwidth by setting the
bw_max = np.inf:In MGWR, users can force some of the variables to have strictly global bandwidths by setting the minimum bandwidth searching for that covariate to be
np.inf, for example.Or to allow the possibility of an inf bandwidth by setting the maximum bandwidth to be
np.inf:See this notebook for details.