You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Search for duplicates among the existing issues, both open and closed.
Description
At #685, #1064, #1090, and #1103, I said that downstream targets of dynamic targets must be dynamic except if you use readd() to turn a dynamic target into a static one. This was always problematic because it required the user to understand the internals of dynamic branching. I just had an idea about how to avoid this problem. It has to do with the internals of memory management, and if it works, we will be able to write plans like this:
Currently it fails because drake thinks rows is a vector of hashes (i.e. how it represents dynamic targets). The goal for this example is to get drake to understand that rows should be a data frame for means.
wlandau
changed the title
Automatically handle downstream targets of dynamic targets
Automatically handle dynamic dependencies of static targets
Dec 10, 2019
Prework
drake
's code of conduct.Description
At #685, #1064, #1090, and #1103, I said that downstream targets of dynamic targets must be dynamic except if you use
readd()
to turn a dynamic target into a static one. This was always problematic because it required the user to understand the internals of dynamic branching. I just had an idea about how to avoid this problem. It has to do with the internals of memory management, and if it works, we will be able to write plans like this:Currently it fails because
drake
thinksrows
is a vector of hashes (i.e. how it represents dynamic targets). The goal for this example is to getdrake
to understand thatrows
should be a data frame formeans
.cc @dpmccabe, @keondonB, @billdenney, @brendanf
The text was updated successfully, but these errors were encountered: