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
The "fixed-point correction" appears to be applied in a dense manner, as seen in RAFT and similar methods. However, the paper mentions that it is applied in a sparse manner. What are the differences in the results between these two approaches?
Furthermore, it seems that intermediate hidden states need to be stored to compute the fixed-point correction. However, changing the f_thres did not result in any difference in memory usage. Can you explain why this is the case?
The text was updated successfully, but these errors were encountered:
Thanks for the great work.
The "fixed-point correction" appears to be applied in a dense manner, as seen in RAFT and similar methods. However, the paper mentions that it is applied in a sparse manner. What are the differences in the results between these two approaches?
Furthermore, it seems that intermediate hidden states need to be stored to compute the fixed-point correction. However, changing the f_thres did not result in any difference in memory usage. Can you explain why this is the case?
The text was updated successfully, but these errors were encountered: