The chart below will tell you (approximately) what to expect when looking through a microscope with varying combinations of eyepieces and objective lenses. As an example (in green below), a dual power stereo microscope with 10x eyepiece lenses and 1x and 3x combinations of objective lenses, would have total powers of 10x and 30x and your field of view would be 20mm and 6.7mm respectively.

Field of view microscope40x

Other considerations: The working distance is the distance from the bottom of the microscope (lens) to the part of the specimen that is in focus. As you increase the magnification, you decrease the working distance. If you need to work under the microscope, you will need a large working distance. Some special microscopes have extended working distances for these purposes. Zoom microscopes have a fixed working distance throughout the zoom range. When using a 100x objective lens (1000x total power) your working distance might only be 0.04mm (40µm). The lens will be extremely close to the specimen! The working distance and the amount of vertical motion of the microscope will also affect the maximum specimen height. Maximum specimen height is how tall an object you can put on the stage and still be able to focus on the top part of the specimen.

Microscope field of view diameterformula

I was able to make this work when there was no angle on the conveyor belt through layout bindings but there is no option to bind to only a corner and not the sides. Plus you can’t rotate template instances which would make this easy.

High power microscopes usually have 10x eyepieces lenses, so there is only one column above the 4x objective. If you wanted to look at an amoeba that is 150µm long (0.15mm) then you would use either the 40x or 100x objectives. There are 25mm in an inch and there are 1,000um (micrometers) in a single millimeter.

This means that an object 20mm (2cm, or about 3/4 inch) wide would fill up the whole viewing area at 10x and an object about 6.7mm wide would fill up the whole area at 30x. As you can see, having the highest power may not be best for your particular application. When you move to greater magnifications, you sacrifice field of view.

Microscope field of view diameterpdf

Ok so I actually managed to make it work without the paintable canvas. I used lines instead of squares for the center as stroke size doesn’t change and then bound them to all 4 sides. The only caveat is that it doesn’t line up at 30 degrees by expanding the template size with ctrl + resize. To make it line up where I want to I just align it with the edge of square template in the center.

This page with pennies at different magnifications might be helpful to get a visual idea of what you can see at different magnifications.

My best guess on how to do this is either through an objectScript() function or through a paintable canvas. The only issue with the paintable canvas is that when I was testing out load times it took significantly longer on initial load to boot using a paintable canvas versus a svg(with flashy graphics). Maybe I’m using them wrong then I’m not really sure.

Microscope field of view diametercalculator

Yea that makes the most sense. Thank you. So with the paintable canvas is it best to use component functions to creat the different shapes then call those functions in the repaint or how is it best to organize the code? Also is it possible to only have the canvas repaint the specific part that needs animated?

Edit: I’m not really sure why mine was so slow then. I must have had a tag being read or some really inefficient code. I did have a bunch of separate canvases that couldve been combined into one. That might have been the reason.

Field of view microscopeformula

What I am trying to do is to get center lines and background “bound” to the top left and bottom right corners without distorting the width of the lines and background so everything lines up correctly. I know I could technically do this through property change event but the issue with that is that it will only run in the client so that won’t do plus you can’t reference a template instances width or height.

Field of View or Field Diameter is very important in microscopy as it is a more meaningful number than "magnification". Field diameter is simply the number of millimeters or micrometers you will see in your whole field of view when looking into the eyepiece lens. It is just as if you put a ruler under the microscope and counted the number of lines.

Edit: That doesn’t work as good as I had originally thought. I got to actually using it at work and trying to manipulate the line positioning and size which was pretty terrible to work with. Especially when the lines were layered on top of each other as I would try to select one line and press right where the line is, not the stroke but the actual line, and a good part of the time it would select something else entirely, or I would need to displace where I press to select it. Plus the angle positioning wouldn’t scale correctly with the template to top that off so I decided that the hassle of lining up the components wasn’t worth it. I guess there is a good reason that this isn’t a widespread use case of lines.

Nothing in the paintable canvas should really be slow as long as you’re using it ‘right’ - make sure you’re at most checking property references in repaint() - if you try to execute any system functions to read a tag, query a DB, etc, you’re going to have a very bad time.

Microscope field of view diametertable

Get a metric ruler and place it on the stage of your microscope. Illuminate from above (if you are using a compound microscope, get a transparent ruler or illuminate it with a flashlight). See how many millimeters you can see from left to right. What would be the field of view of this image? (Answer located at bottom of page).

Plus once I thought about it a paintable canvas is property driven to where it only runs the script when a property changes while a svg(color change) is expression driven to where it changes the property based on the conditional, which runs much more often. So it should be that as long as I am not animating it constantly it will be much faster, though I haven’t tested it. Edit 2&3: Grammar