Example scripts contains some dependencies not listed for Horovod, and in some cases require datasets without explaining how to obtain them. We should provide a README file along with a set of packages (requirements.txt) for successfully running the examples.

Needs to reflect ORTE -> PRRTE changes.

Corresponds to openpmix/prrte#450

The problem is as follows:

Given an optimization model part which contains elements. Gid is specified as output format. If the elements of the optimization model part are not initialized (which may happen e.g. when no internal analyzer is defined), then the function GiDOutputProcess::ExecuteBeforeSolutionLoop will produce a seg-fault when it calls

`__initialize_results --> gid_io.h line 6

I see that here on SourceForge, there are all Documentations in PDF format archived in single downloadable files. However the source is not provided. Did you use LaTeX or any other MarkUp languages to generate these PDFs? I would appreciate if you could do either of these

• add a Documentation folder on [this repository](

Describe the bug

Providing NULL to the send callback of ucp_put_nb leads to a seg. fault.

From looking at the code with @shamisp the problem appears to be that ucp_request_set_callback unconditionally sets UCP_REQUEST_FLAG_CALLBACK.

It seems like the parameter names used to control AMG and solver settings are pretty different for the MPI vs. non-MPI versions of the runtime AMGCL interface. For example, in examples/mpi/solve_mm_mpi.cpp, we have

prm.put("local.coarsening.type", coarsening);
prm.put("local.relax.type",      relaxation);
prm.put("isolver.type",          iterative_solver);

but these parameters lik

We worked very hard to get everything working in Travis. this demonstrates how to build and run everything, but it would be ideal if we translated this information into documentation for how to build the dependencies.

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

Publish to pypi checklist:

• pykwalify requirements changes (1.7.1+)
• Create setup.py
  • Migrate requirements.txt
  • Add entry_points
  • Add README.md ingestion
• Update travis with publish step
• Update README/install docs with pypi option (with caveats)

The dmtcp_launch(1) man page DESCRIPTION section is currently:

DESCRIPTION
       dmtcp_launch launches a process under DMTCP control.

       A typical usage is:
       rm ckpt_a.out_*.dmtcp # Remove any stale copies of ckpt image

In particular, it's missing the subsequent lines:

dmtcp_launch --interval 5 a.out
dmtcp_command --checkpoint # Execute this in another wind

imo everybody intending to do any real-life work with tomsfastmath will require this function to import his binary private keys etc. it should be mentioned right after fp_init() and fp_set(). i spent about half an hour to search for this functionality in both tfm pdf and ltm pdf without success, and only found out by digging through the ltc rsa code.

Part of kubeflow/mpi-operator#217.

• Good reference that summarizes scalability testing for tf-operator here
• We may be able to leverage https://github.com/kubeflow/kubebench

Describe building QUDA with cmake, getting cmake if not available and currently available options in cmake.
Particularly MPI detection.

I recently stumbled upon another test framework, called Catch2. It looks very interesting for us and is already used in couple of big open source projects. The biggest advantage is that it is a single header include. So we do not have to build GoogleTest anymore and we do not need t

The Chef Input variables need documentation.
https://github.com/SCOREC/core/blob/develop/phasta/phInput.h

Please donate your time. Documenting as few as two variables a day can prevent an innocent Chef user from seg-faulting.

We are using this page as a starting point for the variable descriptions:
https://fluid.colorado.edu/wiki/index.php/Chef:_Mesh_Partitioning#Chef