Skip to content

bias-variance tradeoff #175

@Avv22

Description

@Avv22

Hello Code2Vec Team,

You mentioned in your paper Code2Vec that there are two main challenges in your work: 1) how you can decompose a program into smaller building blocks such that:

  1. large enough to be meaningful and
  2. small enough to repeat across programs.

You then defined the previous 2 points as a bias-variance tradeoff. Can you please explain this idea more?

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