This is the official repository for the seminar project and master's thesis project supervised by phseidl, which encompasses two distinct groups: drug-discovery and EEG (Electroencephalography) research. This mono-repository is designed to facilitate coordination, teach version control, and collaboration between you all.
Meetings: every Monday 14-15:00 SP13 S318 or via zoom (except holiday, or stated in the issues page)
Voluntary ML4Drug-Discovery-Journal-Club of our Institute: (almost) every Tuesday 13-14:00 zoom
Most important thing: your results should be reproducible and therefore well documented!
- Project Overview
- Directory Structure
- Getting Started
- Contributing
- Version Control
- Code Style
- Communication
- Disclaimer
This repository hosts the codebase and related resources for two parallel research streams:
-
Drug Discovery:
-
EEG (Electroencephalography) Research:
By maintaining a mono-repository, we aim to streamline collaboration and ensure consistent version control practices.
/drug-discovery: Contains code, data, and resources for the drug-discovery group./eeg-research: Contains code, data, and resources for the EEG research group.
Within the projects a suggestion would be:
*/individual/surname: for your own stuff*/external/: for external repos*/src/: for shared source code*/notebooks/: for shared notebooks (or within your individual folder)*/scripts/: for scripts to run
-- please all try to mentain a README for both projects
each individual project should have a setup.py and a env.yml, README.md, PROGRESS.md, I will provide a base, which you can modify.
To get started with this project, follow these steps:
-
Clone the repository:
git clone https://github.com/phseidl/jku-ml-seminar23
-
Select a paper Papers will be in a folder within the two groups in ````.*/data/papers/``, you can also propose your own paper for the seminar.
Each group is responsible for their own codebase and should follow their established contribution guidelines within their respective subdirectories. Collaboration between groups is encouraged, and any cross-group collaboration should be discussed and documented. Code Style It's essential to maintain consistent coding and documentation standards within each group's codebase. Refer to the specific code style guidelines provided in your group's subdirectory.
We use Git for version control. Make sure to follow Git best practices, create branches for feature development or bug fixes, and use descriptive commit messages.
It's essential to maintain consistent coding and documentation standards within each group's codebase. Refer to the specific code style guidelines provided in your group's subdirectory.
Preferably via github ;)
THIS IS WORK IN PROGRESS -- OPEN FOR SUGGESTIONS