<commit_before>code:
    tag version of code at submission
    trace logger with format strings for different step data etc
    min num_procs,num_cpus really needed/good?
    nomenclature: "fixed" -> "root"
    jim:
        experiment whether cts relaxation has same fxpts as discrete
        very interesting ortho idea
        switching c mid-traverse: as more roots located, update based on their span
    multisolver
        handles oddness, closed loops, and disconnected components
        oddness gets shortcut:
            closed loop -> two components
            open loop -> two traces combined into one component
    for local and multi, smarter termination criteria (e.g., time since last new fixed point >= time to last new fixed point, after many points found)
    more graceful error handling for critical directions (Baram email)
    _ prefix for private functions
    repetitions in tests with multiple W
    "performance" tests: not asserts, but how often things are within expected tolerances, good statuses, etc
    more examples
        many at https://www.sfu.ca/~ssurjano/optimization.html
            Most amenable (diffy, easy mu?):<commit_msg>new todo<commit_after>code:
    tag version of code at submission
    trace logger with format strings for different step data etc
    min num_procs,num_cpus really needed/good?
    nomenclature: "fixed" -> "root"
    jim:
        experiment whether cts relaxation has same fxpts as discrete
        very interesting ortho idea
        switching c mid-traverse: as more roots located, update based on their span
    multisolver
        handles oddness, closed loops, and disconnected components
        oddness gets shortcut:
            closed loop -> two components
            open loop -> two traces combined into one component
    for local and multi, smarter termination criteria (e.g., time since last new fixed point >= time to last new fixed point, after many points found)
    more graceful error handling for critical directions (Baram email)
    _ prefix for private functions
    repetitions in tests with multiple W
    "performance" tests: not asserts, but how often things are within expected tolerances, good statuses, etc
    more examples
        apply to multiextremal optimization RNN in malek2018multiextremal.pdf
        many at https://www.sfu.ca/~ssurjano/optimization.html
            Most amenable (diffy, easy mu?):
{'fraction_non_alphanumeric': 0.04682967260671363, 'fraction_numerical': 0.0016576875259013675, 'mean_word_length': 3.0233333333333334, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 11, 'https://': 2, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1704832', 'n_tokens_mistral': 596, 'n_tokens_neox': 578, 'n_words': 289}