Changtao Li

I have the same issue, and I have tried other methods: 1. `View()` by XQuartz, 2. `DT::datatable()`, 3. `tkWidgets::dataViewer()` (it crashed), 4. `DataEditR::data_edit()`. Except `3` (it crashed), all other methods...

> Possible Solution: > > ``` > SpatiallyVariableFeatures_workaround #' This is work around function to replace SeuratObject::SpatiallyVariableFeatures function. > #' return ranked list of Spatially Variable Features > > #...

> whien I run filtered_data > * data[[paste0(selection.method, ".spatially.variable")]] & (!is.na(data[[paste0(selection.method, ".spatially.variable")]])), > * moransi_cols > * ], new issue intercome😧 > Error in h(simpleError(msg, call)): > Error evaluating argument...

I assume you want [`colorout`](https://github.com/jalvesaq/colorout) package? But it is not compatible with `Radian`.

I don't know how to fix it. It is useful for vim mode but I don't use vim mode.

@ocsmit Wow, thank you so much for your solution! After editing the source code and reinstalling the `languageserver` package, the issue is all fixed for me!

After coding in R for a few hours, I wanted to report a bug related to these changes. In VSCode, I get a memory limit error when plotting with the...

> After coding in R for a few hours, I wanted to report a bug related to these changes. In VSCode, I get a memory limit error when plotting with...

After reading some resources, I realized this might not be a big deal from the computational perspective. If there are no **real tied times** (i.e., two or more events happening...

https://github.com/Novartis/torchsurv/blob/e359edb0b51ec140e5067df7422cf35d6a92492d/src/torchsurv/loss/cox.py#L32 By the way, if you plan to switch from using **unique times** to **unique event times**, you may also need to adjust the sorting step. Currently, [times are sorted...