Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate statements for design point experiment #86 #163

Open
3 tasks
markwhiting opened this issue Jul 9, 2024 · 1 comment
Open
3 tasks

Generate statements for design point experiment #86 #163

markwhiting opened this issue Jul 9, 2024 · 1 comment

Comments

@markwhiting
Copy link
Member

markwhiting commented Jul 9, 2024

In the design point experiment (#86), we want to do something like the following:

  • Generate 100 candidate statements for each design point
  • Measure commonsensicality for them (presumably with some AI approach to save money (@joshnguyen99 thoughts?)
  • Select 1 for each of 15 rank buckets of commonsensicality, so we get 15 statements per design point.

It is worth doing this ad hoc, e.g., doing it for one design point before moving on to the next and even starting experiments while we do it.

This is mostly in commonsense-statements but I've added it here for now because the experiment is here.

Do we need some explicit GitHub representation of experiments? e.g., a repo for each major experiment? (@amirrr thoughts?)

@markwhiting
Copy link
Member Author

Implicit here is that the 100 candidates are unique and probably semantically unique, too. Also that they are unique compared to any of the previous statements for other design points, and that they are positioned reliably in the design space, so step 1 requires a bit more detail than just generating a bunch of statements.

To do this we should think about tooling, reproducibility and the pipeline and automation we have in place in commonsense-statements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant