hpc

I found the sentence in the title obscure at first.
Alternative wordings:
The value of a global variable might change at any point, possibly leading to a change of its type.

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

In the kubernete clusters, we are using the auto-scaler for the resource provisioning. We found for the pytorch distributed training job, if a node finished eariler and the scaler scale down it, the pod is marked deleted and will trigger the deletePod being called, then due to this pod eviction event, the job will be restarted and then failed.

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.

Dear Colossal-AI team,
There are a few features in my mind that I thought would be helpful to the project, and I wanted to ask if there is any of them which might be more useful so I could start implementing them.
Loki-Promtail is a tool for monitoring distributed logs with Grafana. Connecting the Distributed Logger to it and extracting labels from the log structure would be a user-friendly sys

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

Good evening, I am currently struggling with compiling SU2 from source code. After I have built the program I try to compile it using ninja.exe, but during the process I get the following error:

[443/454] Linking target SU2_DEF/src/SU2_DEF.exe
FAILED: SU2_DEF/src/SU2_DEF.exe
c++ @SU2_DEF/src/SU2_DEF.exe.rsp
C:/Program Files/mingw-w64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.1.0/../..

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

while the FORCE_EVAL/SUBSYS/COORD allows to add an optional string after the coordinates to specify the connectivity, additional columns in a XYZ file are ignored, since the XYZ file format is not standardized. Nevertheless, it would be nice to have an option to tell CP2K to use the N-th additional column in a XYZ for the connectivity (or possibly other things).

@KanySUI is that about right?

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.