eruption | Realtime RGB LED Driver for Linux

It does not seem possible with to_array to get the string token list due to Doc.to_array return type, ndarray:

Export given token attributes to a numpy ndarray. If attr_ids is a sequence of M attributes, the output array will be of shape (N, M), where N is the length of the Doc (in tokens). If attr_ids is a single attribute, the output shape will be (N,). You can specify attributes by integer ID (e.g. spacy.attrs.LEMMA) or string name (e.g. “LEMMA” or “lemma”). The values will be 64-bit integers.

You can use

There are 2 workarounds, we can either rotate the labels using,

You can simply concatenate the conditions with the & operator and putting each condition in brackets ().

Y>ou don't want to keep you observer inside the render functions, since this causes an new initialization of an observer every thime the render function is called. I also splited up the code within the render function into two reactive statements so that we can access the at different places.

Unfortunately there is no scale_*_binned_manual(), so I'm afraid you'd have to set the values argument of the scale manually. Because the scale_fill_stepsn() function takes the midpoint between breaks as the point where the colour is interpolated (in transformed space), you can make sure that your colours fall exactly on these midpoints.

The problem is that in shiny::observeEvent(allinputIds(), shinyjs::enable("go")) you just check if the names/amount of input ids change - they don't. You actually need to check if the values of any of the inputs (besides the action button) has changed. Therefore you can either put all inputs directly into the observe like c(input$bins, input$...) or make an extra reactive to check for the values and just call this reactive.

In order to have OpenShift recognize an exposed port, I believe that you will need to express this in a LABEL on the Dockerfile

edit

I recommend not to use this answer - my second answer in this thread is much more appropriate, but I have answered this here in ignorance of the new functions. I still think it may be useful in very specific situations, so I leave it for future readers. The functions are taken and modified taken from Claus Wilke's comment in this github issue.

I'd also like to again recommend to consider user AF7's function to create a fake legend, because you have much more freedom how to style your legend.

geom_contour_filled discretizes your dimension of interest and then the inherently continuous scale_fill_discrete_gradient fails. It seems that metR::geom_contour_fill does not produce discrete data, but keeps it continous...

In order to make this solution work, you need to cut your variable to bins and then use the factor levels for setting breaks and limits. It's a bit hacky...

This looks like a bug in ggplot2, maybe in the iso_to_polygon function here: https://github.com/tidyverse/ggplot2/blob/b76fa9639215785f8e94874d3bdf02225bae898a/R/stat-contour.r#L284 . If levels have no data in them (your first plot has nothing greater than 0.04, so the top two bands are empty), then they are silently discarded.

Edited again:

Here's a partial workaround. If you specify the colour scale to use drop = FALSE, no levels will be dropped. For example,