-
Notifications
You must be signed in to change notification settings - Fork 40
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
'Use Cases' section on opendreamkit.org #75
Comments
Related to the forthcoming workshop, maybe
|
[ ] Write high-level code that runs at « native speed », either using a
ffi tool or a compiler
That's a very good point: we should have use cases about performance,
and in particular the ease of writing fast code.
There remains to frame this into a compelling user story. Something
that makes a visitor reading the scenario immediately think "ah yes, I
have been in those shoes; many people will need that"!
|
A group of coauthors want to collaborate on the GAP code in the GitHub repository, not organising it in a form of GAP package, but using the same as GAP packages for CI and test coverage. Eventually they put a demo of their code in a Jupyter notebook, runnable on Binder, and used the RISE extension to use the same notebook in a slideshow mode. This is https://github.com/sukru-yalcinkaya/unipoly described in the Appendix to D5.15. |
A group of coauthors want ...
That sounds very nice! Are you willing to write up a brief use-case
document about it?
|
@nthiery I do. They also have a press-release at https://www.mub.eps.manchester.ac.uk/in-abstract/adjoint-representations-of-black-box-groups/. Collaborative visits were supported by CCP-CoDiMa, and then we agreed that this could be a basis for an interesting demonstration of ODK. An abstract use case would go further - start the project this way, instead of organising the code after, and submit is as a supplementary material to the paper when it is published. |
We are writing up a use case for MathHub data. |
and an announcement of the system itself (for 8/2019) that we should have done earlier. |
Katja has written two new posts and committed them, but they are not showing up on the web page (for two hours). |
They were missing a .md extension. Fixed.
… Katja has written two new posts and committed them, but they are not showing up on the web page (for two hours).
I wonder whether that is still too busy, ...
|
thanks a lot. I had looked and not seen this. Chapeau |
@minrk: thanks for the use case on collaboration!
|
Great suggestion!
Yes, I'm working on a demo of this. The Work-in-Progress in JupyterLab is in a bit of a transition, so I'm trying to figure out what will demo best. |
Hi @VivianePons, @alex-konovalov, |
@nthiery @VivianePons good idea - and also about delivering training (for which they can use our training materials). |
(hi)
On Sat, Oct 26, 2019 at 10:15:42AM -0700, Alexander Konovalov wrote:
@nthiery @VivianePons good idea - and also about delivering training (for which they can use our training materials).
And our jupyter-training extension.
…--
Nicolas Chauvat
logilab.fr - services en informatique scientifique et gestion de connaissances
|
> @nthiery @VivianePons good idea - and also about delivering training (for which they can use our training materials).
And our jupyter-training extension.
Yes; so really two different use cases:
- Getting training
- Teaching with Jupyter
I added both to my wish list in the first comment of this issue :-)
|
Our web site now has a
Use cases
section, currently available from the Project menu. It's meant to hold short documents such as this one with the following structure:Such documents can be both useful to our readers (providing them with operational solutions and best practices) and to us (showcasing our work, with a concrete perspective on the impact of our actions). In particular it will highlight the versatility brought by the toolkit approach.
Currently, there is a single use case; we should write more! By design they can be relatively short and fun to write, so please volunteer.
Here are some suggestions:
Any others welcome!
Once we have enough documents, we should also make the use case section very prominent; possibly moving it to the front page.
The text was updated successfully, but these errors were encountered: