hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
jbjnr_ has quit [Ping timeout: 264 seconds]
eschnett_ has quit [Quit: eschnett_]
Malvolio has left #ste||ar [#ste||ar]
K-ballo has quit [Quit: K-ballo]
hkaiser has quit [Quit: bye]
Abhishek09 has joined #ste||ar
<Abhishek09>
diehlpk_works:I have found blaze on two places
<Abhishek09>
can i use github one:
<Abhishek09>
is anyone here?
Abhishek09 has quit [Quit: Page closed]
Yorlik has quit [Excess Flood]
Abhishek09 has joined #ste||ar
<Abhishek09>
parsa:can i install blaze through yum.
<zao>
Abhishek09: do they appear to be the same project?
<zao>
If so, find out which one is authorative. If not, find out which one is the right one.
<Abhishek09>
i have to install blaze as dependency:
<zao>
I recommend being a bit more self-supporting and trying/figuring things out. It’s an aspect that is encouraged in SoC as you’re the one that has to do the work in the end.
<zao>
Regardless of which library you end up using and how you install it, you ought to be able to come up with a plan for how to achieve the goal.
<zao>
You could even do some exploratory tests with simpler libraries and Python projects if Phylanx is too huge to start with, to build experience.
<zao>
So did you manage to build Phylanx standalone in any way, ignoring the whole pip thing?
<zao>
A tip by the way, I recommend installing into some private location instead of globally in /usr/local, as it’s easy to permanently affect your system.
<zao>
I’m off for some ice fishing... good luck!
Abhishek09 has quit [Quit: Page closed]
K-ballo has joined #ste||ar
Yorlik has joined #ste||ar
Abhishek09 has joined #ste||ar
Abhishek09 has quit [Ping timeout: 256 seconds]
Abhishek09 has joined #ste||ar
hkaiser has joined #ste||ar
Abhishek09 has quit [Ping timeout: 256 seconds]
<Amy1>
how to get real time memory bandwitdth used?
Abhishek09 has joined #ste||ar
<Abhishek09>
deihlpk_work:is appveyor is support by fedora?
nikunj has joined #ste||ar
<K-ballo>
Abhishek09: what do you think appveyor is?
<Abhishek09>
AppVeyor is a hosted, distributed continuous integration service used to build and test projects hosted on GitHub and other source code hosting services (including GitLab and Bitbucket.org)
<K-ballo>
that sounds a lot more like what wikipedia thinks...
<K-ballo>
so, considering that, what would it mean for fedora to support it?
<Abhishek09>
To build wheels
<K-ballo>
who would build the wheels?
<Abhishek09>
Appveyer
<K-ballo>
why don't you look into it?
Abhishek09 has quit [Ping timeout: 256 seconds]
Abhishek09 has joined #ste||ar
Abhishek09 has quit [Ping timeout: 256 seconds]
Abhishek09 has joined #ste||ar
Abhishek09 has quit [Quit: Page closed]
parsa is now known as parsa_
jaafar_ has quit [Ping timeout: 264 seconds]
Yorlik has quit [Disconnected by services]
Yorlik has joined #ste||ar
eschnett has joined #ste||ar
nikunj has quit [Quit: Leaving]
<K-ballo>
no executors for 20 then?
nikunj has joined #ste||ar
<hkaiser>
K-ballo: design by committee, what do you expect?