sif | purpose distributed computing in the map/reduce paradigm | Architecture library

This is not an Angular issue, rather JS scoping. Instead of assigning generateTooltip: this._showFullTooltip, bind the scope to the function as well like so generateTooltip: this._showFullTooltip.bind(this).

When you pass along a function reference the this keyword will be the context of whoever/whatever is invoking that function. By using the .bind(this) you overwrite the function invocation context with the current assignee context (DashboardComponent). This should allow you to use this.chart.data[row] in your _showFullTooltip function.

Looks like mongod is still trying to write some files somewhere that isn't mounted from the host OS.

"Fast" solution: use singularity run --writable-tmpfs ... to add a writable overlay layer to the running container. This will allow files to be written/modified on the read only .sif, but they will be discarded as soon as the process stops.

"Best" solution: find out what is being written to where, and update the mount points to the relevant locations.

I recommend using the fast solution to find out how to implement the best solution. lsof | grep mongod once it is able to run normally should get you pretty far.

The function igraph::graph.edgelist has the option el which should be a two column matrix. The two columns should contain node names for each side of the edge (e.g. from and to). You did d.int[, c(1, 3)] which selects the type which are not node names. Try d.int[, c(1, 2)] instead.

From your build output it seems that some of the valhalla libraries depend on each other, and those dependencies are not reflected in your CMakeLists.txt. For example, the Tyr library seems to depend at least on the Baldr, Loki, Thor and Odin libraries (as can be seen from the names of the undefined symbols you get). To reflect this dependency you should add something like this to your CMakeLists.txt file:

You need to note that every color is represented by 3 values or channels, i.e. red, green and blue. If you only keep one of those channels you'll skew the results.

Instead you need to decide whether a pixel should retain its original color or become grayscale. So assuming your code already does the conversion to grayscale correctly, it comes down to this:

As you found, instance list only lists singularity processes that were started as instances. Instance logs (both running and past) are stored in ~/.singularity/instances/logs/$HOSTNAME/$USER.

Active processes from non-instance commands aren't tracked anywhere. This is largely because Singularity does not use a centralized service model like Docker. Similarly, there's no "default" log location because stdout/stderr are handled that same as running any other command. As such, tracking down Singularity processes can be done using the standard shell tools.

Some examples:

When you run:

Short answer:

bug your HPC admins to install Singularity

Longer answer:

There are two ways to install Singularity, as a privileged installation or an unprivileged / user namespace installation. The first way is the default, but requires sudo/root for certain actions (mostly singularity build). The latter removes the need for root, but has other system requirements. It's possible additional OS configuration is necessary for Singularity to function as expected.

In addition to privileged/unprivileged installations, disk storage in clusters is usually on NFS or another networked/distributed filesystem so all nodes have access to the same data. Unfortunately, as is usually the case any time it is involved, NFS is a likely cause for your problem. Singularity relies on SUID for its core functionality, but for (quite good) security reasons SUID is disabled on NFS by default. It is unlikely the cluster admins will enable that option, so your best bet is to ask them install it locally on whichever computer/interactive nodes you need it on.

The Singularity equivalent of docker image ls is ls *.sif.

This is one of the key differences between Docker and Singularity: a service with a centralized collection of local images available to all group members vs. images as files that can be run by anyone on any computer with singularity installed. The cache listing you show is also specific to your user (generally ~/.singularity/cache), though build actions do end up with a shared cache at /root/.singularity/cache as they require sudo privileges.

Another important distinction between docker image ls and singularity cache list is after clearing your singularity cache, the sif you generated still works as expected. Removing a docker image is the equivalent of deleting that sif file.

If an image is likely to be used by others, it's worthwhile to set up a shared location on the filesystem. This way you can also separate users who have permission to create images from those who just need to use them.