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.

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

Update module 10: Scientific file formats #93

Open
jemrobinson opened this issue Feb 16, 2022 · 0 comments
Open

Update module 10: Scientific file formats #93

jemrobinson opened this issue Feb 16, 2022 · 0 comments
Assignees

Comments

@jemrobinson
Copy link
Member

These changes will be coordinated by @nbarlowATI

General (applicable to every module)

  • Make each module independent of earlier ones (ie. do not rely on examples/specific code from earlier modules)
  • Ensure that each module has some small exercises (say 1x 5 min exercise per 45 mins or teaching); add a larger (optional) exercise per course for attendees to complete in their own time
  • Update to use more modern libraries and tools (eg. pandas/scipy/numba/poetry)
  • Add instructions to the notebooks that you should "Take 5 minutes to do this exercise"
  • Add estimated timing information at the top of each notebook
  • Switch to a colourblind-friendly colour scheme throughout
  • What do you wish people had told you about Python/coding in general?

Module 10: Scientific file formats

  • There were some good questions and good discussion about other binary file formats (parquet, arrow, feather) - this could be a good thing for us to cover.
  • The last two notebooks on Ontologies, and Semantic Web, are very difficult for a non-expert to teach - the Turtle syntax is very hard to read, and there isn't a huge amount of explanatory text. I would be in favour of downsizing these sections considerably, and devoting the time to something else - possibly other file formats as mentioned above, or perhaps something about streaming or distributed data.
    • We also found these difficult to teach last year! James H (who wrote the course) argued strongly for leaving them in, but maybe we can add additional material as noted about and make these optional reading?
  • We also had a question about Docker - this could be a good thing to mention at some point in the course (not necessarily this module).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants