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 have a question. In the rocsparse SPSV (Sparse Solver), there are three stages, and the second stage is the analysis phase, which generates the dependency array done_array. I am trying to think about how each element in the done_array is generated outside of the code logic. I converted the sparse matrix into a DAG (Directed Acyclic Graph), and found that the number of dependencies for each row does not match the values in the done_array. So, outside of the code, what is the basis for generating the done_array array?"
The text was updated successfully, but these errors were encountered:
I have a question about the rocsparse SPSV (Sparse Solver). In the analysis phase (the second stage), a dependency array called done_array is generated. I am trying to understand how each element of this array is computed outside the code logic. I converted the sparse matrix into a Directed Acyclic Graph (DAG), but I noticed that the number of dependencies per row in the DAG does not match the corresponding values in the done_array.
From my understanding, the value for each node in done_array corresponds to the maximum path from that node to another node in the DAG that has no dependencies. Is this correct? If not, could you explain how the dependencies are defined and calculated during the analysis phase?
"I have a question. In the rocsparse SPSV (Sparse Solver), there are three stages, and the second stage is the analysis phase, which generates the dependency array done_array. I am trying to think about how each element in the done_array is generated outside of the code logic. I converted the sparse matrix into a DAG (Directed Acyclic Graph), and found that the number of dependencies for each row does not match the values in the done_array. So, outside of the code, what is the basis for generating the done_array array?"
The text was updated successfully, but these errors were encountered: