hpc

We have both Symbol and Int getindex for a NamedTuple, but only Symbol setindex.

Is there a reason for this? its seems like we should have both in both cases.

Current implementation of join can be improved by performing the operation in a single call to the backend kernel instead of multiple calls.

This is a fairly easy kernel and may be a good issue for someone getting to know CUDA/ArrayFire internals. Ping me if you want additional info.

Currently spack does not support the following packages, all of these packages are installed outside of Spack at Cori, we would like to get support for these packages if possible.

• cpmd https://www.lcrc.anl.gov/for-users/software/available-software/cpmd/
• ComputeCPP https://github.com/codeplaysoftware/computecpp-sdk need to confirm link
• ds9 https://sites.google.com/cfa.harvard.

Version of Singularity:

3.0.3

Expected behavior

Some progress or update information during the creation of the SIF file.

Actual behavior

During "Creating SIF file..." step, the console does not produce any visible output for the user - but does create the resulting file eventually.

Steps to reproduce behavior

I was executing a few “larger” builds through the bui

What would you like to be added:

Currently, there are few materials about job plugins(ssh/env/svc) such as scenarios, design and usages, expecially about the available parameters in these plugins.

Why is this needed:

We've got a lot of feedback about how to use the job plugins.

In order to test manually altered IR, it would be nice to have a --skip-compilation flag for futhark test, just like we do for futhark bench.

The documentation for the function shmem_wait seems inconsistent with the function signatures as it describes parameters target, pe, and value that are actually not part of the interface. The parameter ivar is described but at least in the C interface the variable is named var (without the prefix i).

See https://github.com/open-mpi/ompi/blob/master/oshmem/shmem/man/man3/shmem_wai

Hello,

In version 7.1.0, runtime.dat no longer functions to stop the job using "OUTER_ITER=", "EXT_ITER=", or "TIME=". Did the parameter change?

(CentOS 7, gluster FS, GCC 7.3.1)

Add the appropriate libncurses package name for each supported distro. This is commonly named libncurses5.

Cirrus CI now has the ability to run tests over an ARM container:

https://cirrus-ci.org/guide/linux/#linux-containers

.cirrus.yml could be updated to add a test case that run on such container to verify Modules correctly build and run on such CPU architecture.