How to use new BPE codes and vocab to generate parallel data

Open
#69 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start with data/test_dataset and the transcoder_test_set.zip archive, then trace the Monolingual and Monolingual Functions preprocessing entry points mentioned in the questions. Compare the .tok inputs with the test.cpp_sa-java_sa.cpp_sa.pth and test.cpp_sa-java_sa.java_sa.pth files. Done means documenting the .pth contents, how the learned codes and vocabulary are used, which vocabulary trains CodeGen, and why two BPE code sets exist.

Written by the indexing model from the issue text.

Description

question

I have a few questions.

  1. I have used the data in the folder https://github.com/facebookresearch/CodeGen/tree/main/data/test_dataset learned BPE codes and vocab using Monolingual Functions mode. I want to know how to use the .tok files in the zip file https://dl.fbaipublicfiles.com/transcoder/test_set/transcoder_test_set.zip and generate files like test.cpp_sa-java_sa.cpp_sa.pth using my bpe codes and vocab?

  2. What is the contents of file test.cpp_sa-java_sa.cpp_sa.pth ? Also what is the difference between files test.cpp_sa-java_sa.cpp_sa.pth and test.cpp_sa-java_sa.java_sa.pth ?

  3. I first preprocessed data in Monolingual mode, learned BPE codes, and then did my MLM training. Then I preprocessed the data in Monolingual Functions mode and learned new BPE codes and vocab. My question is, which vocab have you used to train CodeGen? Also, why two different BPE codes are learned?

Dominant language
Python
Stars
777
Forks
144
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from facebookresearch/CodeGen

All issues in facebookresearch/CodeGen

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.