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/ | GSoC: https://github.com/STEllAR-GROUP/hpx/wiki/Google-Summer-of-Code-%28GSoC%29-2020
hkaiser has joined #ste||ar
hkaiser has quit [Quit: bye]
bita has joined #ste||ar
bita has quit [Ping timeout: 260 seconds]
bobakk3r has quit [*.net *.split]
bobakk3r has joined #ste||ar
jaafar has joined #ste||ar
shahrzad has quit [Remote host closed the connection]
bita has joined #ste||ar
bita has quit [Ping timeout: 260 seconds]
Yorlik has quit [Read error: Connection reset by peer]
amspina[m] has quit [Quit: Idle for 30+ days]
hkaiser has joined #ste||ar
ct-clmsn has joined #ste||ar
ct_ has joined #ste||ar
ct-clmsn is now known as Guest61552
Guest61552 has quit [Client Quit]
<ct_> hkaiser, for distributed LDA, should that be placed into the algorithms directory in phylanx?
<ct_> hkaiser, or would a dist_algorithms directory be preferred?
<hkaiser> ct_: hmmm, so far we have kept everything in 'algorithms', even the distributed examples
parsa has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
<hkaiser> ct_: would you think we should change that?
parsa has joined #ste||ar
<ct_> hkaiser, i don't see a problem with it
<hkaiser> ok
<ct_> hkaiser, keeping things simple w/algorithms
<hkaiser> nod
<ct_> hkaiser, thanks! i'm hoping to get somewhere with this today - finally got that lda_basic branch to clear CI
<hkaiser> nice
<hkaiser> ct_: would you have a moment today to talk?
<ct_> hkaiser, yep! i was about to say, expect some pestering about setting up distributed matrices
<hkaiser> or somewhere over the weekend, but I don;t want to impose
<ct_> hkaiser, i'm at home this week so, no problem
<hkaiser> can I give you a call at around 9:30-10 (my time)?
<ct_> sure thing
<gnikunj[m]> hkaiser: is there a function that converts rank of the locality to its locality id? or a way to find locality id if I have the rank?
<hkaiser> yes
<hkaiser> hpx::naming::(detail::)locality_from_locality_id()
<hkaiser> not sure about the detail::
<hkaiser> or something along those lines, let me have a look
<gnikunj[m]> and that would be?
<gnikunj[m]> Nice, thanks!
<gnikunj[m]> What's HPX_SUPER_PURE macro btw?
<gnikunj[m]> Interesting name for a macro for sure ;-)
<gnikunj[m]> hkaiser: I've written 2 real world benchmarks for our distributed APIs. One extends the 1d_stencil_channel example in HPX and the other extends the fractal_struct example. I'm yet to benchmark them and get numbers. Let's discuss further on the call.
weilewei has joined #ste||ar
<K-ballo> "super pure" really? lol
<gnikunj[m]> K-ballo: interesting. I didn't know about its existence.
<K-ballo> super pure is [[const]]
karame_ has joined #ste||ar
nanmiao11 has joined #ste||ar
<diehlpk_work> hkaiser, Have we updated the hpx headers in the upcoming blaze release?
<diehlpk_work> In blaze 3.7, I get some deprecation warnings
<hkaiser> K-ballo: blame young Bryce for that ;-)
<hkaiser> diehlpk_work: I have not done that as it would force people to use HPX 1.5 when using blaze
<diehlpk_work> hkaiser, Ok, fine with me
<hkaiser> diehlpk_work: you can disable the warning, though
<diehlpk_work> hkaiser, Not so important, just updated the PeriHPX code to use HPX 1.5.0, since we used HPX 1.3.0
<hkaiser> nice
<K-ballo> boost 1.74.0 is out
<rori> HPX 1.5.0-rc2 is out too ;)
<hkaiser> did we test 1.5 with boost 1.74?
<hkaiser> gnikunj[m]: yes, let's chat about the examples later today
<zao> New VC++, new Boost. What could ever go wrong?
<gnikunj[m]> zao let me guess... hpx building as expected?
<zao> gnikunj[m]: I don't know, I haven't tried.
<hkaiser> rori: in any case, thanks for working on the release!
<hkaiser> rori: what's the best procedure for edits to the release notes? PRs?
<rori> hkaiser: PRs I would say yes
<rori> against the release branch
<rori> Will try boost 1.74 ;)
<K-ballo> core buids fine for boost 1.74, vs 16.7.1
<hkaiser> K-ballo: thanks
RostamLog has joined #ste||ar
shahrzad has joined #ste||ar
<hkaiser> gnikunj[m]: meeting now?
<gnikunj[m]> hkaiser: yes. joining
<hkaiser> what link do you use?
<hkaiser> ok, I have another one, but I'll join yours
<gnikunj[m]> hkaiser: would you be able to write the email for overleaf access?
<gnikunj[m]> I'm not sure what to say in the email
<hkaiser> gnikunj[m]: I can do that
<gnikunj[m]> thanks!
<parsa> gnikunj[m]: do you see an issue on the tracker? i don't see any yet
<gnikunj[m]> parsa: no don't see yet. It's late night here, probably he'll do it tomorrow morning?
<parsa> fine with me. thought we'd have it by now. didn't think of the massive timezone difference
hkaiser has quit [Ping timeout: 240 seconds]
bita has joined #ste||ar
ct_ has quit [Ping timeout: 240 seconds]
bita has quit [Ping timeout: 260 seconds]
hkaiser has joined #ste||ar
bita has joined #ste||ar
bita has quit [Ping timeout: 260 seconds]
weilewei has quit [Remote host closed the connection]