reiserlab / component-designs Goto Github PK

Try to set up a working version of FicTrac in parallel to reading the paper.

The production of a detailed step-by-step assembly protocol is one of the goals we defined for the project. In this task we find a place where we can develop and disseminate the document.

We talked about different options in the past week. They included just another page on the github page, a protocols.io document, an instructables website, or a preprint. As part of this task, let's set up a test document with a few paragraphs and see how well we can work with it.

Could this work as an alternative for a commercial product? https://www.thingiverse.com/thing:174398

The goal of this task is to keep the documentation up to date with the state of the setup.

As a result, the step-by-step guide might contain the following information:

• complete Micromanipulator build instruction
• instructions on how to set up FicTrac (what we learned from #12 and #15)
• instruction on how to set up and power the illumination
• previously known issues with laser-cut parts and what we learned from it
• complete camera modification steps

Document formatting (eg via paragraph styles) could help improve readability. How can we improve the figures (eg creating figures with sub-panels, different type of alignment…)? All this is up for discussion.

Change the format of walkingsetup_order.csv to be similar to tethering_order.csv. This might include changing the liquid template in Inexpensive-Treadmill.md

The goal is to not have any redundant information in the csv without loosing information on the website.

We would like to run FicTrac and collect data from the PS3 Eye in 187 fps mode on Windows, without a VM. We are able to get FicTrac to recognize the camera and collect data, using PSEyeDriver installed on top of CLEye. However, this configuration operates in the higher resolution 640 x 480 mode and caps out at ~75 fps.

(We are able to run FicTrac in a Linux VM in the low res camera mode)

Currently, the heat pad is positioned via a makeshift left over. Find a better way to mount the heat pad.

In the lab, there is a screw glued to the heat pad, but maybe there is a better way?

The component list currently has the 25mm lens, but for the new setup 6mm should work fine.

Prints and slices fine; this is a low priority fix. The model seems to have an error at the junction between post and base.

From this weeks work it became obvious, that generating a shopping list to replicate the setup is more laborious than I had hoped.

in this issue we can discuss how this could be improved.

The goal is to run experiments with previous tested display protocol to confirm display efficacy and data collection accuracy.

Add thread to air feed, to be used with something like this: https://www.mcmaster.com/51235K107/

Mount all components for walking and tethering setups on baseplate.

The goal of this task is to verify that FicTrac is working properly. Some short *.dat file would verify that everything works as expected.

To reach this goal, the following steps might be necessary:

• Install FicTrac software
• paint sphere with pattern
• set up sphere holder and air pump
• have the PS3 camera working with IR light
• set up illumination via LED
• configure FicTrac via configGui
• run FicTrac for 5 seconds to record the *.dat file

Add a suggestion to regulate the light intensity for the NIR illumination.

(task takem from presentation page 25)

Currently, the raw image from the PS3 camera is shown upside down. Find a way to orient the image correctly.

One corner of the stl file has non-manifold geometry and is ignored by my slicer.

Modify the top rail to use less support material. This could be achieved by moving the mounting plate to a different location.

The top rail requires a lot of support under the long side of the cage if printed in the suggested direction. The presentation identified this as a potential issue and waste of material.

Currently the laser cutting service costs $150, more than half of what everything else costs. Find a cheaper way to do this, possibly using 3D printing instead of introducing a separate technology stack.

This is a task derived from the lab meeting presentation, page 14.

Produce a first working Micromanipulator from the self-printed parts.

• Act on all comments on the google document.
• create images with panels
• share folder with original images and panelized versions

(this task is taken from presentation page 38)

Micromanipulator top rail (up/down axis) has a tendency to torque when turned. Reducing this tendency will be especially helpful for the tethering setup.

Things to try:

• Conduct qualitative torque test with one nut vs two nuts
• Add in solid body where print supports usually occur in rail production (also removes need for support)

Find a problem on the website and fix it – or add some new information to it.

Part of this task is to find out how to work with the github pages, write documentation, and find a way to communicate with each other.