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

LAGraph NONBLOCKING mode #1

Open
mcmillan03 opened this issue Mar 18, 2020 · 1 comment
Open

LAGraph NONBLOCKING mode #1

mcmillan03 opened this issue Mar 18, 2020 · 1 comment

Comments

@mcmillan03
Copy link
Member

mcmillan03 commented Mar 18, 2020

[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?

@DrTimothyAldenDavis
Copy link
Member

DrTimothyAldenDavis commented Mar 18, 2020

"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.

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