Closed neelakausik closed 1 year ago
I think I've made my last round of comments. Once you've addressed them, then we can do some more testing/profiling.
Could you add a pull request description at the top?
Also, care builds some internal tests (see care/test/ folder ). Do you think any tests are needed? Or would it be difficult to add unit tests for this type of feature?
Also, care builds some internal tests (see care/test/ folder ). Do you think any tests are needed? Or would it be difficult to add unit tests for this type of feature?
Testing this would require specialized infrastructure that we don't have. Since this is for debugging and profiling, I don't think it's worth trying to put in special infrastructure.
Could you add a pull request description at the top?
I expanded on Neela's description. Let me know if it's not clear.
Also, care builds some internal tests (see care/test/ folder ). Do you think any tests are needed? Or would it be difficult to add unit tests for this type of feature?
Testing this would require specialized infrastructure that we don't have. Since this is for debugging and profiling, I don't think it's worth trying to put in special infrastructure.
That's fine, no problem then.
Could you add a pull request description at the top?
I expanded on Neela's description. Let me know if it's not clear.
Thanks, that works for me.
Thanks for your work!
I think that all my comments were addressed except for the alias for the strange map "using ActionMap = std::unordered_map<void , std::function<void(chai::ExecutionSpace, const char , int)>>". Either make the change or tell me if you ultimately decided not to do that, and then I'll approve
CARE had custom infrastructure for doing things before and after RAJA loops. This branch moves debug and profile related code into actual RAJA plugins and makes both plugins optional. It also introduces a requirement to use CHAI's RAJA plugin to make sure data is moved to the correct execution space.