hades | Repository for the CLiPS HAte speech DEtection System | Speech library

There is an extra [] missing on the siteConfig attribute.

It should be

Consider below approach

Make your random list as a set.

Then for every song you extract from it, pop it from the set

The "Sending build context" step is unrelated to the base image download. This step takes a long time because you are running on a remote builder, and your build command is using "." as its build context. This means that the entire contents of your local directory have to be sent over the network to the machine you are building your image on. This is also why it's much faster on your local machine; it doesn't need to transfer your local directory over.

if you add a .dockerignore file to your local directory, you can limit what gets transferred by listing any unnecessary files/directories in there. This will speed up this step.

Your name choices are more naturally organized as Radiobutton widgets.

I believe your goal and your current situation as follows.

• From your provided official document, I thought that you might use the method of "Waitlist" in "Waitlist".

• When I saw the sample curl command, it is as follows.

I think a lot of what you did, specifically around data wrangling, was not necessary, especially since you called d3.hierarchy() and d3.cluster() afterwards. I've replaced this with d3.stratify (which deals with hierarchical data that is not yet in the right format).

I've also replaced d3.cluster with d3.tree() because it was unclear to me why you'd want to use d3.cluster here. Your data has multiple parents, multiple roots and even floating nodes, and d3 is not meant to deal with that. My workaround has been to attach pseudonodes to every level, so as to make sure that there is only one node and that all nodes are at the right level at all times. To make sure the links were drawn correctly, I've written a custom getLinks function, that can deal with multiple parents.

I've also written a custom link generator that draws the links somewhat in the way that you want them. d3 doesn't offer much of flexibility here, but you can use the source code for inspiration.

Edit

I've changed the logic to be more focused on which "partners" got a child, so both links to the same child are on the same level - like in your picture. I've also drawn the nodes based on how many partners they have, and have given every link an offset so the lines are more distinct.

I've sorted the nodes so that the real pro-creators are at the top (Zeus), which gives a more balanced and less crowded view.

Cleaned it up a bit, and got it working nicely for ya!

if (esthos[name]) checks whether the the value held at ethos[name] is truthy. To explicitly cast it to a boolean, you can do if (!!esthos[name]). The reason for this is that javascript uses truthy and falsy values.

You can read more about it in this article.