-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design for Upgraded VAMPIRES #11
Comments
I think a focusing optic right before all of the dichroic stuff is a recipe for disaster, what if instead we used really long focal lengths? Option 2a: Collimating After - Front FaceOption 2b: Collimating After - Rear FaceThere's some more ringing at the rear, which is to be expected, but it really isn't TOO different. Note that these data are taken at more than twice the sampling of the new VAMPIRES sensors at ~1.8um, so these effects will be averaged out anyway. Going to try out the same situations with less sampled data. |
Option 2a: Using 5.3um pixelsOption 2b: Using 5.3um pixelsThere's the averaging. I suspect that the non-sequential group creates a bit of an error in the pupil solve, so we could actually decrease this effect by translating the lens to be a little out of what zemax tells us is focus. I also think that since this ringing is not polarization-dependent, PDI will clean it up nicely. |
The Lenses used for these simulations |
The orca quest pixels are 4.7um |
@mileslucas I don't have exact control over the pixelscale, that was just the closest I could get using zemax's jump in pixels 🙃 There's a workaround, just haven't implemented |
Quick Survey of Available LensesThe simulations above use lens # 1 but I could only find one other achromat of the same clear aperture from thorlabs.
|
@mileslucas I think mechanically it'd be nice to go to a 350mm lens because the above lenses require pretty close spacing to the VAMPIRES objective (~5mm I think), but I can't find any achromats. Is spacing two lenses together by 5mm too close? We can build out the mounting hardware, but it's more of a problem if there are mechanics immediately above the lens. Is there stuff in the red zone here? |
You won't be able to mount anything there because the tube holding the dichroics needs enough clearance for 180° of rotation. If the lens could fit on a motorized flip mount or rotation mount close to the objective lens, it could probably get mounted together in the same post on a platform or something. |
I think the idea is that it was on a motorized stage to switch between
imaging and pupil-imaging. So as long as it isn't toggled at the same time
as the dichroic stack rotation, it should be fine right?
But maybe that's another interlock that needs to be built in. Otherwise the
lens groups might accidentally do a meet-cute and run into eachother.
…On Mon, Oct 17, 2022 at 4:17 PM Miles Lucas ***@***.***> wrote:
*External Email*
You won't be able to mount anything there because the tube holding the
dichroics needs enough clearance for 180° of rotation.
If the lens could fit on a motorized flip mount or rotation mount, it
could probably get mounted together in the same post as the objective lens.
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGC7XBEKXSPXHL55XZEBQMLWDXM7XANCNFSM6AAAAAAQQPA2ME>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The other option is to use a 350mm lens to get some additional clearance,
but then we are limited to singlets so the chromatic aberration is a little
worse.
On Tue, Oct 18, 2022 at 8:05 AM Jaren Nicholas Ashcraft <
***@***.***> wrote:
… I think the idea is that it was on a motorized stage to switch between
imaging and pupil-imaging. So as long as it isn't toggled at the same time
as the dichroic stack rotation, it should be fine right?
But maybe that's another interlock that needs to be built in. Otherwise
the lens groups might accidentally do a meet-cute and run into eachother.
On Mon, Oct 17, 2022 at 4:17 PM Miles Lucas ***@***.***>
wrote:
> *External Email*
>
> You won't be able to mount anything there because the tube holding the
> dichroics needs enough clearance for 180° of rotation.
>
> If the lens could fit on a motorized flip mount or rotation mount, it
> could probably get mounted together in the same post as the objective lens.
>
> —
> Reply to this email directly, view it on GitHub
> <#11 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AGC7XBEKXSPXHL55XZEBQMLWDXM7XANCNFSM6AAAAAAQQPA2ME>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Dr. Strangeoptics Or: How I learned to stop worrying and tolerate the POPThis is a more comprehensive characterization of the lens above we will be using as a collimator. The cases we are interested in are the effective pupil produced by the different paths taken through the dichroic stack. The Setup sans collimatorStrehl Ratio v.s. FoV: Keep in mind the FoV is over-specified because the spectral data isn't being dispersed in this direction
The Setup with collimatorChose the Thorlabs lens mostly for the clear aperture, it's an inch so I think its more compatible with thorlabs mounting hardware. The specifications on anti-reflection coating between the two seem very similar so the choice is somewhat arbitrary. The paraxial pupil position is only 40um past the original image plane in this configuration so we are doing quite well. How does it look? The point spacing of the following data is ~5um, so VAMPIRES will be slightly more resolved than this. First Dichroic Surface
Second Dichroic Surface
Third Dichroic Surface
Rear Mirror Surface
SummaryTotal dPosition from the image plane when the first surface of the dichroic is in the focal plane of the collimator
This analysis shows a couple of things
If we defocus the lens to match the middle dichroic stack, how separated are the pupils?I can't really get the system under multiconfiguration control so there isn't a concise way of showing this data. So here's a bunch of side-by-side footprint plots. Unfortunately there's some partial overlap between the spectral beams. I can only think of a couple solutions if we want a Spectro-polarimetric pupil mode.
|
@mileslucas any thoughts before the vampires meeting today? |
How stopped down does it need to be for option 1? For option 3, could a dichroic beamsplitter cube work or a set of differential filters in the diff filter wheel? Or where does this notch filter have to go? |
O1: Just by eye, I think we'd have to stop down by ~50% in the worst case O3: It could, it's just a little weird because you can't image the beam from D2 at the same time as D1 or D3. If there was a filter that sent D2 to one sensor and D1/D3 to the other sensor - then I think it could work. How do the differential filters work? I was thinking the notch filter would have to go where the rest of the filter wheels go. |
Actually based on this simulation I want to amend what I said. I think D1 and D3 could be imaged at the same time. I also think D2 and D3 could be imaged at the same time. But D1 and D2 are a little too close. |
In this case, you could put a notch filter in the transmissive beam of the differential wheel, and the inverse notch filter on the reflected beam of the differential wheel. This could be used with the polarizing beamsplitter and you'd have to switch the wheel back and forth 180 degrees (same way the h-alpha and continuum filters dance around to remove NCPA). |
Another thing you might consider for prototyping this is that the dichroic tube that is being custom-machined has different (closer) spacing than the zemax files you have. For reference, the average spacing between each dichroic/mirror is ~2mm. This could potentially make your job easier (or maybe harder!). |
Oh hey they might be strictly better in terms of imaging the pupil
also - will be missing the meeting today to go to a jwst colloquium
…On Thu, Nov 3, 2022 at 3:20 PM Miles Lucas ***@***.***> wrote:
*External Email*
Another thing you might consider for prototyping this is that the dichroic
tube that is being custom-machined has different (closer) spacing than the
zemax files you have. For reference, the average spacing between each
dichroic/mirror is ~2mm.
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGC7XBGA3UFZGZ36WHILH53WGQ3EDANCNFSM6AAAAAAQQPA2ME>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Check the actual overlap, apparently it might be wrong. |
Miles updated the FoV calculation so now everything is feasible! yay!
Option 1: Collimating lens before Miles' lens
This option could introduce a lot of wavefront aberrations that are hard to see using Zemax because the pupil is quasi-focal. Luckilly, it doesn't seem to corrupt the simulated pupil image for the on-axis case.
TODO: Simulate how multiple pupils influence the resultant pupil image.
The text was updated successfully, but these errors were encountered: