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.

Sign up for GitHub

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

Jump to bottom

Move generic EpiAwarePipeline tools into a package hosts at ~/EpiAwarePipeline. #280

Open
Tracked by #232
SamuelBrand1 opened this issue Jun 12, 2024 · 2 comments
Open
Tracked by #232

Move generic EpiAwarePipeline tools into a package hosts at ~/EpiAwarePipeline. #280

SamuelBrand1 opened this issue Jun 12, 2024 · 2 comments
Labels
pipeline

Comments

@SamuelBrand1
Copy link
Collaborator

No description provided.

@SamuelBrand1 SamuelBrand1 mentioned this issue Jun 12, 2024
Open
3 tasks
@SamuelBrand1
Copy link
Collaborator Author

Where does core and specific tooling begin and end here?

@seabbs
Copy link
Collaborator

seabbs commented Jun 12, 2024 •
edited
Loading

I think every function should have a abstract type method and that lives in EpiAwarePipeline. Anything that is a explicit type lives in implementation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pipeline
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@seabbs @SamuelBrand1