2020 HPX community survey

With the new decade we want to get to know our community better. We already interact with many of you on IRC, GitHub, the mailing list, and other places, but the interactions tend to be about very specific problems. We want to hear from all of you, all the way from those who found it too difficult to start with HPX to those who have contributed several times. We want to hear what you love about HPX and what you hate about it. We want to hear about your smallest annoyances and problems that may take 5 years to solve. Anything goes. It’s only with your help that we can make HPX into a truly useful tool.

Please take a few minutes to fill in the survey over here. We’ll collect responses for about a month and then we’ll publish the results here.

HPX 1.4.0 Released!

The STE||AR Group is proud to announce the release of HPX 1.4.0. This is a big release! We’ve added numerous new features, continued work on modularizing and making HPX lighter, and all-round improved usability, stability, and performance. Thank you once again to everyone in the STE||AR Group and all the volunteers who have provided fixes, opened issues, and improved documentation.

Download the release from our release page. Please note that we will not be providing downloads from stellar-group.org or stellar.cct.lsu.edu anymore.

New Year, New Journeys

STE||AR Team:

Over the past six years I have had the pleasure of working with all of you wrangling teams, editing papers, writing grants, and just helping out wherever I can. However, as of December 31st, I will no longer be performing the role of program coordinator at LSU, and starting in January, I will be leaving the LSU community to take a position at AMD in Austin, Texas. This move is bittersweet for me. While the prospect of moving to a new city and facing new challenges is exciting, I am leaving a group of people I have grown very close to over the past half-decade.

I feel so privileged to have been able to work with and learn from the talented, knowledgeable, and skillful people who make up the STE||AR team. I really believe that Hartmut has created something special, a community of people who truly care about each other brought together by a vision of how C++ and HPC could be. I am confident that the future is bright for HPX and for all of us lucky people who have had the good fortune to engage with it.

Until we see each other again, happy hacking!

Adrian S. Lemoine

GSoD Final Report

By Rebecca Stobaugh.

We’ve reached the end of Google’s Season of Docs, and we’ve accomplished a lot in the past three months. My initial proposal was to work on three sections of the manual, and we have far exceeded our goal, managing to make changes to twelve different sections of the documentation. The majority of the work I’ve done has consisted of cleaning up grammatical errors and improving sentence structure. I have also added a style guide to the wiki, which should help standardize future changes to the documentation. The style guide can be found in the “HPX Source Code Structure and Coding Standards” wiki document under the section “Documentation Style Guide”. For a complete list of my pull requests during Season of Docs, please see here. To view my changes to the wiki, please see here.

Announcing HPX’s Season of Docs

By Rebecca Stobaugh

HPX was recently selected to be part of Google’s Season of Docs (GSoD), a program designed to improve the documentation of open source software. While the STE||AR Group has created extensive documentation for HPX, this documentation has been written by several different people, which has led to some inconsistencies and awkward organization. I am a technical writer and English PhD student who has been selected to edit and streamline HPX’s documentation. My goal is to clean up the content, concentrating on both grammatical issues and design concerns, to create a more cohesive, user-friendly product. My primary focus will be on two sections of the STE||AR Group’s instruction manual: “HPX Build System” and “Launching and Configuring HPX Applications.” If time allows, I will also revise the “Why HPX” page, with an emphasis on condensing and trimming repetitive content.

You can read my GSoD proposal here.

Trip Report: ICML 2019


By: Bita Hasheminezhad

A few weeks ago, I had the opportunity to attend the International Conference on Machine Learning (ICML) which is the premier gathering of professionals dedicated to the advancement of machine learning. Thirty-Sixth ICML was held on June 9th to 15th at the Long Beach Convention Center.

HPX 1.3.0 Released!

The STE||AR Group is proud to announce the release of HPX 1.3.0! This release focuses on performance and stability improvements. Make sure to read the full release notes to see all new and breaking changes. Thank you once again to everyone in the STE||AR Group and all the volunteers who have provided fixes, opened issues, and improved documentation.

Download the release from our download page, or GitHub page.

HPX accepted for Google Season of Docs 2019

This year Google is organizing for the first time Google Season of Docs (GSoD). Like Google Summer of Code (GSoC) the program aims to match motivated people with interesting open source projects that are looking for volunteer contributions. GSoD, however, aims to improve open source project documentation, which often tends to get less attention than the code itself. We recognize this all too well in the HPX project. For this reason, we decided to apply for GSoD and can now proudly announce that HPX has been selected as one of 50 projects participating in this year’s GSoD!

This means that we are now looking for motivated people to help us improve our documentation. If you have some prior experience with technical writing, and are interested in working together with us on making the documentation of a cutting edge open source C++ library the best possible guide for new and experienced users, this is your chance. You can read more about the program on the official GSoD home page. We’ve provided a few project ideas on our wiki, but you can also come up with your own. Our current documentation can be found here.

The deadline for technical writer applications is June 28. Come talk to us about your ideas and your application on our mailing list, IRC, or Slack. We’d love to hear from you!