-
Notifications
You must be signed in to change notification settings - Fork 12
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
Docker infrastructure #37
Comments
@darribas I think we havent discuss what other packages can be included in that Docker, maybe a brief discussion about the "essential" toolkit to Explore, Analyse and Map the .pb files help us also to define what we should include in the updated Docs. |
yes, that's a great idea, I originally included those that'd allow the user to replicate the docs pages: Lines 24 to 28 in c5f2833
A bit of group discussion as to whether that is correct or we want to expand a bit further would be great. |
My view is, tools like Jupyter Notebook, might provide the experimental toolkit that any data scientist can use to play with the output, in previous discussions the in that the framework or tools was not part of the core of SPC. Now after my experience in the ASG event and other questions, I vote to include in the docker some king of "essential" toolkit to Explore, Analyse and Map the output" (in additional to your suggestions, I'd add Jupyter Lab). Including some examples (Or the already scripts created by Dustin or others we could have) to provide guidance on how to use it. We are claiming easy to use, then I think it falls in our responsibility some kind of teaching/guidance about how to 1) extend the data schema ( we could use some of the use cases we have been included) and 2) How to use it the .pb file in external models ( ASPICS, and other). Happy to discuss this in our meetings or chats. |
Opening separate issue from #33 to discuss and deploy a working model for the "official" SPC image for folks to use. This builds on discussion started on #34 (comment) .
Current thinking (to progress on discussion):
README
Before done, we at least need to:
Anything else I'm missing?
The text was updated successfully, but these errors were encountered: