This issue will be used to collect information to decide on a coronavirus policy for working in the Bicycle Lab physical space.

• Students in a class have to have permission from the teachers to be in the building for course work
• "some small scale graduation work cannot be moved online and can take place"
• research in an adopted form
• work done in fixed small groups

• people in room judged by the space to support 1.5m distancing

• Project work, limited number tutorial sessions, and some Master activities will be organized for on-campus.

https://d1rkab7tlqy5f1.cloudfront.net/corona/coronamaatregelen_tudelft_july_students_EN_01.pdf

https://www.tudelft.nl/en/ae/news/information-coronavirus/education-study/

An example: http://ivory.idyll.org/lab/coc.html

It'd be nice to have a custom lab logo. If anyone has some artistic skills and the lab name inspires them, post some sketches here for discussion.

• get new monitors for the lab
• make a student project cabinet(s), flexible space where new students can claim a shelf and add their label
• organize the tools in the tool cabinets, use dividers, bins, labels, and other organizational methods
• sort all nuts, bolts, things in the plastic bins with labels
• make 6 workstations
• remove all raw materials to basement in organized fashion, make at least one raw material shelf that is labeled
• get rid bad bicycle rims and tires in the basement (probably metal recycling and trash for tires -> talk to Jan v. F.)
• fold up the mock hexapod bike and store in basement (make sure it can be reassembled with instructions)
• hang interesting bikes on the wall (talk to Jan v. F. for permissions required)
• move all bicycles to the basement that are not in active use in the lab or up there for display/demo purposes
• hang tools on the toolboard (label or make a silhouette of the tool so they end up back in right spot)
• clear old junk from all cabinets to make space

https://www.tudelft.nl/en/education/practical-matters/scholarships

Noticed these on the travis builds:

WARNING: Defining PLUGIN_PATHS setting as string has been deprecated (should be a list)

WARNING: %s usage in CATEGORY_FEED_ATOM is deprecated, use {slug} instead.

WARNING: Watched path does not exist: /home/travis/build/mechmotum/mechmotum.github.io/content/images

WARNING: Empty alt attribute for image fiets2small.jpg in /home/travis/build/mechmotum/mechmotum.github.io/content/spring-2003.rst

WARNING: Empty alt attribute for image bike2small.jpg in /home/travis/build/mechmotum/mechmotum.github.io/content/spring-2003.rst

WARNING: Empty alt attribute for image Bike3xrl.jpg in /home/travis/build/mechmotum/mechmotum.github.io/content/spring-2003.rst

WARNING: Empty alt attribute for image Bike3xRev.jpg in /home/travis/build/mechmotum/mechmotum.github.io/content/spring-2003.rst

WARNING: Other images have empty alt attributes

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/bicycle-handling-qualities.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/computational-thinking.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/about.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/members.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/bicycle-parameters.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/index.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/sympy-beam.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/guide.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/human-powered-water-pump.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/ski-jump-safety.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/jobs.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/resonance.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/bicycle-data-logger.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/quadriplegic-friendly-tricycle.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/libretexts-jupyter.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/optimal-handling-bicycle.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/products.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/standing-control-id.rst: Ensure exactly one top level section

WARNING: Document title missing in file /home/travis/build/mechmotum/mechmotum.github.io/content/pages/research/rowing-performance.rst: Ensure exactly one top level section

WARNING: There is no "sortorder" attribute in "pages/jobs/determining-dynamics-perception-thresholds-of-bicycles.rst". Defaulting to slug order.

WARNING: There is no "sortorder" attribute in "pages/jobs/fast-musculoskeletal-simulations.rst". Defaulting to slug order.

WARNING: There is no "sortorder" attribute in "pages/jobs/how-fast-will-open-source-break.rst". Defaulting to slug order.

WARNING: There is no "sortorder" attribute in "pages/jobs/optimization-based-bicycle-design.rst". Defaulting to slug order.

WARNING: More files are missing the needed attribute.

WARNING: Unable to find '/implementation-of-ebike-speed-controller.rst', skipping url replacement.

WARNING: Unable to find 'ebike-speed-controller.rst', skipping url replacement.

Seems pelican spits out errors but the CI doesn't fail.

They will likely disappear otherwise.

• sort all nuts, bolts, things in the plastic bins with labels
• Get new monitors (and HDMI/DP adapters) [there is an open request for this with the secretaries]
• make 6 workstations
• Get rid of excess bicycle rims and tires (stacked beside the floor bicycle rack)
• hang interesting bikes on the wall (talk to Jan v. F. for permissions required)
• remove all raw materials to basement in organized fashion, make at least one raw material shelf that is labeled
• organize the tools in the tool cabinets, use dividers, bins, labels, and other organizational methods
• move all bicycles to the basement that are not in active use in the lab or up there for display/demo purposes
• send some unneeded bicycles to the kringloopwinkel
• inventory all the bicycles in a spreadsheet
• make a student project cabinet(s), flexible space where new students can claim a shelf and add their label
• fold up the mock hexapod bike and store in basement (make sure it can be reassembled with instructions)
• hang tools on the toolboard (label or make a silhouette of the tool so they end up back in right spot)
• clear old junk from all cabinets to make space
• setup method for checking out tools from the lab (for lab members that need to use the tools outside the lab or for other labs borrowing our equipment)
• Make space for the large treadmill (likley move cabinets)
• organize all cabinets, shelfs, drawers, etc. with labels and such
• Utilize the small parts bins for organization
• Develop an inventory list of things that are 250 EUR or greater in price (spreadsheet in the shared GDrive)
• Install a lab equipment check out list on the wall by the door
• Get rid of the excess bicycles in the basement (all of the ones grouped in the floor rack).
• Organize and label shelves in the basement.
• Move materials under the workbench to the material shelf in the basement.
• Remove homeless keys from the bicycle key box. Label all keys for current bikes. Make sure bikes are locked in the basement.
• Move the large treadmill into the bicycle lab.
• Label the fall mats in the basement with "bicycle lab"
• Dismantle the ice skate measuring device and store the materials in the rack in the basement
• Get rid of the walking treadmill (or service it)
• Order a broom

We could make a page dedicated to this and showing their logos, etc. Or we could add them to each project page. Or both.

I picked https://github.com/gfidente/pelican-svbhack to start with. We can either pick a different theme, create a new one, or modify this one.

Premade pelican themes can be viewed here:

http://www.pelicanthemes.com/

We like to find something that fit the name of the lab. I'm not stuck on the current one at all.

• https://www.eurobike.com/en/
• https://iccss2020.com/
• http://cyclingresearchboard.com/2021/
• This group holds a conference: https://science-cycling.org
• nacob.org
• Velocity
• https://ioc-preventionconference.org/ IOC WORLD CONFERENCEON PREVENTION OF INJURY & ILLNESS IN SPORT
• world congress of biomech every 4 years https://www.wc-biomechanics.org/congresses

• The computer graphics community (SIGGRAPH) always has videos that explain their papers. These are very effective communication tools.
• Steve Collins does a good job of this: https://biomechatronics.stanford.edu/other-videos

The lab website certainly has weaknesses in presenting itself as welcoming to diverse new members. It would be helpful to improve that and give a clear and honest picture of that for prospective new members.

Some ideas:

• Make a diversity statement that explains our values
• Code of conduct
• Provide mentorship
• Have lab attend trainings

Google Drive? Surf Drive? Nextcloud on our server?

The students may not have enough experience making a plan (or knowing how long tasks will take). Some guidance that helps them budget time better for specific tasks would help.

It would be nice to have a web page that shows of the major equipement that we have avilable in the lab. For example, the bicycle simulator, the various instrumented/actuated bicycles, specialized measurement tools, treadmills, etc.

Tasks:

• Take nice photos of each item to list
• Resize the photos to something reasonable (600x600px or so) and name them to unique lowercase "kebab-case".
• Create a new hidden page rst file called "Facilities" (or maybe there is a better word)
• Design the page layout
• Link to the page from relevant top level pages on the website

• BMD/BME MSc students that would like more community in their MSc graduation process should sign up for the new “Graduation Community Program” by March 6th, 2022 (email coordinators for more info). This looks like a nice way to get advice on succeeding through your graduation internship, lit study, and project. I recommend checking it out.
• BMD MSc students now have some new excellent guidance documents with flowcharts available on the "Master Biomedical Engineering" Brightspace course under "ALL STUDENTS - Flowcharts & Guidance Docs". The ones for BMD will be created in the coming months and will be very similar. So if you are BME definitely look at these and if you're BMD I recommend checking them out too. Anyone that is supervising BME or BMD students should also get familiar with them.
• MSc students should continually be aware of the latest forms on these two pages. These are the official and sole sources from here on out. We will always use the latest forms at the time the form is needed:
• https://www.tudelft.nl/en/student/faculties/3me%E2%80%90student%E2%80%90portal/education/related/student%E2%80%90forms/msc%E2%80%90forms/
• https://www.tudelft.nl/en/student/faculties/3me-student-portal/education/related/student-forms/internship-forms

We are looking into Element (backed by matrix).

Needs:

• Display a reference list for all of the lab's research products.
• Include all research products created by lab members while a member of the lab. Would be nice if this went back in history to Arend's launch of the bicycle efforts.
• Link to all PDFs and other relevant file types without limits of paywalls and journal websites etc.
• Auto-update on build when new items are in the Zotero collections.

pyzotero and zot_bib look useful for this

I tried setting the background color to all of the secondary colors listed here:

https://www.tudelft.nl/en/tu-delft-corporate-design/colours/

The only one that seemed to work (as a simple swap) was #abc6d8. It looks like this:

Should I make the change?

Just had a talk with Joris about how to get started on a literature study and realized this will be repeated for each student. We should develop a getting started document for this.

The lab guide needs more information and thoughtful pieces.

List of some inspiration from others:

• Eric Gilbert's PhD Student Syllabus https://docs.google.com/document/d/11D3kHElzS2HQxTwPqcaTnU5HCJ8WGE5brTXI4KLf4dM/edit (most is good advice, I don't agree with all of it though).
• Titus Brown's lab page has some interesting guide elements: http://ivory.idyll.org/lab/
• Katy Huff has a lab manual: http://arfc.npre.illinois.edu/manual/
• Reddit post with tips another profs gives: https://www.reddit.com/r/AskAcademia/comments/13ura10/useful_resources_for_the_development_of_your/

https://www.globalcyclingnetwork.com/

I'd like to leave them up for historical reasons though, instead of just removing them when students take them on.

It would be very nice to have photos of everyone on the website.

• Jason
• Arend
• Joris
• Shannon
• Julie
• Marco
• Jan
• Tim H.
• Patrick
• Mandeepika
• Noah
• Tim S.
• Junda
• Rado
• Leila
• Jelle

Add some form of this to a page:

I'd like to have you all send out AIOs to the lab group each week. If you've had me for EME 185 you now what these are.

"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.

You should send it to [email protected] and cc anyone not in the lab that is involved in your project.

The purpose of these are to share what you are doing with me, anyone involved in your project outside the lab, and also to share among the lab members. The latter is the most important one, because many of you may be solving similar problems and can offer help/tips to other members. Doing this will hopefully start conversations among the group. Some notes:

If you are working in a team you can send out a single AIO for your team.
No need to list your hours worked or who did what in teams.
The AIOs do not need to be elaborate, concise is best.
It is ok, and preferred, to reply-all if you want to comment on an AIO with a suggestion so everyone can learn.
This is not a contest. I don't care how much you accomplish, but I do care that you are working and attempting to make progress. If you had vacation that week or just didn't have much time to work, that's fine, just note that.

The AIOs should be sent the day of your meeting with me. 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. However you do it, each week the accomplishments should hopefully reflect the objectives you wrote the previous week.

I want this to be useful to us all. If you have feedback to improve, or think it is useless burden, tell me and we can discuss better ways to accomplish things.

This is what I think I need to do:

• Create a new dreamobject user for the lab.
• Add two keys: one for me and one for lab members (that I can revoke if ever needed).
• Migrate the mechmotum bucket from my personal dreamobject user to the fietslab user.
• Make the key available to lab members so they can run the dreamobject.py script.

There is a new standard agreement we must sign for all students that work with a company.

We need a page that lists the labs products:

• publications
• software
• teaching materials
• ?

Here is some info I got from the Valorisation office.

From Irene Otten-Reynhout [email protected]

Without taking any actions, if a master or bachelor student starts working in your department doing a project (eg part of his thesis project), the IP that the student generates is owned by the student. The student has nu obligations at all (also no confidentiality etc).

As an employee of TU Delft, TU delft owns the IP that the employee generates.

Research projects are often carried out in collaboration with third parties. Agreements concerning IP are prepared by the contract managers. In general: IP belongs to the party that generates the IP. If an employee (eg you) generates results, TU Delft owns this IP. Depending on the contribution of a company he can have certain access rights (eg licence).

Before a specific student project will start, you should always contact Sjoerd/ John and together with them they will have a look what will be the best option:

1. Signing an NDA
2. Transfer of his IP rights to TU Delft
3. Do nothing

What you should not do:

Do not sign NDA’s, contracts etc by yourself. This is not allowed. Only the dean of the faculty is allowed to sign. Therefore, if you receive an NDA (or a company is requesting this), please ask Sjoerd and John

and from Sjoerd van Kesteren [email protected]

In addition to Irene’s e-mail, please note that when it concerns a master graduation project, a mandatory TUD graduation agreement template is to be used (a three party agreement between TUD, company and student). Students can download the draft version from the student portal (a new version is to be released shortly).

The basic principles in the graduation agreement are that the students results are transferred to company. Any results generated by TUD (through e.g. the supervisor) are the sole results of TUD. In case of joint IP of a combination of TUD, the student or the company, TUD is a joint owner. The company will have the possibility to purchase or license TUD’s IP against a market price. TUD does not have any claim to company’s IP.

Furthermore, company may request (and is automatically granted) an embargo for max 2 years. Additionally, an extension of 3 years (so 5 year max) can be requested with TUD’s board of directors (which may grant or deny this in its sole discretion). For sake of completeness, TUD accepts a confidentiality period of max 5 years and confidential information needs to be marked or summarized as such.

I'm taking over the "TU Delft Bicycle Lab" and will transition away from "Laboratorium of Marvelous Mechanical Motum". This website will stay in tact and be hosted at bicycle.tudelft.nl. Arend and I will each have bicycle.tudelft.nl/schwab and bicycle.tudelft.nl/moore, but the main site will be this one.

• Change the name of the lab on the website
• Merge Arend's old blog posts into from http://bicycle.tudelft.nl/schwab/Bicycle/ this blog reel
• Update members page to include both Arend and me as PIs and lab members at TU Delft (present and past if possible)
• Should I change the Github org name and the repo name? Could become bicycle-lab/bicycle.tudelft.nl or fietslab or ...
• Include all references on the product page from Arend and my lab
• Make sure the whole site is https
• Setup hosting the website at https://bicycle.tudelft.nl
  • Create scripts that ensures existing directories hosted at bicycle.tudelft.nl can be overwritten or added to via this pelican build.
• Add TU Repository, and title and links of each thesis

Wishes

• preserve bicycle.tudelft.nl/schwab
• backup the old index.htm (top level)

See this issue: getpelican/pelican#2489

I have yet to get it debugged on Travis. So I'm using the old slug spec and Pelican < 4 currently.

I tried removing the svbhack theme on Travis and it still failed.

See: http://labcarpentry.org/

Things to implement:

• Code of conduct
• add more here as we go

https://urc.ucdavis.edu/PUF

See: https://github.com/regro/regolith

This would be an alternative to Pelican. It is a small project but targeted to research labs.

Add notes here:

• We need a general lab policy for data in the lab
• Have to deal with company's prop data.
• Everyone can use 500Gb on Surfdrive, could be an option for timely backups (and/or sync)
• Every new PhD has to create a data management plan, see https://www.tudelft.nl/en/library/research-data-management/r/plan/data-management-plans
• Require data backups of computers on regular basis to external place.
• Every computer hard-drive should be encrypted
• Passwords should be different and very secure
• Careful about using sync services for backup
• Always have a "do not touch original data" backup elsewhere. Far far away :))
• Certain data can't be stored on non-EU servers (or non-NL)

https://www.nwo.nl/en/calls/rubicon-2022-3

There has been some new activity in the last years at:

https://github.com/nairobilug/pelican-alchemy

I tried merging in the changes and it merged pretty cleanly with only one minor conflict, but there is a new default theme based on the bootswatch changes that were made. I need to use the old style but the screenshot of the old style looks like the whole background is grey instead of the lower white section and upper grey section. Some adjustments may need to be made.

• Costs less than 50 euro should be bundled and submitted together at the end of the month. Costs > 50 euro can be submitted anytime.
• Where to submit claims?
• What codes are used?
• Who approves the claims?

• We need to show who we work with and have worked with.
• We need to show off what equipment and skills might be useful to industry and other orgs.
• Need some guide to show them how to connect with us.
• Explain basics of IP issues so they can see how that might work.

Marco made this comment:

Depending on the audience, if not only academic but you are also interested in the general public, I like the website of Eric Maris (from Radbout University, Nijmegen) where he tries to explain the neuroscience related to cycling in plain language.

It would be nice to follow this "LabCarpentry" idea. And example is Titus Brown's lab website: http://ivory.idyll.org/lab/index.html

Just sets up expectations, guidelines, and instructions.

Google Drive

TU Delft offers G-Suite access to any TUD netid. Go to drive.google.com and login with [email protected]. More info

Nextcloud

We could run our own nextcloud instance on a server. The server we use for element may not be ideal because it may not have much storage space. If I can get the server in the lab exposed publicly to the internet we could run Nextcloud on it.

Surfdrive

Surfdrive would be good. You can even collaborate on documents like in GDrive, but students don't get access. Each item has to be individually shared with students with a unique password.

Onedrive

TU Delft offers this and it's connected to Teams somehow.

Organizations

• Cycling Research Center in Spain: https://cycling-research.com/
• Urban Cycling Institute: https://urbancyclinginstitute.com/
• Dutch Cycling Research Center: http://www.crcbikeposition.be/nl/

Journals

• Journal of Science and Cycling: https://www.jsc-journal.com/index.php/JSC/about
• Human Power eJournal: https://www.hupi.org/HPeJ/

Initiatives

• https://www.tno.nl/en/focus-areas/traffic-transport/roadmaps/smart-and-safe-traffic-and-transport/smart-vehicles/making-bicycles-cars-and-intersections-intelligent/
• https://cyclingresearchreview.com/

Conferences

• https://cyclingresearchboard.com/2020/ (Oct 26 2020)