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
nikunj97 has quit [Read error: Connection reset by peer]
hkaiser has quit [Quit: bye]
kale[m] has quit [Ping timeout: 244 seconds]
kale[m] has joined #ste||ar
weilewei has quit [Ping timeout: 245 seconds]
bita_ has quit [Ping timeout: 240 seconds]
Yorlik has quit [Ping timeout: 246 seconds]
nanmiao11 has quit [Ping timeout: 245 seconds]
nikunj has quit [Ping timeout: 256 seconds]
nikunj has joined #ste||ar
kale[m] has quit [Ping timeout: 244 seconds]
kale[m] has joined #ste||ar
linus2 has quit [Ping timeout: 260 seconds]
linus2 has joined #ste||ar
nikunj97 has joined #ste||ar
kale[m] has quit [Ping timeout: 260 seconds]
kale[m] has joined #ste||ar
Nikunj__ has joined #ste||ar
nikunj97 has quit [Ping timeout: 244 seconds]
nikunj97 has joined #ste||ar
Nikunj__ has quit [Ping timeout: 244 seconds]
<gonidelis[m]> Could someone explain how /docs work on hpx?
<gonidelis[m]> in general
<gonidelis[m]> I mean how do we compose docs
<gonidelis[m]> and how do we compile them
<gonidelis[m]> I can see that the tool we are using is called sphinx
<zao> The format is restructuredtext, which is like Markdown but weird :D
<zao> Also doxygen.
<gonidelis[m]> Since I write some .rst file how do we compile that?
<zao> If you squint at the top-level CMakeLists.txt, you'll find `HPX_WITH_DOCUMENTATION`, and if you squint at the CMakeLists.txt in the docs/ dir, there's a `docs` target.
<gonidelis[m]> So what's the difference between doxygen and sphinx
<gonidelis[m]> Are they doing the same job?
<zao> Sphinx generates a book-like website with an index and separate pages and stuff.
<zao> Doxygen generates automatic documentation from source code doc-comments.
<zao> The doxygen output is weaved together with the manually authored content from the .rst files.
<zao> If you've looked at the reference sections of the docs for all the contents of headers and function documentation, that's from Doxygen.
<gonidelis[m]> reference sections of the docs?
<gonidelis[m]> oh okk..
<gonidelis[m]> How do we compile sphinx and how do we compile doxygen?
<ms[m]> freenode_gonidelis[m]: essentially you'll need to set `HPX_WITH_DOCUMENTATION=ON` and have the prerequisites for building the documentation, meaning doxygen and a few python packages
<ms[m]> if you'd like to try it the easiest might be to use the docker image we use on circleci since it already has all the dependencies (stellargroup/build_env:ubuntu on docker hub)
<ms[m]> after that make docs first processes the source files with doxygen, and then builds the rst files and incorporates the doxygen output
<ms[m]> i.e. what zao said... this is all done automatically by make docs (although it's not always correctly rebuilt if you change files...)
<zao> gonidelis[m]: You have those tools installed externally.
hkaiser has joined #ste||ar
weilewei has joined #ste||ar
nikunj97 has quit [Ping timeout: 246 seconds]
akheir has joined #ste||ar
diehlpk__ has joined #ste||ar
nanmiao11 has joined #ste||ar
Yorlik has joined #ste||ar
karame_ has joined #ste||ar
nikunj has quit [Ping timeout: 244 seconds]
<gonidelis[m]> `HPX_WITH_DOCUMENTATION=ON` goes when I `cmake` at my build?
<hkaiser> gonidelis[m]: what do you mean?
<gonidelis[m]> hkaiser: Sorry. That was a late response to ms[m] 's latest message
<gonidelis[m]> on how to compile the docs
<rori> yes
<rori> it's a cmake option
<gonidelis[m]> So bottom line: When I want to provide documentation for some of my work I go the according `/docs/.....` dir or make some doxygen comments on my source and then I check my changes with the cmake option above?
<gonidelis[m]> hkaiser: I think that as we are closing the first period I should provide some documentation for my work thus far. (`for_each` is almost complete and all the traits that I have implemented, too)
<hkaiser> gonidelis[m]: ms[m] knows what you need to do to generate the docs
<gonidelis[m]> extra question: How do I make the changes visible here? https://hpx-docs.stellar-group.org/latest/html/index.html
<rori> yes! the cmake option + `make docs`
<hkaiser> that page shows the docs on master
<hkaiser> rori: but he needs to install some additional tools, no?
<gonidelis[m]> ok so whenever a doc PR merges with master, it should be visible here ?
nikunj has joined #ste||ar
<hkaiser> yes
<gonidelis[m]> doxygen and a few python packages
<hkaiser> after the tests have cycled
<rori> yep doxygen and sphinx I believe, maybe other dependent python packages
<gonidelis[m]> rori_[m]: So do I use `pip3` for these packages?
nikunj has quit [Read error: Connection reset by peer]
<gonidelis[m]> also hkaiser what do you believe on the documentation related to my work thus far?
<rori> freenode_gonidelis[m]: yes you can
nikunj has joined #ste||ar
<gonidelis[m]> rori_[m]: great... thank you! I 'll give it a try...
<hkaiser> gonidelis[m]: not sure what you're asking
<rori> you can use sphinx-autobuild (installed with pip too) to view the changes to the docs locally or pandoc if you just need to check that the syntax is fine (can convert .rst to .html)
<gonidelis[m]> hkaiser: Well when I was conducting my GSoC proposal, you asked me to devote some time for documenting. So, I am asking wether it is good to provide documentation for the traits that I have implemented so far in the first period: `is_sentinel_for`, `sized_sentinel_for` and `distance.hpp`
<gonidelis[m]> rori_[m]: Was about to ask that. Thanks a lot!
nikunj has quit [Ping timeout: 260 seconds]
<hkaiser> gonidelis[m]: I don't think those facilities will be exposed to HPX users, so it might not be necessary to create formal docs. some comments in the code might be sufficient
<gonidelis[m]> ahhh... great. Yeah you are right
<gonidelis[m]> So, I shall worry about docs as soon as I deliver the adapted `for_each`, shouldn't I?
<hkaiser> yes
nikunj has joined #ste||ar
<gonidelis[m]> hkaiser: Thanks!
<hkaiser> for_each already has doxygen comments, you'd need to adapt those
<gonidelis[m]> Yup... right on
<hkaiser> gonidelis[m]: in the end we should get to a point that our algorithms are conforming to the standard
<hkaiser> that means we need to have things in hpx::ranges in addition to the ones in hpx::
<hkaiser> but that a more involved discussion
nikunj has quit [Read error: Connection reset by peer]
<gonidelis[m]> hmmm... ok. We shall discuss that on Friday then?
nikunj has joined #ste||ar
<hkaiser> k
nikunj has quit [Ping timeout: 244 seconds]
nikunj has joined #ste||ar
bita_ has joined #ste||ar
kale[m] has quit [Ping timeout: 256 seconds]
kale[m] has joined #ste||ar
nikunj97 has joined #ste||ar
kale[m] has quit [Ping timeout: 240 seconds]
kale[m] has joined #ste||ar
<weilewei> For HDF5 in Piz Daint, have anyone experience such error: terminate called after throwing an instance of 'H5::FileIException' ?
<weilewei> or any suggestion how to resolve it? I can compile it successfully, and run my application, but once it arrives hdf5 write out part, it fails at this place
<weilewei> Or is there any Piz Daint user-group chat I can ask questions around?
<weilewei> ms[m] rori jbjnr maybe have some insights? Thanks
nikunj has quit [Read error: Connection reset by peer]
nikunj has joined #ste||ar
<hkaiser> weilewei: file not found?
<weilewei> But the hdf5 file will not exist until dca tries to write out an file
<weilewei> hkaiser
<rori> no idea ms and jbjnr would probably know more than me
<hkaiser> weilewei: access rights?
<hkaiser> non-existing target directory?
<weilewei> hkaiser hmm, not sure about if I have access right, I simply salloc a debug node, and then srun main_dca input.json in the same directory
<diehlpk_work> kale[m], Have you sent your information for the blog post yet?
<weilewei> and I ask for writing out hdf5 file in the same directory
<diehlpk_work> Note that you are three days late!
<diehlpk_work> nikunj, parsa Please poke kale[m] to deliver
<nikunj> diehlpk_work: on it
<nikunj> diehlpk_work: wasn't it due this week?
<diehlpk_work> No, last Friday
<nikunj> We asked him to deliver this week by Friday
<nikunj> Aah that's why
<nikunj> I'll ask him to get it delivered. Apologies for the misunderstanding.
<nikunj> We're very close to having a working wheel (linux) with all dependencies in place
<diehlpk_work> nikunj, Cool
<nikunj> We have some troubles with linking to static libraries. If that's resolved, we'll have a working wheel. We'll focus on CI integration within phylanx next.
<kale[m]> diehlpk_mobile[m: We had a misunderstanding on our part about the time I need to submit a blog.
<kale[m]> I'll write one before Friday
nanmiao11 has quit [Remote host closed the connection]
nanmiao11 has joined #ste||ar
<weilewei> hkaiser I can see the hdf5 is created, but with zero bits... and it has -rw-r--r--
<weilewei> hkaiser I ran unit test, and it does complain about file accessbility: https://gist.github.com/weilewei/264e174be5c156684e53a0b04a15f24f
nikunj has quit [Ping timeout: 244 seconds]
nikunj has joined #ste||ar
<weilewei> hkaiser oh yea, after export HDF5_USE_FILE_LOCKING=FALSE, it writes out file successfully, thanks!
<zao> nikunj: Ooh, progress on the wheely thing?
<nikunj> zao: a good amount, I must say ;-)
diehlpk__ has quit [Ping timeout: 244 seconds]
kale[m] has quit [Ping timeout: 264 seconds]
kale[m] has joined #ste||ar
karame_ has quit [Remote host closed the connection]
karame_ has joined #ste||ar
kale[m] has quit [Ping timeout: 256 seconds]
kale[m] has joined #ste||ar
weilewei has quit [Remote host closed the connection]
nanmiao11 has quit [Remote host closed the connection]
weilewei has joined #ste||ar
Nikunj__ has joined #ste||ar
nikunj97 has quit [Ping timeout: 272 seconds]
nikunj97 has joined #ste||ar
Nikunj__ has quit [Ping timeout: 246 seconds]
Nikunj__ has joined #ste||ar
nikunj97 has quit [Ping timeout: 272 seconds]
nikunj97 has joined #ste||ar
Nikunj__ has quit [Ping timeout: 264 seconds]
kale[m] has quit [Ping timeout: 265 seconds]
kale[m] has joined #ste||ar
kale[m] has quit [Ping timeout: 246 seconds]
kale[m] has joined #ste||ar
<nikunj97> hkaiser, yt?
<hkaiser> nikunj97: here
<nikunj> hkaiser: see pm please
kale[m] has quit [Ping timeout: 244 seconds]
kale[m] has joined #ste||ar
nikunj97 has quit [Read error: Connection reset by peer]
diehlpk__ has joined #ste||ar