OpenFlexure Microscope

A 3D printable microscope, including a precise mechanical stage to move the sample and focus the optics. There are many different options for the optics, ranging from a webcam lens to a 100x, oil immersion objective.
https://gitlab.com/openflexure/openflexure-microscope

Category: Biosphere
Sub Category: Biodiversity Citizen Science

Keywords

Open Science Hardware

Keywords from Contributors

3d-printing assembly-instructions microscope openscad electronics gerber pcb kicad

Last synced: about 18 hours ago
JSON representation

Repository metadata

A 3D printable microscope and translation stage

https://gitlab.com/openflexure/openflexure-microscope/blob/master/

          # OpenFlexure Microscope
The OpenFlexure Microscope is a  3D printable microscope, including a precise mechanical stage to move the sample and focus the optics.  There are many different options for the optics, ranging from a webcam lens to a 100x, oil immersion objective.

![3 views of the microscope](docs/images/microscopes_wide.jpg)

The trick of making a microscope out of a webcam has been around for a little while, and produces good results.  However, getting a nice mechanical stage to focus the microscope and move around on the sample is very difficult.  This project is a 3D printable design that enables very fine (sub-micron) mechanical positioning of the sample and the lens, with surprisingly good mechanical stability.  It's discussed in various [media articles](https://openflexure.org/about/media-publications).

If you use the OpenFlexure microscope in your work please consider citing one of our papers:

* *Robotic microscopy for everyone: the OpenFlexure microscope*, [Biomedical Optics Express **11** 2447 (2020)](https://doi.org/10.1364/BOE.385729) (open access).
* *A one-piece 3D printed flexure translation stage for open-source microscopy*, [Review of Scientific Instruments **87**, 025104 (2016)](http://dx.doi.org/10.1063/1.4941068) (open access).

## Building a microscope
For up-to-date build instructions, STL files, and pre-built Raspberry Pi SD images, please head to the [build a microscope page].

[build a microscope page]: https://openflexure.org/projects/microscope/build

## Instructions
The latest release of our assembly documentation can be found from the [build a microscope page] on our website. The editable instructions are Markdown format (built using [GitBuilding](https://gitbuilding.io)), in the [docs folder](./docs/) of this repository. If you have a problem accessing the images after cloning the repository see the section on LFS files below.

## Printing it yourself
Configure your microscope hardware and download the STL files through the [microscope STL configurator] page.  The [assembly instructions](https://build.openflexure.org/openflexure-microscope/latest) contain instructions on print settings and putting it together.

If you've built one, let us know. You can let us know on [our forum](https://openflexure.discourse.group/), add yourself to the [wiki page of builds](https://gitlab.com/openflexure/openflexure-microscope/wikis/Assembly-Logs), or submit an [issue](https://gitlab.com/openflexure/openflexure-microscope/issues/new) marked as a build report.  This is a really helpful for us even if you don't suggest improvements or flag up problems.

[microscope STL configurator]: https://microscope-stls.openflexure.org

## Come join us!
Most of the development of this design has been done as part of various research projects - if you would like to join our research groups in [Glasgow](https://www.gla.ac.uk/schools/physics/staff/richardbowman/) or [Bath](https://researchportal.bath.ac.uk/en/persons/william-wadsworth), and you have funding or are interested in applying for it, do get in touch.  Check the jobs sites for the Universities of Glasgow and Bath, or findaphd.com, to see if we are currently advertising any vacancies.  The team is bigger than Glasgow and Bath, there are contributors in Cambridge, Dar es Salaam, and beyond.

## Kits and License
This project is open-source and is Released under the CERN Open Hardware License, strongly reciprocal, v2.0 or later (CERN-OHL-S-2.0) (CERN-OHL-S, see the License file).  The OpenFlexure Project doesn't sell micrscopes, but several companies do, you can find a [list on our website](https://openflexure.org/about/vendors).

## Get Involved!
This project is open so that anyone can get involved, and you don't have to learn OpenSCAD to help (although that would be great).  Ways you can contribute include:

* [Join our forum](https://openflexure.discourse.group/)
* Share your microscope images (of both microscopes and what you've seen with them) on social media - you can mention @openflexure on Twitter, @openflexure.bsky.social on BlueSky, or have us add you to [our map](https://openflexure.discourse.group/t/where-are-you-ofm-location-survey/771/last).  
![](https://canada1.discourse-cdn.com/free1/uploads/openflexure/optimized/2X/1/170f0e188fed108e467e25203d93ea08a0483d55_2_690x479.jpeg)
* Suggest better text or images for the instructions.
* Improve the design of parts - even if you don't use OpenSCAD, STL files or descriptions of changes are helpful.
* Fork it, and make merge requests - again, documentation improvements are every bit as useful as revised OpenSCAD files.

Things in need of attention are currently described in [issues](https://gitlab.com/openflexure/openflexure-microscope/issues/) so have a look there if you'd like to work on something but aren't sure what.

## Developing
If you want to play with the OpenSCAD files or change the documentation, you should fork the repository.  You can edit the documentation online in GitLab, or clone the repository if you want to edit the OpenSCAD files.  You will need to clone the whole repository as the OpenSCAD files are dependent on each other.

### Changelog
The changelog can be generated using `python generate_changelog.py`. In future, this should be used to keep the changelog up to date for each new release.

### Development environment
We mostly use VSCode to edit the OpenSCAD files, and then use OpenSCAD with the editor hidden and the "automatic reload and compile" option ticked.  This is much nicer for a big multi-file project like the microscope than relying on OpenSCAD's built-in editor, and also works nicely with version control.

### Automatic builds
The build system is based on Python and Ninja, see [compiling](COMPILE.md) for more details.

### Release flow
We use GitLab CI to manage builds and deployment.

The CI will build STL files that will remain on GitLab for 1 week when:

* A merge request is submitted
* A merge request is modified

The CI will build and deploy STL files and documentation to [build.openflexure.org](https://build.openflexure.org/) when:
* A build is manually triggered from GitLab web
* A release is tagged

The build server will mark a release as "latest" ([build.openflexure.org/openflexure-microscope/latest](https://build.openflexure.org/openflexure-microscope/latest)) when a release is tagged, with a full semantic version and no suffix. For example:
  * v6.0.0 will replace "latest"

However, incomplete semantic versions will not replace latest. For example:
  * v6.0.1-beta.1 will **not** replace "latest" (pre-release suffix)
  * v6.1 will **not** replace "latest" (no patch version specified)
  * 6.0.1a will **not** replace "latest" (non-standard suffix)

### LFS files

This repository stores images using Git LFS. This means that cloning the repository without Git LFS installed will only download placeholders for the images. Follow these instructions to [install Git LFS](https://git-lfs.github.com/).

With LFS installed Git will download the latest version of the images used in the documentation. If they are still missing try running:
```
git lfs fetch
git lfs checkout
```

## Related Repositories

Other repositories relating to the Openflexure Microscope are in the [OpenFlexure GitLab group](https://gitlab.com/openflexure).  Particularly useful ones are:

* [OpenFlexure Microscope Server](https://gitlab.com/openflexure/openflexure-microscope-server). This is the software that runs on the microscope.
* [OpenFlexure Connect](https://gitlab.com/openflexure/openflexure-connect). The recommended client software for controlling the microscope. The repository is mostly device discovery code, with the interface handled by the server.
* [OpenFlexure Microscope Python Client](https://gitlab.com/openflexure/openflexure-microscope-pyclient). This allows you to control a microscope from a python script.
* [OpenFlexure Delta Stage](https://gitlab.com/openflexure/openflexure-delta-stage). A 3-axis stage for microscopy that keeps the objective in a fixed position.
* [OpenFlexure Block Stage](https://gitlab.com/openflexure/openflexure-block-stage). A higher precision 3-axis stage with a smaller range.

Repositories for compatible motor controllers:
* The ["sangaboard" motor controller](https://gitlab.com/filipayazi/sangaboard-rp2040) (and its [firmware](https://gitlab.com/filipayazi/sangaboard-firmware)). This is the standard motor controller for the microscope. It was developed collaboratively with Filip Ayazi and based on the legacy controller that was developed in collaboration with [BTech in Tanzania](https://btech.co.tz/), see below.
* The legacy ["sangaboard" motor controller](https://gitlab.com/bath_open_instrumentation_group/sangaboard). This contains Arduino IDE compatible firmware for the [workaround motor controller using an Arduino Nano](https://build.openflexure.org/openflexure-microscope/latest/workaround_motor_electronics/workaround_motor_electronics.html).


A number of other related projects include:

* [micat](https://gitlab.com/bath_open_instrumentation_group/micat) For microscope calibration
* [PiCamera CRA Compensation](https://gitlab.com/bath_open_instrumentation_group/picamera_cra_compensation/) Contains hardware and software for colour calibration of a Raspberry Pi camera.
* Some [characterisation scripts for analysing images of the USAF resolution test target](https://github.com/rwb27/usaf_analysis/)

Some OpenFlexure repositories still remain on [Richard's Github](https://github.com/rwb27/).

## Compiling from source
If you want to print the current development version, you can compile the STL from the OpenSCAD files - but please still consult the documentation for quantities and tips on print settings, etc.  You can use Ninja build to generate all the STL files (run ``pip3 install -r requirements.txt`` and then ``./build.py`` in the root directory of the repository).  More instructions are available in [COMPILE.md](COMPILE.md).

        

Owner metadata


Committers metadata

Last synced: 5 days ago

Total Commits: 2,418
Total Committers: 37
Avg Commits per committer: 65.351
Development Distribution Score (DDS): 0.72

Commits in past year: 220
Committers in past year: 4
Avg Commits per committer in past year: 55.0
Development Distribution Score (DDS) in past year: 0.223

Name Email Commits
williamwadsworth w****h@b****k 678
Julian Stirling j****n@j****k 612
Richard Bowman r****n@c****t 532
Kaspar Emanuel k****l@g****m 178
millirowland m****3@b****k 70
Richard Bowman r****4@b****k 64
samuelmcdermott s****3@c****k 57
Florian Festi f****n@f****o 53
Joel Collins j****l@j****t 39
Joel Collins 2****2@u****m 25
jtc42 j****2@g****m 22
Martin Budden m****n@g****m 9
Filip Ayazi f****i@g****m 8
GraceAnyelwisye g****e@o****m 8
Thomas Bourke 1****1@u****m 8
Joe Knapper j****r@h****m 7
Kaspar Emanuel k****r@m****k 7
Joe Knapper j****4@b****k 6
Just_a_Lonely_Traceback_Error w****7@i****m 5
Beth Probert b****t@s****k 4
Bill Schaller b****r@f****m 4
orgemd o****n@i****g 3
Jenny Molloy j****2@g****m 2
Kaspar Emanuel k****r@k****g 2
Theo Sanderson t****o@s****k 2
William Wadsworth p****w@b****k 2
Beth Probert b****t@o****m 1
Brian Degger b****r@g****m 1
Cash TingHin Lo c****n@g****m 1
Darigov Research h****o@d****m 1
and 7 more...

Committer domains:


Issue and Pull Request metadata

Last synced: 5 days ago


Dependencies

requirements.txt pypi
  • colorama ==0.4.3
  • ninja ==1.9.0.post1
  • pylint ==2.6.0
scripts/zenodo/requirements.txt pypi
  • PyYAML ==5.3.1
  • requests ==2.23.0

Score: 8.462948176563842