Skip to content

Deep Validation Pipeline #5

Description

@nickotto

human in the loop section. user can select a completed hypothesis and do a deep dive into it.

may be already completed with post job updates, but there should another check for hallucination, synthetic data creation, and test for knowledge graph "groundedness"

Google scholar + arxiv + pubmed search for any prior work or positive/negative result.

If there is a holdout/validation subset, the pipeline should test the models and/or statistical analyses to make sure the hypotheses tracks. Of course, any pipeline prior to this should not ever see this subset of data and should be solely for post hypothesis validation.

There should be a final interest score based on domain (how popular the subject is/# of citations), a novelty score (effectively how publishable the result is).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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