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 look into only passing minimal inputs (component table- or even just the requested metrics as lists/arrays; cross-component metrics; hyperparameters) to the selection node functions, rather than the whole ComponentSelector. I think we could probably create a class (e.g., SelectionNode) to handle any logging that goes on in the individual selection node functions at the moment.
The text was updated successfully, but these errors were encountered:
tsalo
added
the
refactoring
issues proposing/requesting changes to the code which do not impact behavior
label
Feb 29, 2024
I'll think about this more once we get the other active refactors into the code. This would be a non-trivial amount of work. I don't think this would make a meaningful computational speed or memory difference, but it has the potential to make the code slightly easier to understand.
Summary
I'd like to look into only passing minimal inputs (component table- or even just the requested metrics as lists/arrays; cross-component metrics; hyperparameters) to the selection node functions, rather than the whole ComponentSelector. I think we could probably create a class (e.g., SelectionNode) to handle any logging that goes on in the individual selection node functions at the moment.
The text was updated successfully, but these errors were encountered: