New upper bound for inter1d objects #205
                
     Open
            
            
          
      
        
          +10
        
        
          −8
        
        
          
        
      
    
  
  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.
  
    
  
    
After reproducing nextstrain/augur#1032 @corneliusroemer and I found that the issue was during
_ml_t_joint. An internal node was suggested time points that were out of bounds of pre-calculated interpolation objects (integral_merger_rate,total_merger_rate). These time points were obtained frommsgs_to_multiplyand were outside of the x -axis upper bound for the interpolation objects. The upper bound of the interpolation objectsintegral_merger_rateandtotal_merger_ratewas predefined usingttconf.BIG_NUMBER.To avoid further out of bounds errors we introduced a new constant value
BIGGEST_NUMBER = sys.float_info.maxto use as an upper bound for the interpolation objects. We don't think that altering this range will have any numerical impact but please let us know if we have overlooked something @rneher.Resolves nextstrain/augur#1032