Skip to content

Reconsider how confidences are stored for an engine #937

@Enkidu93

Description

@Enkidu93

Currently, the confidences are only associated with pretranslations. This means that once a new build is run, the old pretranslations (and thus confidences) are discarded. Seeing how confidences change across time as an individual project drafts new books could be very helpful, but the current behavior would not allow this. Since we probably don't care about tracking per-verse confidences per project across time (since they will likely be drafting new books), we should consider adding some confidence stats (either overall or per book, chapter averages and maybe std dev) to the build itself. This would allow us to study confidences across time without having to keep all the past pretranslations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for Enhancement.

    Projects

    Status

    🔖 Ready

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions