torus | Torus Distributed Storage

Since you have enabled coords = TRUE when generating g, the layout coordinates names have been given as x and y.

To avoid collision, you should name layout l1 with different column names, e.g., lx or ly,

You have used MeshBasicMaterial for your plane mesh which is a unlit material. So it does not receive shadpws. Using a lit material like MeshStandardMaterial solves the issue.

When lighting (GL_LIGHTING) is enabled, then the color which is associated, is taken from the material parameters (glMaterial).

If you still want to use the current color attribute (which is set by glColor), then you have to enable GL_COLOR_MATERIAL and to set the color material paramters (glColorMaterial):

For a 1D torus interconnect, the diameter is floor(p/2).

Thus, for a 3D torus interconnect, the diameter is floor(p/2) * 3 since the Manhattan distance should be used for this grid-based interconnect. To visualize that, you can think about a small 4 x 4 x 4 grid and how data packets move through the edges of the grid.

In older versions of SLSQP, there were bugs in the design variable bounds enforcement. This was fixed in the scipy SLSQP code base, but never in the pyoptsparse one. In other words the SLSQP code in the two code bases is not the same, and has diverged a bit. That explains why ScipyOptimizerDriver is respecting your bounds and pyOptSparseDriver is not (when using SLSQP). If you switch to IPOPT in pyOptSparse, then it would respect your bounds.

You are looking for torch.roll

The HTTP protocol is stateless. That means you cannot save data in variable for later. You can use a session to store values in siuations like this one. Check PHP Sessions for more info.

In short:

1. Start session if you did not already done it.
2. Save message in session $_SESSION["error"] = "Error message";
3. Check and echo error value if isset($_SESSION["error"]) { echo $_SESSION["error"]; }

If I replace scene with this.scene it seems to work just fine. Notice however that the combination of WebGL rendered 3D objects and HTML elements is problematic in some cases since depth testing does not work across both primitive types.

With the current setup, the image will always be rendered on top of the torus.

As far as I know, the L2Switch feature which was responsible for L2 switching is not supporting after the Fluorine version. There is no module for arp handling l2 switching. It may visible to write a code to do L2 forwarding.

P.S Regarding your topo "This topology has LOOPS and WILL NOT WORK with the default controller or any Ethernet bridge without STP turned on! It can be used with STP, e.g"