Needs to reflect ORTE -> PRRTE changes.

Corresponds to openpmix/prrte#450

Reading through the book, the function set_compiler_flag doesn't result in the expected behavior.

Expected Behavior

After calling set_compiler_flag, I would expect that compiler flag to be set.

Current Behavior

The function sets a status variable to indicate that the flag is valid.

Possible Solution

Rename to check_compiler_flag or find_valid_compiler_flag

Somewhat related to #4.

Currently we have individual specification markdown documents for each module and we place them in the src/ directory.

Personally, I find that it'd be much easier to read the spec if we consolidated all the spec docs into a a single markdown file. Then we could have heading 2 for each module and heading 3 for each procedure. More importantly, if you wanted to show s

I tried using the MPIEXEC_PREFIX_DEFAULT environment variable (which is suggested on the man page) but it doesn't seem to have an effect:

> MPIEXEC_PREFIX_DEFAULT=1 mpiexec -n 2 echo "hello world"
hello world
hello world

However the -prepend-rank option (which isn't mentioned on the man page, but is mentioned under

This program is super useful! I have built it in to my git pre-commit hook so that it runs before every commit, but that means every single time I have to wait for the search index to "update" even when I haven't made any changes to the documentation.

It would be really cool to build in a functionality that the full program would only run if the documentation had changed. For instance, you co

Add more description tomorrow. See #231

The test counts should be identical across compilers, meson/cmake, and operating system.
This takes a little extra maintenance and is an ongoing task.

Description

We just switched to using Github Actions for our CI and it would be nice to add a new step that uses CMake to build the library and tests. The file can be found here:

• https://github.com/libocca/occa/blob/master/.github/workflows/build.yml

Remove (or update) requirements badge. Since to support python 2.7 we need to install older version of setuptools, it makes sense the requirements outdated but it conveys an incorrect message about the health of scikit-build

The documentation for the 'cflags' feature in the latest Boost Build docs says:

"For cflags that is both the C and C++ compilers, for cxxflags that is the C++ compiler"

but this is not reflected in the common.handle-options rule, which has 'cflags' being set for the toolset's 'compile.c' rule rather than for the toolset's 'compile' rule, while the 'compileflags' feature, which is no longer d

This showed up on the mailing list and was a problem @amneetb’s student had. We should verify that all dependencies use the same MPI implementation and fail to configure if they do not.

In biogeochem/CNCarbonStateType.F90, at line 2671, an incorrect parameter is being used to initialize C14 soil carbon variables, if starting a simulation from restart that does not include C14 variables. The parameter used is "c3_r2", but it should be "c14ratio". The c3_r2 variable is calculated for typical C13 ratios. The c14ratio is a parameer defined in main/clmvarcon.F90.

...by not overriding n or more consecutive whitespace characters. The number n (by default n=2) should be a command line option.

For discussion, see #12 and #29

At the very least opencoarrays.F90 should be documented. Test should probably be documented as well as some build system stuff etc.

Here an easy way to get going on a Windows machine if you like to work in the WSL environment.
Assuming you have installed WSL Ubuntu:

sudo apt install python3-pip
pip3 install python-config
pip3 install matplotlib
sudo apt install python3-tk

Install VcXsrv from https://sourceforge.net/projects/vcxsrv
Add "export DISPLAY=localhost:0.0" to ~/.bashrc

Restart your bash Window and it sho

For CLI having a long list of CLAs it could be helpful to section CLAs in families of CLAs, e.g. files-section, dirs-section, input-section...

Something similar to argparse groups that is different from FLAP groups that are, indeed, argparse subcommands.

Example