Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'predicted' and 'results' functions vs use of a mapping class #6

Open
grlloyd opened this issue Jul 23, 2018 · 0 comments
Open

'predicted' and 'results' functions vs use of a mapping class #6

grlloyd opened this issue Jul 23, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@grlloyd
Copy link
Member

grlloyd commented Jul 23, 2018

Functions 'predicted' and 'results' allow different outputs to be used as the input to the next model when using e.g. model.lists or chaining together iterators.

A better approach might be to create a 'mapping' class where the outputs from one object are explicitly assigned to the inputs of the next. This would allow more flexibility and streamline e.g. using VIP rank as inputs for Forward selection, and allow multiple outputs from one model as inputs to another. mappings can be auto-generated when creating an object if output names match input names, for example, but changed by the user for bespoke applications.

Unsure how this would work in galaxy environment.

@grlloyd grlloyd added the enhancement New feature or request label Jul 23, 2018
@grlloyd grlloyd self-assigned this Jul 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant