BeadTracker issueshttps://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues2016-12-06T16:31:10+01:00https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/27Binary Files: No readout tool.2016-12-06T16:31:10+01:00Edo van VeenBinary Files: No readout tool.*Created by: daimonie*
Apparently, the option to write Binary tools was used in the past by Jelmer Cnossen only; there no longer is an available readout tool.
Sam and I discussed this, and found that the apparent reason writing binar...*Created by: daimonie*
Apparently, the option to write Binary tools was used in the past by Jelmer Cnossen only; there no longer is an available readout tool.
Sam and I discussed this, and found that the apparent reason writing binary is faster is mostly that it writes less data, because it neglects special characters (e.g. \t) and the motor info.
As such, this has little priority. Even so, it must be done at some point (or the option needs to be removed).https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/26Incorporating force-distance information into MotorUI2016-11-25T12:21:04+01:00Edo van VeenIncorporating force-distance information into MotorUI*Created by: samleachman*
One thing that surprised me about this lab is that force-distance determinations are done outside LabVIEW, either using Richard's ForceInfo tool or a graph taped to the wall. The average force is a sum of two e...*Created by: samleachman*
One thing that surprised me about this lab is that force-distance determinations are done outside LabVIEW, either using Richard's ForceInfo tool or a graph taped to the wall. The average force is a sum of two exponentials of the distance with empirically determined weights and decays. The distance can be calculated from the force in advance with a look-up table (with 0.01 mm precision or similar) or using LabVIEW's numeric solver. Incorporating this is crucial to implementing constant loading rate (pN/s) experiments, where you need to find the velocity to move the magnets. If you get around to this, I can share the code I used to implement this on my old setup in Berkeley.https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/24Reorganisation2016-12-05T11:23:54+01:00Edo van VeenReorganisation*Created by: daimonie*
Testing is made extremely hard by missing and badly organised dependencies.
In trying to make the ResultManagerTest, I needed a dependency that left me trailing to multiple directories. What's up with that. Als...*Created by: daimonie*
Testing is made extremely hard by missing and badly organised dependencies.
In trying to make the ResultManagerTest, I needed a dependency that left me trailing to multiple directories. What's up with that. Also, note that the C++ code does not call for proper dependencies itself but rather depends on visual studio supplying the paths; otherwise, it bugs.
While understandable, the bad resource management makes it very hard to add proper debugging and I consider it something that must be dressed, possibly combined with a reorganisation of the code so that it is also somewhat sensible where what file is found.https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/20Standardised Algorithm Test2016-11-09T11:55:19+01:00Edo van VeenStandardised Algorithm Test*Created by: daimonie*
Standardised Tests are something I want to look into at some point.
- I'm thinking of a test similar to Cheezum for any algorithm (by using an Adaptor pattern on any implementation of the algorithm).
- Sta...*Created by: daimonie*
Standardised Tests are something I want to look into at some point.
- I'm thinking of a test similar to Cheezum for any algorithm (by using an Adaptor pattern on any implementation of the algorithm).
- Standard protocol to test labview+C++ using tethered beads
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/15200ms delay in motor updates2016-11-09T11:08:41+01:00Edo van Veen200ms delay in motor updates*Created by: jwassenburg*
The motor positions are only probed and saved 5 times per second. As such, interpolation of the motor positions is required to find the position at every frame.
Would getting the position more often severely i...*Created by: jwassenburg*
The motor positions are only probed and saved 5 times per second. As such, interpolation of the motor positions is required to find the position at every frame.
Would getting the position more often severely impact performance?
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/14Error handling (long-term)2016-11-09T11:08:51+01:00Edo van VeenError handling (long-term)*Created by: jwassenburg*
Implement better error handling. At the moment, whenever a crash occurs for whatever reason, LabVIEW crashes entirely and any unsaved changes to settings or beads are lost.
First:
Instructions for users how to...*Created by: jwassenburg*
Implement better error handling. At the moment, whenever a crash occurs for whatever reason, LabVIEW crashes entirely and any unsaved changes to settings or beads are lost.
First:
Instructions for users how to handle crashes.
0. Save settings, beadlists, LUTs before starting the next step
1. Always press stop if an error occurs and make a screenshot of the error message
2. Send the screenshot of the error message to me, along with a short description of what you were doing when it happened
3. Fully exit LabVIEW
4. Run again
Eventually:
Catch errors as they occur without allowing LabVIEW to crash on them.
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/130-point magnet rotation2016-11-09T11:09:08+01:00Edo van Veen0-point magnet rotation*Created by: jwassenburg*
Implement a possibility to set the current rotation as the 0-point, just like you have for the magnet height.
Sam:
when you switch magnet heads or during initial alignment, and maybe if your motor is turned wh...*Created by: jwassenburg*
Implement a possibility to set the current rotation as the 0-point, just like you have for the magnet height.
Sam:
when you switch magnet heads or during initial alignment, and maybe if your motor is turned while off, you'll need to re-align the magnetic field with the image. This is important for proper force calibration but also to ensure consistent lighting. Currently, I think you need to align in BeadTracker, close LabVIEW and open PI MikroMove, and reset the magnet there.
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/12CUDA crash D018R2016-12-13T18:30:06+01:00Edo van VeenCUDA crash D018R*Created by: jwassenburg*
Mariana:
we got a program crash 3 times in a row when I wanted to take a LUT with the CUDA running. Once I disabled the CUDA everything worked fine again.
Speedtest works with CUDA.
*Created by: jwassenburg*
Mariana:
we got a program crash 3 times in a row when I wanted to take a LUT with the CUDA running. Once I disabled the CUDA everything worked fine again.
Speedtest works with CUDA.
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/11QTrk dll location confirmation2016-12-07T09:54:28+01:00Edo van VeenQTrk dll location confirmation*Created by: jwassenburg*
On many setups, when starting anything that requires the QTrk DLL, LabVIEW asks for a confirmation of the location of it.
*Created by: jwassenburg*
On many setups, when starting anything that requires the QTrk DLL, LabVIEW asks for a confirmation of the location of it.
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/10Real-time image size2017-01-11T14:21:16+01:00Edo van VeenReal-time image size*Created by: jwassenburg*
Request by Richard:
Look at a larger display possibility for the real-time image display. Especially for the 12MP camera the current size is quite small. For example, clone in seperate window.
*Created by: jwassenburg*
Request by Richard:
Look at a larger display possibility for the real-time image display. Especially for the 12MP camera the current size is quite small. For example, clone in seperate window.
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/9Script parsing . or ,2016-11-09T11:26:49+01:00Edo van VeenScript parsing . or ,*Created by: jwassenburg*
Recognize numbers with both . and , in the script parsing.
*Created by: jwassenburg*
Recognize numbers with both . and , in the script parsing.
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/8Scrolling in script editbox2016-11-09T11:26:59+01:00Edo van VeenScrolling in script editbox*Created by: jwassenburg*
Is it possible to include a sidebar/mousescrolling control on the script editbox in ExperimentProgramUI.vi?
*Created by: jwassenburg*
Is it possible to include a sidebar/mousescrolling control on the script editbox in ExperimentProgramUI.vi?
https://gitlab.tudelft.nl/nynke-dekker-lab/public/BeadTracker/-/issues/7Set magnet position as offset2016-11-09T11:27:08+01:00Edo van VeenSet magnet position as offset*Created by: jwassenburg*
Add button to MotorUI.vi to set current magnet position as offset.
*Created by: jwassenburg*
Add button to MotorUI.vi to set current magnet position as offset.