AOtools / aotools

A useful set of tools for Adaptive Optics in Python

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Units of phasescreens put out by the aotools.turbulence.phasescreen.ft_sh_phase_screen function

phillips-r opened this issue · comments

Greetings,

I'm poking around with aotools some and I am having a little trouble understanding what the units are on the phasescreens put out by the aotools.turbulence.phasescreen.ft_sh_phase_screen function. In some places in the documentation, it seems to refer to the units are radians but then in other places it seems to refer to the units as nanometers of wave front deviation per unit length. Can anyone clear this up?

Hi @phillips-r,

The units from the phase screen creation functions, including aotools.turbulence.phasescreen.ft_sh_phase_screen are definitely in radians. We should certainly write this into the function docs! Can you point us to where its indictated that it may be in nano-metres?

Thanks!

Andrew

Andrew,

Thanks for getting back so quick! I'll hunt down where the docs are unclear and get back to you. Is there a per unit length assumed with the phase screens? As in "radians per meter" etc?

Andrew,

appologies for getting back so late. I was able to track down where I found that and it seems to be in a couple of the places like "optical_propagation.ipynb" in the AOtools_tests section where there is a figure after input 5 that implies the units are "wavefront deviation (nm)".

Can you confirm for me what the unit length scale is on the phase screen measurements? They're in radians, but radians per unit what? meters? kilometers? Thanks again for this great tool!

Hi @phillips-r,

OK - Thanks for digging this out. We can have a look and make sure it clear where the units are radians and where its in metres. We'll keep this issue open until its sorted.

Radians in phase screens are always a little confusing.

The phase screens are in "radians of a wavelength", so it depends on what wavelength you are considering. If you are assuming r0 is specified at 500nm (which is normally standard), then that implies that if you get a value of 2pi in the phase screen, there is 500nm of path difference at that point. If you wanted to convert your phase screen to nm then, you must multiply by 500 / (2 pi). However, when you're building an "electric field" from the phase screen, for instance to use in some optical propagation algorithm, then the phase needs to be in units of radians of wavelength.

Does this help?

Andrew

I've now changed labels in that notebook - @matthewtownson will run the notebook through again and upload so that the figure caption actually changes...

I will re-run the notebook to update the plots. Thanks for updating.

Updated the notebook, all docs and examples should now be consistent - units of phase screens are radians.