Is the API support for this coming?
457 karma · joined November 25, 2012
Previously founded and sold rinocloud.com, and was a PhD student at University of Cambridge working on quantum computing.
Github : https://github.com/eoinmurray
Email: eoin at kyso.io
Is the API support for this coming?
We will be supporting runnable dashboards and notebooks soon.
You can currently use https://github.com/jupyter/colaboratory But its not under heavy development anymore, only internally at Google.
So for example if a sales team gather data, and there is a data-transform thats done all the time by hand, or feeding new data to an ML model, an internal app would save time, and Jupyter dashboards have the potential to make this really easy.
We are planning the fully runnable Jupyter environment in the future.
Thanks for your reply - this is on our roadmap, do you need the dashboards (we're the code runs, but is no editable) or full development notebooks?
We are planning both in the future - email me at "eoin [at] kyso.io" if you need this sooner rather than later.
edit: spelling
On our roadmap is for Kyso to work like the Google drive integration, where you can use a jupyter kernel (https://github.com/jupyter/jupyter-drive) hosted anyway but server the notebooks from Kyso.
And we are also planning fully runnable notebooks too, we do aim to be the easiest way to run your own jupyter server.
So normally when you publish a notebook online - you'd use Github or http://nbviewer.jupyter.org/
Github doesn't allow the interactive graphs, and nbviewer wont actually host the notebooks for you (you need to link from somewhere else).
Let you just type `kyso create "new-study"` and `kyso push "new version"` and your notebook is live online
edit for spelling
Will be releasing a node v6.0 compatible version in the next 2 days, and an node independent version very soon!!
my email is eoin [at] kyso.io
Launched https://kyso.io - Kyso is the fastest way to share data analysis to your team and the world.
tldr: they use jupyter notebooks, and use an internal system to execute them upon commit.
similarities to git; 1) we are making a portable datastore where the entirety of a body of data (metadata, discussion, data itself) can be moved around in a plain text format. 2) versioning and tracking of all evolutions to the data.
differences; obviously the diff'ing since a lot of datasets are non-text, or are very large (which we can handle).
Hope this tool is useful to some of you - let me know if you have any questions. Im hoping to get some feedback.
(quick demo here https://www.youtube.com/watch?v=LFRPAAj1ijc)
One of the best things I have seen to convince investors, assuming this is your first raise or seed round, is showing them 'interviews' with customers or potential customers - we have made that a central theme at Rinocloud - to do as much 20 minute Skype calls with current and potentials users - showing these to investors has been a massive success.
They could recoup the money from cheaper cars from the faster purchase cycle.
Or else move to a leasing model (this is becoming more popular with people I know in the UK, Ireland).