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
Based on the discussion (17.02), we decided to give it a try with a full parameter refactoring.
The entire premise is based on the uniqueness of parameter names (ie. both design matrix groups, and genkw groups don't share any parameters) in the global parameter domain / space.
The draft should thus contain two suggestions:
The actual parameter configuration setup. Bear in might that field and surface parameter stay practically the same.
The loading and saving of parameter into the storage. Here, the suggestion was to exploit pollars and use the row-wise way of data storing to preserve the data type:
Parameter Name
Value
Transformed Value
Param1
10
f(10
Param2
25
f(25)
Param3
100
f(100)
The text was updated successfully, but these errors were encountered:
Based on the discussion (17.02), we decided to give it a try with a full parameter refactoring.
The entire premise is based on the uniqueness of parameter names (ie. both design matrix groups, and genkw groups don't share any parameters) in the global parameter domain / space.
The draft should thus contain two suggestions:
The text was updated successfully, but these errors were encountered: