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/ | GSoC2018: https://wp.me/p4pxJf-k1
EverYoung has joined #ste||ar
diehlpk has joined #ste||ar
EverYoun_ has quit [Ping timeout: 276 seconds]
hkaiser has joined #ste||ar
EverYoung has quit [Ping timeout: 260 seconds]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
eschnett has joined #ste||ar
EverYoung has quit [Ping timeout: 240 seconds]
nikunj has joined #ste||ar
eschnett has quit [Quit: eschnett]
EverYoung has joined #ste||ar
parsa has joined #ste||ar
EverYoung has quit [Ping timeout: 240 seconds]
_gedaj_ has quit [Read error: Connection reset by peer]
__gedaj__ has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
diehlpk has quit [Remote host closed the connection]
diehlpk has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
nikunj has quit [Ping timeout: 260 seconds]
diehlpk has quit [Ping timeout: 240 seconds]
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 276 seconds]
nanashi55 has quit [Ping timeout: 264 seconds]
nanashi55 has joined #ste||ar
V|r has quit [Ping timeout: 265 seconds]
parsa has joined #ste||ar
V|r has joined #ste||ar
V|r has quit [Changing host]
V|r has joined #ste||ar
titzi has quit [Ping timeout: 265 seconds]
titzi has joined #ste||ar
parsa[[w]] has joined #ste||ar
bibek_ has joined #ste||ar
rod_ has joined #ste||ar
bibek has quit [Ping timeout: 276 seconds]
RostamLog_ has quit [Ping timeout: 265 seconds]
parsa[w] has quit [Ping timeout: 276 seconds]
RostamLog has joined #ste||ar
rtohid has quit [Ping timeout: 276 seconds]
jbjnr_ has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
jbjnr__ has quit [Ping timeout: 255 seconds]
nikunj has joined #ste||ar
jbjnr_ has quit [Quit: Leaving]
jbjnr has joined #ste||ar
__gedaj__ has quit [Read error: Connection reset by peer]
<jbjnr>
heller: because today I received a letter from the university addressed to "Dr John" and officially conferring the title on me. All the paperwork has now been completed and it is official. Took months - but it's almost over - just the cerremony left now ....
<heller>
yay!
<heller>
good for you
<jbjnr>
You're next!
<jbjnr>
have you submitted yet?
<heller>
don't want to talk about it :/
<jbjnr>
<sigh>
<jbjnr>
just submit and be done. you must have enough matreial in there already. You were 'almost' ready back in Sept!
<heller>
I still am
<heller>
just can't find the bloody time to finalize it
<jbjnr>
make time - the joy of being free is worth it.
<jbjnr>
I'm floating.
<jbjnr>
There's no weight on my shoulders .....
<jbjnr>
<flap flap flap>
<jbjnr>
:)
<heller>
/quit
<jbjnr>
lol
<jbjnr>
are you home or still swanning about the USA somewhere?
<heller>
home
<jbjnr>
job?
<heller>
university
<heller>
but yes
<zao>
$ make defense install
<heller>
rather: this = nullptr;
mcopik has quit [Ping timeout: 265 seconds]
mcopik has joined #ste||ar
eschnett has joined #ste||ar
K-ballo has joined #ste||ar
<hkaiser>
jbjnr: congrats!
<jbjnr>
thanks.
EverYoung has joined #ste||ar
<hkaiser>
jbjnr: the deadline for P1017 is next Monday
<jbjnr>
really? ok. I'd better get writing
<jbjnr>
want a chat at all?
<hkaiser>
jbjnr: sure, might be good
<jbjnr>
now? later? tomorrow?
<hkaiser>
later or tomorrow - not now
<jbjnr>
tomorrow then. Pick a time. I'm, in all day
<hkaiser>
what about 10 my time? would that be too late for you?
<hkaiser>
9:30 should work as well
<hkaiser>
that's 4:30pm
<jbjnr>
not sure what time that is for me. hold on....
<hkaiser>
4:30
EverYoung has quit [Ping timeout: 265 seconds]
<jbjnr>
that's fine. Tomorrow 16:30 my time. ok
<hkaiser>
jbjnr: ok
mcopik has quit [Ping timeout: 256 seconds]
mcopik has joined #ste||ar
hkaiser has quit [Ping timeout: 248 seconds]
hkaiser has joined #ste||ar
apsknight has joined #ste||ar
eschnett has quit [Quit: eschnett]
apsknight has left #ste||ar [#ste||ar]
aserio has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
EverYoung has joined #ste||ar
EverYoung has quit [Client Quit]
K-ballo has joined #ste||ar
aserio1 has joined #ste||ar
aserio has quit [Ping timeout: 265 seconds]
aserio1 is now known as aserio
parsa has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
eschnett has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
eschnett has quit [Client Quit]
parsa has joined #ste||ar
aserio has quit [Ping timeout: 240 seconds]
<jbjnr>
hkaiser: heller K-ballo do either of you know what changes wash is planning on making to futures in his proposal for iso c++ this june?
<K-ballo>
I have not been following closely
<K-ballo>
my impression so far is that they are still all over the place
<jbjnr>
any idea what a/the fundamental change will be?
<jbjnr>
break hpx much?
<K-ballo>
they are still discussing interface related changes
<K-ballo>
.then and such
<jbjnr>
ok, but nothing fundamental to the synchronization activity then
<K-ballo>
like what? what could that be?
aserio has joined #ste||ar
<jbjnr>
no idea, but CJ told me today that big changes were afoot from Bryce that would change futures completely. That's not to say he knows what we do in hpx or anything, but ... it got me wondering and hence my question
<K-ballo>
it's quite likely that they change the entire `future` interface in a breaking way
<K-ballo>
drop get, drop wait, redesign then, etc
<jbjnr>
chaging the api is ok, as long as they don't change what they do
<jbjnr>
drop get?
<jbjnr>
hmmm.
<jbjnr>
that might make it tricky to 'get' stuff from the future!
<K-ballo>
it can be reimplemented on top of .then
<jbjnr>
that's ok, as long as the future still passes the dat through
<jbjnr>
nobody ever calls .get except in the continuation anyway. mostly.
parsa has quit [Quit: Zzzzzzzzzzzz]
eschnett has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
diehlpk has joined #ste||ar
david_pfander has quit [Ping timeout: 276 seconds]
Anushi1998 has joined #ste||ar
__gedaj__ has quit [Remote host closed the connection]
_gedaj_ has joined #ste||ar
diehlpk has quit [Ping timeout: 264 seconds]
<K-ballo>
hkaiser: there's been advancements in packing variadics in lambdas
<parsa>
who would trigger it? it's a successful hpx build that should trigger that call back
<heller>
so, multiple options
<heller>
the prereqs for phylanx, without HPX, won't change that often. That can be easily prebuilt
<parsa>
yes
<heller>
and then you just use multiple base images, which is perfectly fine
EverYoun_ has joined #ste||ar
<parsa>
multiple base images are used to run services needed a stage. they won't merge into a single container. only the primary container is used for running commands
<parsa>
:s/stage/job
<heller>
docker-compose might be an option here
<parsa>
triggering a build of phylanx's base image inside hpx's own CI workflow is the only option
EverYoung has quit [Ping timeout: 255 seconds]
<heller>
which is a nogo, IMHO
<parsa>
that's what i though
<parsa>
t
<heller>
so let's take a step back
<heller>
what are the requirements we need for a phylanx docker image?
<heller>
1) Compile phylanx C++ applications?
<heller>
2) Run phylanx python code?
<heller>
3) Use the profiling tools?
<parsa>
the requirement for a container is that it can be used to build and test phyla
<parsa>
nx
<heller>
for circleci
<heller>
yes
<heller>
which can use multiple base containers
<parsa>
that's the one we're talking about here, i don't care for other images