Guide


Contents

This page is intended to house documentation for lab members that describes the nuts and bolts of how the lab functions. It's primary purpose is for on-boarding new members, but is also a reference for current members. For this page to be useful, all lab members will need to provide their collective knowledge and experiences. It is up to all of us to make this guide useful. You are expected to contribute to the guide and edit it. Discuss with the lab any desires to change any of the guidelines.

Getting Started

  • Join the lab communication channels:
  • Send an introduction email to the lab email list: who you are, a bit about yourself, what you will work on, etc.
  • Add your name and portrait to the lab members page by sending a PNG or JPG 300px x 400px portrait to Jason or by submitting a pull request on Github.
  • Setup regular mentorship meetings with your mentor(s). This should at least be a weekly or biweekly depending on your needs and the mentor(s) recommendations.
  • Attend biweekly lab meetings. Ask a lab member for the calendar invite with the video chat link. Add your ideas and votes for meeting topics to the google document (ask Marco for permissions to edit).
  • Send out an AIO (see below) before your regular mentor meetings.
  • Get campus card access to the bicycle lab and bicycle lab storage (if needed). These can be requested from Jason. Ask for a tour of the space from a current lab member before you start working there.
  • See the recommended reading list below for some reading materials to get you started.

Internship

After you have found an internship, typically on your own but sometimes through postings via the lab, here are some things you need to do:

  • Review the Study Guide explanation of your internship, for example:
  • Review the assessment rubric for the internship and the associated report: https://wbmt2.tudelft.nl/organisatie/formulieren/msc/3me-msc-assessmentcriteria__internshipreport.pdf
  • Fill out the MSc internship initiation form with your project description and other relevant information. Develop this project idea with your internship company contacts. If you think this aligns with Jason's research interests or the internship came through the bike lab you can send the form to Jason and ask him to be your TUD advisor. If he agrees, then you can obtain his signature on the form and forward it to your respective MSc coordinator.
  • Make all of your internship arrangements yourself with the company (travel, stipend, housing, etc.)
  • To receive academic credit for your internship at the end you need to write a report and have it assessed by your TUD internship supervisor. The report will be assessed based on the above linked rubric.
  • Note that your TUD supervisor is typically not involved in your internship other than the signing the initial form and assessing and providing a grade at the end.

Getting Started on the Literature Study

MSc Thesis

COVID-Time Lab Rules

Use of the bicycle lab for hands-on project work is allowed as long as 3mE allows this type of work inside the building. Check with Jason for the up-to-date rules if in question. The current lab rules are:

  • All the University rules and 3mE rules apply and the following rules are in addition to those.
  • No more than 6 people working in the lab at any given time. If you need to visit the lab briefly and there are 6 people present, ask if the people present are comfortable with you entering when arriving.
  • You are expected to maintain 1.5 m distance between everyone present in the lab and use face masks when you are not seated.
  • If you are sick, stay home and get tested. Let others you were in contact with know immediately of possible or confirmed COVID infection to prevent spread.
  • Take the virus seriously and respect everyone's health needs/wishes. Everyone should feel comfortable if using the space. Communication is key for this.

Communication

Lab Email List

When you join the lab you should request access to the lab email list:

https://groups.google.com/forum/#!forum/mechmotum

This can both be used by everyone as both an announcement list and a discussion list. All lab members need to join and pay attention to this list for announcements and are welcome to use if for discussion.

Text, Audio, Video Chat Room
We host a matrix server which can be accessed using https://element.io or any other supported clients. This is used for quick chats, meetings, etc. We'll keep the chat histories around, but its best to treat the data as transient. Lab members can use as needed for lab related communication.
Issue Trackers

We make heavy use of issue trackers on Github and Gitlab to communication. This is good for topic oriented, long form discussion that needs permanency, organization, and/or task control. General lab issues can be tracked in this repository (in addition to the website issues):

https://github.com/mechmotum/mechmotum.github.io

Quarterly Blog Posts
In general, we would like each project to write regular blog posts for the lab website. These posts should describe updates on project progress and results. This writing exercise will help build the content for future papers and theses and provide outreach to the public about our work. It is helpful to do these on a schedule (quarterly, semi-annually, etc.) so that the get done. If your project is of a proprietary nature, you'll need to select aspects of the project or work that can be shared or embargo the blog post to a later date. Discuss these things with your supervisor.

AIO Weekly Emails

Lab members are expected to send out AIOs to their supervisor(s) and any project collaborators you meet with during your regular meetings.

"AIO" stands for Accomplishments, Issues, and Objectives. This email should contain three bullet lists:

  • what you or your team accomplished in the previous week,
  • what issues you encountered during that week and would like help with, and finally
  • what your objectives are for the coming week.

The purpose of these are to share what you are doing with your daily supervisor and anyone involved in your project outside the lab. Some notes:

  • If you are working in a team you can send out a single AIO for your team.
  • The AIOs do not need to be elaborate, concise is best.
  • No need to list your hours worked or who did what in teams.
  • It is ok, and preferred, to reply-all if you want to comment on an AIO with a suggestion so everyone can learn and discuss.
  • The AIOs are not a contest. Your supervisor is not collecting these to judge how much you accomplish, but they do care that you are working, attempting to make progress, and communicating with your lab members for help. If you had vacation that week or just didn't have much time to work, that's fine, just note that.
  • If you need help via with issues, you need to provide enough detail for the reader to understand the problem.

The AIOs should be sent the day of your meeting with the supervisor. It can be before (we can use it as an agenda) or after if you prefer to work on the issues with me and then post outstanding ones and the revised objectives post meeting. Some students like to leave the objectives blank and add them after meeting with the supervisor. However you do it, each week the accomplishments should hopefully reflect the objectives you wrote the previous week.

Laboratory Meetings

We meet every two weeks as a lab, where we will have a designated person (picked in advance at random in our very own weighted raffle) take the proverbial stage and share and teach any topic that can be useful in our academic endeavors.

The topic can be anything bicycle or research related. It may be content-related, soft-skill related, practical-skill related or harking to your personal interest in bicycles. It might be an expertise or skill you have, but also be a skill or software program you want to learn. Co-presenting is fine (and a great way to meet your peers) provided your topics align. Options galore:

  • 10-20 minute presentation with Q & A
  • tutorial
  • have us read something (a paper) we could review
  • watch and discuss a video
  • invite a speaker
  • play a game
  • practice your colloquia or conference talks
  • bicycle-themed stand-up
  • etc.

Members are expected to attend and participate regularly. It's fine to miss a meeting here and there, but avoid making that regular. If the meetings are not useful to you, please be proactive about helping us make them useful for all.

Past Meeting Topics and Materials

Title Date Presenters Materials
Learning to stand with unexpected sensorimotor delays 2021-09-28 Patrick Forbes https://elifesciences.org/articles/65085
Robot bicycle overview 2021-09-28 Tim Huiskens Slides
Welcome back 2021 Q1, Browser-only Mechmotum website update 2021-09-14 Rado Dukalski  
Optimal Control in Biomechanics 2021-05-03 Joris Ravenhorst, Jan Groenhuis, and Jason Moore Slides
Balance and stability in elderly 2021-04-22 Leila Alizadehsaravi  
Introduction to Eline's Lab 2021-04-07 Eline de Kruk  
BioMechanical MSc Guide Review 2021-03-25 Eline van der Kruk, Jan Groenhuis, & Jason Moore  
Bicycle-rider perturbations & Bump’em 2021-03-11 Jelle Haasnoot & Shannon van de Velde  
Data Management 2021-02-11 Leila Alizadehsaravi & Rado Dukalski & Marco Reijne  
Bicycle Handling Qualities 2021-01-28 Julie van Vlerken & Jason Moore Slides
Bicycle Accidents and Crashes 2021-01-14 Joris Kuiper & Marco Reijne  
Bicycle Trainers 2020-12-17 Jelle Haasnoot & Rado Dukalski  
Introduction to Git and Github 2020-12-03 Tim Huiskens & Jason Moore Slides
BMX Racing 2020-11-19 Jan Groenhuis & Marco Reijne  
Introductory Meeting 2020-11-05 NA NA

Research Ideas

Specific MSc project advertisements can be found on the jobs.

Check out our research ideas Github repository to read, post, and discuss new ideas:

https://github.com/mechmotum/ideas/issues

Have a look at current and past projects on the research page

Open Science

The default science and engineering practice from the lab should be open practices (open access publications, open source software, open data, accessible and public sharing etc.). If unsure whether to make information public, ask, otherwise please default to sharing early and often. We do work with organizations that value or require privacy (human subject data, student protected data, proprietary company needs). Always check with the involved parties before sharing when this is the case. This is something that should be discussed at the beginning of all projects.

TU Delft offers several resources for open science:

Research Tools Contributions

Researcher have to use and develop a variety of tools to complete their work. For example, we will develop experimental equipment and software often in the lab. Many tools are potentially useful to other people inside and outside of the lab. Lab members should build on and contribute to the tools we use and develop in the lab. There is a general expectation to create and contribute to open source software and open hardware efforts while working in the lab.

Lab Website

The lab website is a Pelican based static website hosted through Github pages. The source for the website is here:

https://github.com/mechmotum/mechmotum.github.io

Lab members should help collectively maintain and update the website. Please use the Github pull request mechanism to submit changes for review. As long as one lab member reviews the pull request and approves the changes, the changes can be merged. Keep in mind that content here should reflect the whole of the lab.

Software Tools

Reference Management

The lab has a shared Zotero group which can be used for lab related reference management (currently 20 GB plan). Zotero is an open source reference management system backed by a consortium of libraries. Create an account and request membership to the mechmotum group. Note that all lab members can view the contents of this library.

Version Control

The lab currently has group accounts on Gitlab and Github for version control of text based sources (software, text, etc):

The services are more or less interchangeable. We used Gitlab in the past because it provided free unrestricted private repositories, but Github does now too. Gitlab's core software is open source. You may prefer the features of one service over the other.

Lab members should be able to make use of version control and communication through these services. The Software Carpentry Git lesson is a recommended introduction. Create an account on one or both services and request group membership.

Private repositories are private for a reason. If you gain access to private repositories in the two organizations you are expected to keep the private and not to distribute the files in any way. Ask your supervisors if you'd like to share something that is set to private.

Lab Space

Inventory

There is a common spreadsheet on google drive that lab members should use to track our non-consumable inventory (tools, devices, expensive stuff, computers, etc). Anytime you buy something add it to the spreadsheet. The spreadsheet can be accessed at this link:

https://docs.google.com/spreadsheets/d/1w80SolpcLTbLtuFDIf9-F-sS_pO-1PEHSpSgEGH_SSg/edit?usp=sharing

Ask Jason if you don't have permissions for this file.

Training

It is important to both learn the tools, methods, and techniques used in the lab and to teach the lab new things you've learned so we can collaborate efficiently and effectively.

Useful TU Delft MSc Courses

Multibody Dynamics B
Core high level dynamics principles that are the foundation for almost every project in the lab.
Special Topics Course in Sports Engineering
TU Delft organizes an annual two week course to train students in sports engineering. Cycling has been used as the motivating topic to learn the methods.
Musculoskeletal Modelling and Simulation ME41005
Learn how to develop and utilized computational neuromuscular models with OpenSim. Many projects in the lab make use of neuromuscular and biomechanical modeling.

The Carpentries Trainings

Each lab member will need to learn the collaborative software tools and open source development practices needed to work on code and other text based sources together. Carpentries trainings (Software Carpentry in particular) is a great way to get started on this. TU Delft offers regular courses:

Sign up by emailing Femke van Giessen (F.vanGiessen@tudelft.nl) to register for a slot. You will be directed to an Evenbrite. Sign up on Eventbrite immediately because these typically fill up in 10 minutes and there are large wait lists.

Writing Help

TU Delft Writing Center
Schedule a meeting with a writing coach to get advice on your thesis or other documents.

Connecting to Research Communities

We regularly participate in several research communities.

Online

Biomech-L forum
A 30+ year old public discussion forum to connect to the international Biomechanics community. Lot's of great scientific discussions.
Single Track Vehicle Dynamics listserv
Public email based forum for discussing the dynamics and control of single track vehicles.

Conferences

PhDs and Postdocs should submit to and present at conferences each year, if possible. MSc and BSc students are also encouraged to do so if resources allow.

Bicycle and Motorcycle Dynamics Conference
This conference is the most closely related to the bicycle lab's core research in single track vehicle dynamics, handling, and control. The conference series ordinated with Arend Schwab and his colleagues and was launched in 2010 in Delft. The lab should make a strong effort every three years to submit to and be involved in this conference.
International Cycling Safety Conference
This is the next most important conference to be involved in. We should aim to have at least one or two submissions to this conference each year.
ECCOMAS Multibody Dynamics Conference
This is a good conference for presenting topics that focus in multibody dynamics methods.
International Sports Engineering Conference
This is the best conference to submit sports engineering topics. It is held every other year. There are likely many other TU Delft participants, especially through the Sports Engineering Institute.
International Society of Biomechanics Congresses
Huge annual conference with a broad array of biomechanics topics. Great networking and a catch all for many topics from the lab. Every two years.
SciPy & EuroSciPY
Annual conferences. If your work involves open source Python software these are a great place to showcase the advances in library development and use of the tools.

Funding Opportunities

Dekker-Padget Internshiup Program: Dutch2USA
Funding for minority or economically disadvantaged college students to do an internship in the USA.
Veni
The Veni is part of the NWO's Talent Programme. It is the first of three personal grants. Postdocs in the lab that plan to continue in academia should apply for this. Final year PhDs are also encouraged to apply too. If you get this grant, you will gain a strong advantage in moving your academic career forward in the Netherlands. If you don't, you'll have practiced developing your personal research vision and goals, which is also extremely valuable.