Closed msuchard closed 3 years ago
Not really an Andromeda issue. Somewhere arrange()
is being called (as lazy operation) on an Andromeda table, and then other operations are applied subsequently, which could very well change the order and so make the arrange()
call have no effect.
What specific context is this warning occurring?
The warnings are occurring here: https://github.com/OHDSI/Cyclops/blob/75ab6624719e7bf193e744ad6061962c7a008d5c/R/NewDataConversion.R#L350
There are number of (important) covariates <- covariates %>% arrange()
before the batchApply
but as far as I can see there are no arrange()
after this point (i.e. in loadCovariates
and further downstream).
Might I need to force executing of the earlier covariates <- covariates %>% arrange()
statements? And, how do I do this?
Solved by @schuemie here: https://github.com/OHDSI/Cyclops/issues/52
Below is a warning I am seeing in the
Cyclops
test-units. Is this an error inAndromeda
? @schuemie