Skip to content

Bug in Large Perception Thresholds in BestFit 2 #2

@rlclark23

Description

@rlclark23

A colleague is doing a paleoflood course for a university in NM this week and wanted an example dataset for the site they are visiting. She made up an NEB that was super large and went back over 8000 years. She wanted this as an example of what dataset not to use. The results were not what she (nor I) expected. I assumed that if you tell BestFit that in the past 8000 years and there is a perception threshold set to an unachievable value, it will essentially not move the curve because you are not giving it much information. That was not the case, and I can't justify why adding this PT would shift the curve this much.

I ran this in BestFit 1.0 and it did not shift the curve, essentially kept it the same which is what I expected. I then ran it through all 4 beta 2 versions, and they all produce this drastically shifted curve. I assume there is something I don’t get but thought I would bring it to your attention.

BestFIt2.4.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions