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
I'd like to use the data from variables in the factor evaluation, e.g. Radar data. I think we should pass down the variables into the factor evaluation, so that I could potentially use smallData or bigData.
DF edit, predominant design discussion over in #783 -- can use this issue once a decision has been made there on how to split manifest and user-meta-data requirement.
user desire for more "metadata" in a variable: #783 (comment) -- i.e additional data format and contents from end user not know at design time.
The text was updated successfully, but these errors were encountered:
Punchline is to use the new CalcFactor approach, and hopefully stable API defined in v0.21. See #467 as relatively well linked issue discussion on what the API should be. All metadata (variables, smalldata, entry=>data, etc.) are available through the CalcFactor approach. This is both during residual factor evaluation and getSample.
I'd like to use the data from variables in the factor evaluation, e.g. Radar data. I think we should pass down the variables into the factor evaluation, so that I could potentially use smallData or bigData.
EDIT
DF, punchline: #784 (comment)
DF edit, predominant design discussion over in #783 -- can use this issue once a decision has been made there on how to split manifest and user-meta-data requirement.
user desire for more "metadata" in a variable: #783 (comment) -- i.e additional data format and contents from end user not know at design time.
The text was updated successfully, but these errors were encountered: