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

The message selection issue #4

Open
Dy1anT opened this issue Feb 28, 2024 · 1 comment
Open

The message selection issue #4

Dy1anT opened this issue Feb 28, 2024 · 1 comment

Comments

@Dy1anT
Copy link

Dy1anT commented Feb 28, 2024

I have a question: why is a list of messages used in the code, and then the following code is used in the WmProcessorMessageModel to select one of these messages? What is the significance of doing so?

cur_message = self.message[message_len // self.encode_len]
@leanwang326
Copy link
Collaborator

if the message is long, we split it into several parts and encode each independently. For example, if we have 100 bits to encode, we may turn it into a list of five 20-bit parts and encode each into 200 tokens. This is because directly encoding and decoding a single message with too-many bits is too computation-expensive.

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

2 participants