cctbx.r_free_utils
index
/net/chevy/raid1/nat/src/cctbx_project/cctbx/r_free_utils.py

 
Modules
       
random
sys

 
Functions
       
adjust_fraction(miller_array, fraction, log=None)
Expand or shrink an existing set of R-free flags to match the target
fraction.
assign_r_free_flags_by_shells(n_refl, fraction_free, n_bins)
assign_random_r_free_flags(n_refl, fraction_free, format='cns')
export_r_free_flags_for_ccp4(flags, test_flag_value)
export_r_free_flags_for_shelx(flags, test_flag_value)
extend_flags(r_free_flags, test_flag_value, array_label, complete_set=None, accumulation_callback=None, preserve_input_values=False, allow_uniform_flags=False, d_max=None, d_min=None, log=None)
# XXX if the flags don't actually need extending, the original
# values will be preserved.  I think this is a good thing, but does
# this inconsistency cause problems elsewhere?
get_r_free_as_bool(miller_array, test_flag_value=0)
get_r_free_stats(miller_array, test_flag_value)
looks_like_ccp4_flags(flags)
remediate_mismatches(array, verbose=False, log=None)
Given a set of R-free flags generated for anomalous data, detect any
mismatches between Friedel/Bijvoet mates, and move reflections to the
free set as needed to ensure consistency.

 
Data
        division = _Feature((2, 2, 0, 'alpha', 2), (3, 0, 0, 'alpha', 0), 8192)
generate_r_free_params_str = ' fraction = 0.1\n .type=float\n .shor... .short_caption = Number of resolution shells\n'