You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m currently working on fitting large tables into encoder models. To achieve this, I flatten the table into a text and calculate self-attention across the entire text. However, for very large tables, this approach becomes infeasible due to memory and computational constraints.
To address this, I aim to constrain the attention to specific parts of the table, such as tokens within the same row or column. My idea is to use a custom attention mask that limits interactions to these regions, reducing the complexity.
Given that Attention Gym supports optimized attention implementations with efficient memory usage and time-saving mechanisms, I was wondering:
• Do you think a mask of this nature (row- or column-constrained attention) could benefit from your implementation?
• Is it a problem if mask are different for every tables?
Thank you in advance !
The text was updated successfully, but these errors were encountered:
Hello,
I’m currently working on fitting large tables into encoder models. To achieve this, I flatten the table into a text and calculate self-attention across the entire text. However, for very large tables, this approach becomes infeasible due to memory and computational constraints.
To address this, I aim to constrain the attention to specific parts of the table, such as tokens within the same row or column. My idea is to use a custom attention mask that limits interactions to these regions, reducing the complexity.
Given that Attention Gym supports optimized attention implementations with efficient memory usage and time-saving mechanisms, I was wondering:
• Do you think a mask of this nature (row- or column-constrained attention) could benefit from your implementation?
• Is it a problem if mask are different for every tables?
Thank you in advance !
The text was updated successfully, but these errors were encountered: