https://github.com/imperialcollegelondon/fast-and-curious
The materials for the 2024 Fast and the Curious Hackathon run by the Research Computing and Data Science at the Graduate School
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (14.6%) to scientific vocabulary
Keywords
Repository
The materials for the 2024 Fast and the Curious Hackathon run by the Research Computing and Data Science at the Graduate School
Basic Info
- Host: GitHub
- Owner: ImperialCollegeLondon
- License: bsd-3-clause
- Language: Python
- Default Branch: main
- Homepage: https://blogs.imperial.ac.uk/postgraduatenoticeboard/2024/06/04/rcds-hackathon-2024-12-july-2024-sk-campus/
- Size: 887 KB
Statistics
- Stars: 2
- Watchers: 3
- Forks: 5
- Open Issues: 0
- Releases: 0
Topics
Metadata Files
README.md
The Fast and The Curious Hackathon
Introduction
This repository contains the code for The Fast and The Curious Hackathon. This hackathon is based around the dual themes of optimising code for speed and the use of Generative AI tools to assist with programming. It is written primarily in Python, but does not assume advanced levels of programming, and many of the techniques presented can be applied to other languages.
Pre-Session Work
In order to follow this hackathon, you will need to have a GitHub account. If you don't have one, you can sign up for free. You will also need to enable Github Copilot in your Github account. This is, by default, a paid-for feature, but it is also available for free to students and educators through Github Education. You can register for this here. It may take a few days for your application to be approved, so it is best to apply at least a week in advance.
There are several Jupyter notebooks (the files with the extension .ipynb) present in this repository. You may review them in advance if you want to, but you aren't required to.
Opening a Codespace
This hackathon is designed to run inside of a Codespace. A Codespace is a development environment hosted by GitHub directly from a repository. To use this, you will need to be signed into a GitHub account. To open the Codespace, click the green Code button at the top right of the repository. Make sure you're in the Codespaces tab and click the Create New Codespace on Master button. This will create a Codespace of your own. This will take a minute or so to initialise. You may be asked to reload the page. If so, do reload the page. If the Codespace seems to get stuck loading, reloading the page can often fix the problem.
Once your Codespace has initialised, it will remain associated with your GitHub account for around a month, when it will expire. Your Codespace will be given a name like "fuzzy-barnacle" so you can identify it. To reopen it on a future occasion, click the Code button again, then select the Codespace, click Open, then Open in Browser.
To download the content of the files within the Codespace, open the Files tab on the left, select the files, right click and click Download button. Alternatively, if you're familiar with GitHub, you can open the source control tab on the left, you can commit and push changes. This will fork the repository with your changes. Either of these options will allow you to keep a copy of the course notes with your solutions to the exercises, etc.
Owner
- Name: Imperial College London
- Login: ImperialCollegeLondon
- Kind: organization
- Email: icgithub-support@imperial.ac.uk
- Location: Imperial College London
- Repositories: 311
- Profile: https://github.com/ImperialCollegeLondon
Imperial College main code repository
GitHub Events
Total
Last Year
Issues and Pull Requests
Last synced: over 1 year ago
All Time
- Total issues: 2
- Total pull requests: 2
- Average time to close issues: 28 days
- Average time to close pull requests: about 15 hours
- Total issue authors: 1
- Total pull request authors: 1
- Average comments per issue: 3.0
- Average comments per pull request: 0.5
- Merged pull requests: 2
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 2
- Pull requests: 2
- Average time to close issues: 28 days
- Average time to close pull requests: about 15 hours
- Issue authors: 1
- Pull request authors: 1
- Average comments per issue: 3.0
- Average comments per pull request: 0.5
- Merged pull requests: 2
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- cmcooling (2)
Pull Request Authors
- jaydesl (4)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- line_profiler *
- numba *
- numpy *
- pandas *
- scipy *