gg | Ultra minimalistic , cross-platform GUI toolkit based on SDL | Media library

Comparison operators returns NA when there is an NA

IODKU lets you eliminate the separate SELECT:

This isn't exactly what you're looking for. I was able to create a meaningful color bar, though.

I removed the call for interaction between the groups and created a separate trace. Then I created legend groups and named them to create separate legends for gender and age. When I pull color = out of the call to create a colorbar, this synced the color scales.

However, it assigns colors to the labels for age and gender and that's not meaningful! There are a few things that don't line up with your request, but someone may be able to build on this information.

Here is a useful regex trick approach:

You asked:

is there a clean way to achieve this using Java Streams?

Yes. Indeed, you can process your inputs, filter out the unwanted parts, and produce a finished list, all using streams.

First define some example data, a list of inputs.

Generate a stream from that list. This stream has 3 elements, given our example data.

Call Stream#flatMap to return a new stream whose elements are made from pieces of the original stream’s elements. The new stream has 9 elements, produced by breaking each of the 3 original elements into 3 parts each (3 * 3 = 9).

Filter the newer longer stream for elements whose text starts with our targeted y= prefix.

Transform each of the string elements that passed our filter’s predicate test. Use simple string manipulation to replace "y=" with an empty string. So a value such as y=bb becomes bb.

Collect transformed strings by gathering into a new List object.

You can use walrus operator. But list comprehension is not meant to efficient, it's just shorter(I think)

Current IntelliJ IDEA version requires Java 11 to run. Remove the overrides (idea.jdk file/environment variables) to use the default bundled JetBrains Runtime.

This may not be what you want but you can do this by adding a runtime of shiny in your yaml

Looking at the plotly code here (excerpt below), it seems that the raster is only defined for any values of x and y available in the dataset - and whatever happens in between is up the the rest of the plotly code.