GraphBLAS / LAGraph-Working-Group

Public document and planning repository for the LAGraph Working Group

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

LAGraph NONBLOCKING mode

mcmillan03 opened this issue · comments

[18Mar2020] Should LAGraph return a GrB_Matrix that is deferred?

Related question: are the algorithms is composable for which the result of one is passed to another.

Is GraphBLAS execution mode orthogonal to the concerns of LAGraph?

"Should LAGraph return a GrB_Matrix that is deferred?" I would say yes, it may if it wishes too.

"Related question: are the algorithms is composable for which the result of one is passed to another." I would say yes. This is one reason why I think we need to use GrB_* objects for the parameters, as much as possible. Some algorithms might want to use int64_t or double arrays, as "int64_t *Component" where Component [i] = k if node i is in the kth component. I'm just making that up as an example, but I think we should try to avoid that.

"Is GraphBLAS execution mode orthogonal to the concerns of LAGraph?" yes. GraphBLAS is entirely opaque in this regard so LAGraph shouldn't care if it's blocking or non-blocking.