Brian Derstine

I agree

Additionally, I followed the file backend methodology and it seems to have a bug: ``` ## Create a keyring and add an entry using the variables above kb

FYI: it doesn't seem possible to put a gridExtra::tableGrob(...) as the first element in the list of plots? ``` p1

aha! Now that I know to look for it, I found the following: "`distinct` gives distinct records for which all attributes and geometries are distinct; `st_equals` is used to find...

I noticed several related odd behaviors with the tooltip argument in `ggplotly()`. For `ggplot`, the order and placement of aes's sometimes matters: ``` data(mtcars) mtcars$text

ah, had same exact error attempting to make same plot labels! Fold Change vs. negative log p-value is the 'volcano plot'.

Aha! This seems to have worked: `export PATH=$PATH:/usr/pgsql-15/bin` (I also tried: `export PKG_CONFIG_PATH=/usr/lib64` but this didn't work. I can confirm that the `export PATH ...` fix above was thing that...

When I try that, it doesn't seem to change anything: ``` $ sudo dnf install libpq-devel Updating Subscription Management repositories. github_git-lfs 691 B/s | 833 B 00:01 github_git-lfs-source 673 B/s...

I modified my .bashrc file to include `export PATH=$PATH:/usr/pgsql-15/bin` so that this would persist across sessions, although other users on the machine would need to modify their own .bashrc file....

If that is the case then the menu wording is misleading. All of the menu items referring to "segments" should be changed to single tense "segment" to avoid confusing users.