RESOURCE GUIDES
Choose courses, research software and practical tools
Start with the work you want to do: analyse a recording, understand a method, or build a small measurement prototype. A clear task makes it easier to compare the learning and tools you need.
Use these checklists to assess an option before spending time or money. Write down your constraints and evidence for each choice; revisit them when your project changes.
Choose a course around a useful outcome
For a first signal-analysis project, look for a course that takes you from loading a permitted dataset to explaining a result. Compare the depth of the syllabus with your existing maths, programming and domain knowledge. A certificate and a practical learning outcome answer different needs.
Before you choose
- Prerequisites and syllabus: identify the maths, Python and domain concepts you need, the topics actually taught, and the time required for exercises.
- Practice and feedback: check whether code and datasets are accessible, assignments produce a reusable output, and feedback is human, automated or peer-based.
- Teaching language: distinguish the original teaching language from translated subtitles or dubbing; inspect a sample lesson and any specialist terminology.
- Access and cost: verify the current provider terms, certificate charges, subscription renewal, course access period and refund rules. Compare free auditing or open materials when available.
Choose research software you can reproduce
Select software for a specific data format and method. For example, electrophysiology analysis and general machine-learning experiments involve different assumptions and validation steps. A working example with your own permitted test data is more informative than a feature list.
Before you choose
- Fit and licence: confirm supported data formats, required methods, and the licences of the software, dependencies and example data; check whether your intended use is permitted.
- Reproducible environment: record package versions, operating system and installation steps. Run a small example and save the environment alongside the code and random seeds.
- Maintenance and support: review release notes, documentation, issue handling and upgrade guidance. Plan how to preserve a working version if an update changes an API.
- Alternatives and full cost: compare an open-source or free option with any paid service, including hosting, storage, export formats and the effort needed to migrate your work.
Choose hardware for a defined measurement
Begin with a bench task such as recording an environmental sensor or synchronising a signal with an event. Define the range, sampling needs and acceptable error before choosing parts. This guide covers educational and research prototyping in nonclinical applications.
Before you choose
- Measurement and budget: specify the quantity, range, sampling rate, accuracy and total budget, including sensors, cables, power supply, enclosure and replacement parts.
- Compatibility: verify operating voltage, connectors, interfaces, drivers and software support for your computer or board. Check the complete data path with a small prototype.
- Documentation and availability: look for schematics or pinouts, a usable example, manufacturer documentation and a practical source of spare parts in your market.
- Seller terms and safe use: verify local delivery, returns, warranty and applicable instructions for electrical, battery or mechanical hazards. Human-connected or clinical applications need their own requirements and validation.
Keep a short decision record
A one-page comparison is enough to make the reasoning visible. Use the same task and criteria for each option, and mark anything you have not verified.
-
Define success
Write one sentence describing the output you need, then list constraints such as available time, language, data access, computer capacity and budget.
-
Try a small example
Preview a lesson, run a minimal script or test one sensor. Record what worked, what failed and what you still need to learn; keep free alternatives in the comparison.
-
Check the current terms
Confirm the provider or seller details before committing. Record the date, source and reason for your choice so that another person can assess it later.
Start with the original documentation
These free documentation links are examples for evaluating a workflow. Select the method and software version that fit your data, and verify installation and licences in the relevant project.