Here's a direct link to the docs: https://bears-r-us.github.io/arkouda/
You can also find the link in the README.md :thumbsup:
You can also find the link in the README.md :thumbsup:
Happy Holidays!
Today's Arkouda weekly call @bmcdonald3 will talk about his PR #1034 to refactor the binary operators
For the latest Arkouda version. I have the following error
/home/z/zd4/Mike/arkouda//dep/checkRE2.chpl:3: In function 'main':
/home/z/zd4/Mike/arkouda//dep/checkRE2.chpl:9: error: Cannot find module or enum 'Regex'
make: * [check-re2] Error 1
I have installed regex using conda.
How to fix this checking problem?
export CHPL_RE2=bundled
It seems I missed something else?
I need to
make clean
first?
make clean
first?
Must I build it from clean? If I rebuild the chapel, it will need a long time.
What version of Chapel are you using? (
chpl --version)
I have make clean and make
make “ARKOUDA_SKIP_CHECK_DEPS=true from the arkouda directory.
We’ve recently been talking about what could be done to make uses get processed more lazily (or other things to be processed more aggressively) so that the code would’ve worked as you’d hoped. But that’s a ways off yet, I’m afraid.
@pierce314159 : I added a comment to #1032 here: https://github.com/Bears-R-Us/arkouda/pull/1032/files#r802103781 but probably it deserves an issue to make sure it doesn’t get lost. Can you take care of that?
@zhihuidu, the issue you were having should be resolved by Bears-R-Us/arkouda#1084. You should be able to make without skipping checks on the latest version of arkouda master
Hi @zhihuidu — Sorry not to have noticed this earlier. I believe that you're correct that, today by default, Chapel processes assume they own the full compute node, and so will (for example) create a thread per core and pin those threads to the cores. When both processes do this, it can hurt performance of course.
There are some advanced features that can be used to try and carve up a compute node (like a shared memory system like this) between multiple Chapel processes, and we've had some success with them, but it's still not optimal.
I expect that we'll be doing more here to support a user-facing "locales per node" setting that will cause the processes to be more aware of each other and cooperate better, but that doesn't exist today.
As far as best practices for the advanced features I refer to above, Elliot Ronaghan (@ronawho on gitter) is the resident expert. I think he was giving tips on this to others at Arkouda recently, let me see if I can find them.