D2.4: A short course for lecturers on using OpenDreamKit for delivering mathematical education. #44

Closed
minrk opened this Issue Sep 8, 2015 · 20 comments

Comments

@minrk
Contributor

minrk commented Sep 8, 2015

SageMathCloud is both an open source software project (https://github.com/sagemathinc/smc) and an online instance of that software (hosted at https://cloud.sagemath.com/) that provides an interactive, collaborative environment for teaching and research in science, technology, engineering, and mathematics. SageMathCloud is used in teaching all over the world and a selection of courses utilising it can be found at https://github.com/sagemathinc/smc/wiki/Teaching. SageMathCloud predates OpenDreamKit and acts as prototypical example of VRE that can be built from the ecosystem OpenDreamKit aims at fostering; hence we are working in close collaboration with its development team.

In this deliverable, we have developed a short course for educators who wish to adopt this technology in order to enhance their teaching. Produced in collaboration with SageMathCloud developers and the wider community, the result is a website (https://mikecroucher.github.io/SMC_tutorial/) that can easily co-evolve with the technology it describes.

@minrk minrk added this to the D2.4 milestone Sep 8, 2015

@nthiery nthiery modified the milestones: Month 18: 2017-02-28, D2.4 Mar 22, 2016

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Jun 13, 2016

Member

In support of this item, I'm writing a tutorial for lecturers on how to use SageMathCloud for teaching. Github repo at https://github.com/mikecroucher/SMC_tutorial

Member

mikecroucher commented Jun 13, 2016

In support of this item, I'm writing a tutorial for lecturers on how to use SageMathCloud for teaching. Github repo at https://github.com/mikecroucher/SMC_tutorial

@bryongloden

This comment has been minimized.

Show comment
Hide comment

👍

@bpilorget

This comment has been minimized.

Show comment
Hide comment
@bpilorget

bpilorget Nov 21, 2016

Contributor

@mikecroucher (lead beneficiary) and @VivianePons (WP leader)
This deliverable is due for February 2017

Contributor

bpilorget commented Nov 21, 2016

@mikecroucher (lead beneficiary) and @VivianePons (WP leader)
This deliverable is due for February 2017

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Nov 22, 2016

Member

The SageMathCloud (SMC) tutorial is largely done and has been used here at Sheffield to teach lecturers in several departments including Physics, Biomedical sciences and Computer Science. It's also linked to from SMC itself as part of its documentation. There is a plan to hack on this further in January #208 (comment) and I'll spend some more time on it in December.

This has led to several departments at Sheffield using Jupyter and SMC as an integral part of their teaching.

This was what I had in mind when I wrote the deliverable. I'd value others' opinions on what else needs to be done in this area.

Member

mikecroucher commented Nov 22, 2016

The SageMathCloud (SMC) tutorial is largely done and has been used here at Sheffield to teach lecturers in several departments including Physics, Biomedical sciences and Computer Science. It's also linked to from SMC itself as part of its documentation. There is a plan to hack on this further in January #208 (comment) and I'll spend some more time on it in December.

This has led to several departments at Sheffield using Jupyter and SMC as an integral part of their teaching.

This was what I had in mind when I wrote the deliverable. I'd value others' opinions on what else needs to be done in this area.

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 6, 2017

Contributor

Dear M18 deliverable leaders,

Just a reminder that reports are due for mid-february, to buy us some time for proofreading, feedback, and final submission before February 28th. See our README for details on the process.

In practice, I'll be offline February 12-19, and the week right after will be pretty busy. Therefore, it would be helpful if a first draft could be available sometime this week, so that I can have a head start reviewing it.

Thanks in advance!

Contributor

nthiery commented Feb 6, 2017

Dear M18 deliverable leaders,

Just a reminder that reports are due for mid-february, to buy us some time for proofreading, feedback, and final submission before February 28th. See our README for details on the process.

In practice, I'll be offline February 12-19, and the week right after will be pretty busy. Therefore, it would be helpful if a first draft could be available sometime this week, so that I can have a head start reviewing it.

Thanks in advance!

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 23, 2017

Contributor

Hi @mikecroucher; the report for D2.4 is becoming urgent! Let me know if you are missing information to proceed.
Thanks!

Contributor

nthiery commented Feb 23, 2017

Hi @mikecroucher; the report for D2.4 is becoming urgent! Let me know if you are missing information to proceed.
Thanks!

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Feb 24, 2017

Member

I'll get on it today. Thanks for the reminder

Member

mikecroucher commented Feb 24, 2017

I'll get on it today. Thanks for the reminder

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 24, 2017

Contributor
Contributor

nthiery commented Feb 24, 2017

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Feb 24, 2017

Member

@nthiery Sorry to be a pain but can you remind me where the report template is please?

Member

mikecroucher commented Feb 24, 2017

@nthiery Sorry to be a pain but can you remind me where the report template is please?

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 24, 2017

Contributor
Contributor

nthiery commented Feb 24, 2017

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Feb 26, 2017

Member

I've updated the description of the deliverable at the top of this issue but the \githubissuedescription command is still pulling down an old version. The text DELIVERABLE DESCRIPTION, AS TAKEN FROM GITHUB ISSUE #44 ON 2017-02-08 gets included in the report.

How can I kick this so that the updated text appears?

Member

mikecroucher commented Feb 26, 2017

I've updated the description of the deliverable at the top of this issue but the \githubissuedescription command is still pulling down an old version. The text DELIVERABLE DESCRIPTION, AS TAKEN FROM GITHUB ISSUE #44 ON 2017-02-08 gets included in the report.

How can I kick this so that the updated text appears?

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Feb 26, 2017

Member

First draft completed. Would you mind taking a look please @nthiery

Member

mikecroucher commented Feb 26, 2017

First draft completed. Would you mind taking a look please @nthiery

mikecroucher added a commit that referenced this issue Feb 26, 2017

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 26, 2017

Contributor

On it.
I fetched the latest description from the github issue, by using:

ODK > rm WP2/D2.4/report.pdf WP2/D2.4/github-issue-description.*
ODK > make WP2/D2.4/report.pdf

and committed and pushed.

Contributor

nthiery commented Feb 26, 2017

On it.
I fetched the latest description from the github issue, by using:

ODK > rm WP2/D2.4/report.pdf WP2/D2.4/github-issue-description.*
ODK > make WP2/D2.4/report.pdf

and committed and pushed.

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Feb 26, 2017

Member

Thanks. Does the report look OK for the EU?

Member

mikecroucher commented Feb 26, 2017

Thanks. Does the report look OK for the EU?

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 26, 2017

Contributor

I'll commit a few minor edits in a couple minutes. Altogether, that looks good indeed!

Further suggestions:

  • Reproofread the issue description after my changes
  • Give some figures in the report: e.g. number of attendees to the workshop, "size" of the website
  • There is a tiny bit of repeat between Section 1 and the first paragraph of Section 3.
  • Mention some web technologies used to produce the website (jekyll?)
  • You may want to include some material in the appendix. Things that you really want the reviewers to look at. That could typically be screenshots of some of the main pages of the website, or the BMS 353 teaching story. See WP5/D5.4/report.tex for an example on how we did that in another deliverable.

Cheers,

Contributor

nthiery commented Feb 26, 2017

I'll commit a few minor edits in a couple minutes. Altogether, that looks good indeed!

Further suggestions:

  • Reproofread the issue description after my changes
  • Give some figures in the report: e.g. number of attendees to the workshop, "size" of the website
  • There is a tiny bit of repeat between Section 1 and the first paragraph of Section 3.
  • Mention some web technologies used to produce the website (jekyll?)
  • You may want to include some material in the appendix. Things that you really want the reviewers to look at. That could typically be screenshots of some of the main pages of the website, or the BMS 353 teaching story. See WP5/D5.4/report.tex for an example on how we did that in another deliverable.

Cheers,

mikecroucher added a commit that referenced this issue Feb 27, 2017

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 27, 2017

Contributor

Thanks; I'll look at this after lunch!

Contributor

nthiery commented Feb 27, 2017

Thanks; I'll look at this after lunch!

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Feb 27, 2017

Member

Thank you @nthiery. I've tried to act on all of your suggestions and have added a couple of appendices that include the BMS353 case study and Mark Quinn's slide deck from the January meeting which tells the story of the Physics teaching here. I think it shows evidence of great impact (Fundamentally changing how 500+ students are taught!).

Member

mikecroucher commented Feb 27, 2017

Thank you @nthiery. I've tried to act on all of your suggestions and have added a couple of appendices that include the BMS353 case study and Mark Quinn's slide deck from the January meeting which tells the story of the Physics teaching here. I think it shows evidence of great impact (Fundamentally changing how 500+ students are taught!).

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 27, 2017

Contributor

Yeah, that's quite impressive :-)

Contributor

nthiery commented Feb 27, 2017

Yeah, that's quite impressive :-)

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 27, 2017

Contributor

Submitted! Congratulations @mikecroucher and everybody who helped for making this happen so successfully, and thanks the nice report.

Contributor

nthiery commented Feb 27, 2017

Submitted! Congratulations @mikecroucher and everybody who helped for making this happen so successfully, and thanks the nice report.

@nthiery nthiery closed this Feb 27, 2017

@mikecroucher

This comment has been minimized.

Show comment
Hide comment
@mikecroucher

mikecroucher Feb 27, 2017

Member

and thanks for all of your help. You're a star.

Member

mikecroucher commented Feb 27, 2017

and thanks for all of your help. You're a star.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment