Manual: Updates for 0.4.0 #2685
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ax3l
commented
Aug 11, 2018
INSTALL.rst
Outdated
| @@ -89,13 +89,16 @@ zlib | |||
|
|
|||
| boost | |||
| """"" | |||
| - 1.62.0-1.64.0 (``program_options``, ``regex`` , ``filesystem``, ``system``, ``math``, ``serialization`` and header-only libs, optional: ``fiber`` with ``context``, ``thread``, ``chrono``, ``atomic``, ``date_time``) | |||
| - download from `http://www.boost.org <http://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download>`_ | |||
| - 1.62.0 - 1.68.0 (``program_options``, ``regex`` , ``filesystem``, ``system``, ``math``, ``serialization`` and header-only libs, optional: ``fiber`` with ``context``, ``thread``, ``chrono``, ``atomic``, ``date_time``) | |||
There was a problem hiding this comment.
Help wanted: we should verify that boost 1.67.0 and 1.68.0 work for us, especially with nvcc
There was a problem hiding this comment.
1.67.0 seems to be working, 1.68.0 is problematic (see alpaka link below)
ax3l
force-pushed
the
doc-usageUpdates040
branch
from
618a914 to
a53810b
Compare
ax3l
commented
Aug 11, 2018
| @@ -3,15 +3,29 @@ | |||
| TBG | |||
| === | |||
|
|
|||
| .. sectionauthor:: Axel Huebl, Richard Pausch | |||
There was a problem hiding this comment.
Moved below to shared section.
Will potential move to new page in the future.
ax3l
force-pushed
the
doc-usageUpdates040
branch
from
a53810b to
6c1892f
Compare
PrometheusPi
approved these changes
Aug 11, 2018
USAGE.rst
Outdated
|
|
||
| pic-create | ||
| """""""""" | ||
|
|
||
| This tool is just a short-hand to create a new set of input files. | ||
| It does a copy from an already existing set of input files (e.g. our examples or a previous simulation) and adds additional default files. | ||
| It does a copy from an already existing set of input files (e.g. our examples or a previous simulation) and adds additional helper files. |
There was a problem hiding this comment.
optional:
better wording:
It copies from an already ...
docs/source/usage/tbg.rst
Outdated
|
|
||
| We abstract the description of queues, resource acquisition and job submission away from PIConGPU user input via *template files* (``.tpl``). | ||
| For example, the ``.cfg`` file defines how many *devices* shall be used for computation, but the ``.tpl`` file calculates how many *physical nodes* will be requested. | ||
| Also, the ``.tpl`` file takes care off how to spawn a process when scheduled, e.g. with ``mpiexec`` and which flags for networking details need to be passed. |
PrometheusPi
previously requested changes
Aug 11, 2018
|
Cross-link: Alpaka Boost 1.68.0 support status https://github.com/ComputationalRadiationPhysics/alpaka/pull/606 |
sbastrakov
reviewed
Aug 13, 2018
docs/source/usage/tbg.rst
Outdated
| An unfortunate aspect about batch systems from a user's perspective is, that their usage varies a lot. | ||
| And naturally, different systems have different resources in queues that need to be described. | ||
|
|
||
| We abstract the description of queues, resource acquisition and job submission away from PIConGPU user input via *template files* (``.tpl``). |
There was a problem hiding this comment.
I feel it's a little imprecise: queues, resource acquisition and job submission are not part of PIConGPU user input per se (at least queues are not), but part of a launch command line. Maybe just remove words from PIConGPU user input ?
sbastrakov
reviewed
Aug 13, 2018
docs/source/usage/tbg.rst
Outdated
| And naturally, different systems have different resources in queues that need to be described. | ||
|
|
||
| We abstract the description of queues, resource acquisition and job submission away from PIConGPU user input via *template files* (``.tpl``). | ||
| For example, the ``.cfg`` file defines how many *devices* shall be used for computation, but the ``.tpl`` file calculates how many *physical nodes* will be requested. |
There was a problem hiding this comment.
I think here the .cfg file is rather unnatural, we are talking in general about a configuration file, right? There are also other cases I'm not sure about, but this one jars on my ears.
sbastrakov
reviewed
Aug 13, 2018
docs/source/usage/tbg.rst
Outdated
| For example, the ``.cfg`` file defines how many *devices* shall be used for computation, but the ``.tpl`` file calculates how many *physical nodes* will be requested. | ||
| PIConGPU runtime options are described in *configuration files* (``.cfg``). | ||
| We abstract the description of queues, resource acquisition and job submission via *template files* (``.tpl``). | ||
| For example, a ``.cfg`` file defines how many *devices* shall be used for computation, but a ``.tpl`` file calculates how many *physical nodes* will be requested. | ||
| Also, the ``.tpl`` file takes care of how to spawn a process when scheduled, e.g. with ``mpiexec`` and which flags for networking details need to be passed. |
There was a problem hiding this comment.
Sorry, did not mark it last time. Here it also has to be a tpl file.
Fix outdated .cfg file names. Improve clarity and structure.
Refresh version ranges, update min. alpaka, add notes, replace wget with more widespread curl command, remove untar verbosity.
Thx for the review @PrometheusPi
Thx for the review @sbastrakov
We can probably add work-arounds later to PMacc and Alpaka. But right now, it's not usable with NVCC.
ax3l
force-pushed
the
doc-usageUpdates040
branch
from
3df463a to
5288bc2
Compare
PrometheusPi
approved these changes
Aug 13, 2018
|
@PrometheusPi ping :) |
psychocoderHPC
added a commit
to psychocoderHPC/picongpu
that referenced
this pull request
Oct 4, 2018
Boost 1.68.0 is not allowed since ComputationalRadiationPhysics#2685 but after we will integrate the next alapak release we will end in compile issues. The reason is ComputationalRadiationPhysics#2707. The definition of `boost::math::gcd` is not available if `boost/integer/common_factor_rt.hpp` is included. This PR fixes the behaviour be using always `boost/integer/common_factor_rt.hpp` and use `boost::integer::gcd` within PMacc.
2 tasks
ax3l
pushed a commit
to ax3l/picongpu
that referenced
this pull request
Oct 5, 2018
Boost 1.68.0 is not allowed since ComputationalRadiationPhysics#2685 but after we will integrate the next alapak release we will end in compile issues. The reason is ComputationalRadiationPhysics#2707. The definition of `boost::math::gcd` is not available if `boost/integer/common_factor_rt.hpp` is included. This PR fixes the behaviour be using always `boost/integer/common_factor_rt.hpp` and use `boost::integer::gcd` within PMacc.
steindev
pushed a commit
to steindev/picongpu
that referenced
this pull request
Oct 16, 2018
Boost 1.68.0 is not allowed since ComputationalRadiationPhysics#2685 but after we will integrate the next alapak release we will end in compile issues. The reason is ComputationalRadiationPhysics#2707. The definition of `boost::math::gcd` is not available if `boost/integer/common_factor_rt.hpp` is included. This PR fixes the behaviour be using always `boost/integer/common_factor_rt.hpp` and use `boost::integer::gcd` within PMacc.
steindev
pushed a commit
to steindev/picongpu
that referenced
this pull request
Oct 16, 2018
Boost 1.68.0 is not allowed since ComputationalRadiationPhysics#2685 but after we will integrate the next alapak release we will end in compile issues. The reason is ComputationalRadiationPhysics#2707. The definition of `boost::math::gcd` is not available if `boost/integer/common_factor_rt.hpp` is included. This PR fixes the behaviour be using always `boost/integer/common_factor_rt.hpp` and use `boost::integer::gcd` within PMacc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tbgsectionGreetings from Toronto Airport!