This wiki page is a guide to use the Differential Image Motion Sensor Using Multiapertures (DIMSUM) instrumentation that was installed to Aux Tel between December 6th and 16th. I am currently writing this as a wiki page to be able to get feedback during the process of documentation. Once everything is finalized I can create a pdf file if requested.
Description Of Instrument
The purpose of this instrument is to take pictures of an array of flashlights with a high speed camera while the AuxTel is taking data. Flashes are short enough to not create additional background light. The differential motion of the light sources calculated through the analysis of data can be correlated with the fwhm of the stars if the instrument works properly.
The instrument has two parts that wirelessly communicate with each other: the pegboard that holds the array of light sources powered by the Xenon Flash lamp inside the grey box and the camera connected to the computer. The procedure is as follows:
- The camera receives a command from the computer to take pictures.
- The remote flash trigger on top of the camera sends a signal to trigger receiver mounted to floor.
- The receiver triggers to flash lamp to light the sources up.
- The camera takes the picture of the light sources and downloads them to the computer.
- The pictures are written to the external disk through a script called python bash.
These steps are just a general overview of the steps. Below are the descriptions of operating the instrument with illustrations.
General Setup:
The camera connected to Macmini located near the table close to stairs.
The view of the pegboard from the location of the camera.
The view of the entire part of the pegboard.
Step By Step Instructions To Use DIMSUM
- Check if the MacMini is on. It should always be on, but someone may have unplugged it. If it is off, either unplugged or just not lighting up, turn it on.
- Take the lens cap of the camera. Make sure
- Turn the camera on. When the camera is on, there should be options visible on the small screen on top of the camera (not the flash trigger).
- Turn the flash trigger on. That is the object that is attached on top of the camera. It has godox written in front of it. Turn on the bottom switch. The top should stay off.
- After this step you are done with this part of the setup. Go to the pegboard part of the setup.
- Turn the flash receiver on. It should be attached to the floor under the pegboard. Make sure it is on group 01 and channel A
- Turn the power to the flash lamp on. That is done by switching on the green extension chord.
- This concludes the hardware part of the preparation. Further steps are software related.
ssh into the MacMini using
ssh stubbslab@auxtel-macmini03.cp.lsst.org
This works if you are on the summit. You will need vpn access if you are not on the summit. It may be good to open up two windows because two separate processes will run.
- 106McKay!
Once logged in create a directory for the observing run. You can name the file as you wish but it would be easier to track if naming would be in the form of mm-dd-yy_observing_run, thus if someone were to take data on January 17th 2023, the naming would be 23-01-17_observing_run. The command to create the file in the external disk would be:
mkdir /Volumes/LaCie/yy-mm-dd_observing_run
Once the directory in the external disk is created go to code directory using the command:
cd /Users/stubbslab/documents/strobed_dimm/code
Step 12 has been updated. Old instructions are available at the bottom of this point.
Set up the storage managing code. The images taken by the camera are initially sent to the computers local disk, then when a certain number of pictures accumulate, they are transferred to the external disk. 50 images is an ideal number to buffer. The storage management is automatically done by the script python_bash_updated.py. Once you are in the code directory run:
python python_bash_updated.py ./ /Volumes/LaCie/yy-mm-dd_observing_run/ 50 CR2
This is the way it is used for the context of DIMSUM, but the meaning of arguments are as follows:
path/to/source (where the files are internally saved), path/to/target (the directory of the external disk), number of files to transfer after, file type.
Old description for step 12
Set up the storage managing code. The images taken by the camera are initially sent to the computers local disk, then when a certain number of pictures accumulate, they are transferred to the external disk. 50 images is an ideal number to buffer. The storage management is automatically done by the script python bash. Once you are in the code directory run:python python_bash.py ./ /Volumes/LaCie/yy-mm-dd_observing_run/ 50 CR2
This is the way it is used for the context of DIMSUM, but the meaning of arguments are as follows:
path/to/source (where the files are internally saved), path/to/target (the directory of the external disk), file type, number of files to transfer after.- This code is an infinite while loop, when the command above is run, you will need a new window to run the image taking commands. Thus once step 11 is completed you need to opene a new terminal window. You may have to log in again.
Once logged in, go to code directory again using:
cd /Users/stubbslab/documents/strobed_dimm/code
Run the command:
./CommunicateTrial.sh
This will only take one burst, if you are taking data all night long you may want to modify the command using repeat N. A single burst approximately takes 11 seconds. For a 2 hour run repeat 900 would be enough. Repeat 900 command approximately takes 160 minutes to run. A single run approximately takes 11 seconds.
repeat 900 ./CommunicateTrial.sh
- Step 15 is updated. Old Version at the bottom of the new version. New version uses the script python_bash_updated.py and does not result in a problem of a single run with more than 10000 images.
Old Instructions for step 15
Run the command:./CommunicateTrial.sh
This will only take one burst, if you are taking data all night long you may want to modify the command using repeat N. A single burst approximately takes 11 seconds. For a 2 hour run repeat 900 would be enough. The 900 is a maximum for now because it may result in more than 10000 photos. If that is the case, the camera may overwrite the previous files. Thus for a run longer than 2 hours, first run the command:
repeat 900 ./CommunicateTrial.sh
When this is finished:
stop the python_bash script running on the other window (just hit control c).
Transfer the remaining files to the external disk. There will be remaining files because the script transfers them 50 by 50. You can easily transfer all the remaining files by:
python python_bash.py ./ /Volumes/LaCie/yy-mm-dd_observing_run/ 1 CR2
The steps below this is if the run is still going on after the repeat 900 command finishes executing. If the AuxTel run finishes before the 900 repeat finishes, just end the process using control c and transfer the remaining CR2 files to external disk using the command above.
Create another folder in the external disk named mm-dd-yy_observing_run_2:
mkdir /Volumes/LaCie/yy-mm-dd_observing_run_2
In the window that is used to run the script python_bash, run python_bash slightly changing the parameters:
python python_bash.py ./ /Volumes/LaCie/yy-mm-dd_observing_run_2/ 50 CR2
- Repeat step 14 until end if more data is needed. If not, stop both of the scripts when the run ends.
Transfer the remaining files to the external disk. There will be remaining files because the script transfers them 50 by 50. You can easily transfer all the remaining files by:
python python_bash_updated.py ./ /Volumes/LaCie/yy-mm-dd_observing_run/ 1 CR2
- Once the run is finished and all of the scripts are stopped. Go back to AuxTel and:
- Turn off the power to flashlight
- Turn off the flash trigger receiver.
- Turn off the flash trigger.
- After everything is done and you have
Troubleshooting
There may be errors while using the instrumentation. Below is a list of possible errors and how to fix them.
The camera is not detected by the computer although it is connected with all cables and is on.
This is a common problem, follow the steps below. Try the next one if the previous one does not work.
- Turn the camera on and off.
- Unplug the orange cable and plug it again.
The camera is on but does not see the pegboard, it is facing somewhere else.
The picture below is how the camera should be seeing the sources. If the camera is somehow not seeing this, or not seeing another part of the pegboard, it means it has moved.
This is the optimal view and getting this exact view without a screen nearby may be hard. However, it is possible to get the camera to be at least seeing the pegboard is possible by remote support.
To move the camera left and right:
- Loosen the screw at the bottom of the camera where it is connected to the L mount. The screw holding it should be a ¼-20 socket head screw. This means a ball hex key or a screw driver that is 3/16 of an inch could be used to loosen and tighten it.
- Once it is loose, rotate (azimuthally) the camera to a position where it sees the pegboard.
- Tighten the screw.
To move the view of the camera up:
- Loosen the screw
- Support the camera with your hand and lift it up.
- Tighten the screw when you are supporting the camera until it holds in its new upward position without your support.
Warning: While you are moving the camera you may have readjusted the focus. Do not forget the refocus or at least check whether the focus is still correct.
Flashes are not flashing but the camera is taking pictures. Pictures taken ended up being all black.
This is the most common error and means some part of the trigger system is not working. This may be caused by several things.
- Check that all the steps through 1 to 7 are correctly done. That is making sure the flash trigger is on, flash receiver is on, the power to flash lamp is on.
- If the receiver or the trigger cannot be turned on or do not show anything when they are turned off and on, replace their batteries. Spare batteries were left on the table close to staircase.(batteries were replaced with AC adapter in Dec 2023)
- Sometimes, if the camera was operated via EOS utility on the computer, it can be left in Live Mode. That needs to be off (affects mirror lock) in order for flash to trigger.
Flashes are flashing but they are clearly out of sync with the camera. Pictures taken ended up being all black.
This means that trigger receiver may be running on low battery. Replace its batteries.
The camera only takes one long pic.
This really should not happen but may be caused by 3 things:
- While turning on the camera, somebody may have changed the settings to Auto Focus or something else.
That wheel should always be on M. - Somebody changed the settings from high speed shooting to single shooting while debugging. This would be done by EOS Utility 3 software in the computer while somebody is trying to debug the focus. The squares with a subscript H on the top right corner of the screen on the right indicates high speeding shooting. If that indicator is anything else, switch it back to highspeed shooting.
- Somebody may have increased the exposure time to debug the focus using EOS Utility 3. Open Eos Utility and change the shutter speed to 1/200.
There is always an error occuring in script TakeImageCommunicate.sh and camera takes shots one by one.
This should not happen in any regular case unless someone who really knows what they are doing played with the controls. This happens when the mirror lockup is turned on. Turn mirror lock up off.
Analysis
See Software Analysis of Differential Image Motion For DIMSUM Vol 1 for the analysis of DIMSUM data.
Calibration (Stubbs, Jan 29, 2023)
We'd like to know the line-of-sight weighting function W(x/L) along the path from the source to the camera, for turbulence. For differential motion it vanishes at both ends, but for different reasons. At the source end, differential beam deflection does not affect the apparent position of the source, because the 'level arm' for image motion is too small. At the camera end, all rays go into the entrance pupil and so corrugations in index produces a wider PSF but no differential image motion.
If we introduce a beam deflector and move it along the optical path, we should be able to calibrate this weighting function. A complication is that different spatial scales are sampled at different distances, and the beams increasingly overlap as you approach the lens.
Any deflected rays need to get into the camera lens.
If we introduce a plexiglass wedge with angle theta, what's the deflection of the emerging beam vs. theta? Index of plexiglass is 1.49, so Snell's law says sin(theta_out)=1.49*sin(theta), and so for small-angle sin()-() approximation, deflection angle is just wedge angle*0.49.
Size of deflector area has to be at least as big as projected pupil size at that distance. Imagine a cylindrical surface on one side, flat on the other. If the surface has a radius of curvature R then y(x)=sqrt(R^2-x^2). Derivative is -2x/sqrt(...). Carrying this through to have deflection difference in two sources equal to 0.1 of their separation implies we want radius of curvature on one side to be of order 2*L, so about 20m. That assumes one side is flat, other curved. If it's a meniscus lens then we need differential curvature.
Thought about slumping, molding, and machining plexiglass for this. It seems machining and polishing is going to be fastest and easiest.
Polishing of acrylic:
Putting this in the beam and rotating it will produce a separation-dependent motion of sources. The tile difference is calculable. Also this leading order index perturbation, a wedge of index produces no observable differential image motion signal in our system, although it does produce common mode motion.
Feb 5 2023.
Crude calibration device:
Procured the following items from Amazon:
| Item | link | |
|---|---|---|
| 14 inch plexiglass disk 1.4 in ch thick | https://www.amazon.com/dp/B085ZQT2F8?psc=1&ref=ppx_yo2ov_dt_b_product_details |
|
| 30 rpm geared DC motor, 12V | https://www.amazon.com/dp/B071GTTX4D?psc=1&ref=ppx_yo2ov_dt_b_product_details |
|
| 12V power supply, fixed voltage | ||
| Motor mount | https://www.amazon.com/dp/B07BHDZH7Y?psc=1&ref=ppx_yo2ov_dt_b_product_details |
|
| Shaft-mount flange | https://www.amazon.com/dp/B00B887FX8?ref=ppx_yo2ov_dt_b_product_details&th=1&psc=1 |
|
| 12V supply | https://www.amazon.com/dp/B0B6W6S9JP?psc=1&ref=ppx_yo2ov_dt_b_product_details |
|
Motor mount holes are M3. Flange threads are 4-40.
Placed the plexiglass disk in the oven at home at 320F, which softens it enough to bend and mould. Rolled and mushed it to introduce surface variations and index changes.
Mounted the shaft flange onto it.
Motor then turns it so variations move across the beam.
To-do:
1) improve set screw connection to shaft of motor. Set screw kit ordered. DONE, CWS Feb 5, 2023.
2) drill out motor mount plate to allow mounting to a tripod, with 1/4-20 hardware. DONE, EKU, Feb 6, 2023
3) test it out in lab. For Canon 6D we can take video, and use MATLAB optical flow tools to process it. Be sure to use highest resolution video capture and ALL-I compression option. See https://thepointsguy.com/news/united-pqp-deposit/ /
Lab tests:
Set up tests with an LED and a bifurcated fiber with two outputs. Tried to take videos (all-I, 24 fps) with the spinning plexiglass at various points along the path. Notes/results/observations:
- The plexiglass changes the location of the focus enough that you have to try to refocus, but it is very hard to tell when you are in focus. Here is a video of going through focus (note that it is a normal donut without the plexiglass: IMG_1618.MOV
- There is clearly less differential motion when the plexiglass is close to the camera (IMG_1619.MOV) compared to when it is far away (IMG_1620.MOV). Currently, the images are saturated, though.
- Here's another video with lower light level. Perhaps with enough smoothing this could work. IMG_1621.MOV
December 4-7 2023 DIMSUM upgrade.
We are going to make three system changes:
- change from mirror lens to Canon 100-400 mm lens. manual here: ef100-400f45-56lisiiusm-im-e.pdf
- extend spatial extent of fiber array to get a wider field.
- swap out batteries with replacement DC power supplies, Lenink Adjustable adapter from Amazon.com. https://www.amazon.com/gp/product/B0CBP6KBDX/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1
1430 Chile time Dec 4 2023:
Have changed lens and set focal length to ~200mm. Added extension bar above pegboard. "updated' python program in steps 12, 13 above did not work. The earlier version seemed to run (note it hangs in open loop, on purpose).
Tried power cycling the camera and plugging and unplugging but still getting "camera not found" gphoto2 errors.
Fixed cable issue and got connected to camera. adjusted zoom, focus, and pointing to get to:
The metal bars hold 7 fibers each.
In order to get a good focus I set lens to autofocus (AF), and increased exposure time to 1/10 sec or so. Did partial-button-push to engage autofocus, took and image. Then I switched the lens to manual focus (MF).
Plan for tomorrow:
- find DC light source and use it to focus
try different fiber couplers
replace batteries
Note that autofocus on camera thinks screen is 6m away.
Dec 5 2023.
OK, had some good success working with Johnny Esteves and remote support from Elana.
We replaced dual AA batteries on both ends of remote shutter controller with AC adapters. We connected up additional optical fibers to the vertical and horizontal bars using SMA to SMA couplers.
After some futzing around with flash controller we got good images. Telescope structure blocks some of the upper extension bar but the horizontal one works fine. Central fiber in the bundle gets most of the light.
WIth current setup and using autofocus tool the cores of PSFs are saturated. So we might want even more ND filtering!
Am now going to try using gphoto2 to control lens focus remotely.
gphoto2 --list-config gives (among other things)
/main/actions/autofocusdrive
/main/actions/manualfocusdrive
/main/actions/cancelautofocus
(base) stubbslab@auxtel-macmini03 ~ % gphoto2 --get-config manualfocusdrive
Label: Drive Canon DSLR Manual focus
Readonly: 0
Type: RADIO
Current: None
Choice: 0 Near 1
Choice: 1 Near 2
Choice: 2 Near 3
Choice: 3 None
Choice: 4 Far 1
Choice: 5 Far 2
Choice: 6 Far 3
I think these are incremental adjustments around current setting.
This seems to have worked:
(base) stubbslab@auxtel-macmini03 ~ % gphoto2 --set-config manualfocusdrive=0
(base) stubbslab@auxtel-macmini03 ~ % gphoto2 --set-config manualfocusdrive=1
So that should have changed things.
Note another option to reduce flux is to reduce the aperture. That could also make focus sharper.
(base) stubbslab@auxtel-macmini03 ~ % gphoto2 --get-config aperture
Label: Aperture
Readonly: 0
Type: RADIO
Current: 5.6
Choice: 0 5
Choice: 1 5.6
Choice: 2 6.3
Choice: 3 7.1
Choice: 4 8
Choice: 5 9
Choice: 6 10
Choice: 7 11
Choice: 8 13
Choice: 9 14
Choice: 10 16
Choice: 11 18
Choice: 12 20
Choice: 13 22
Choice: 14 25
Choice: 15 29
Choice: 16 32
Choice: 17 36
END
3 am Chile Dec 6. Kicked off repeat 500 ./CommunicateTrial2023.sh, along with python data xfer script. This is with stopped-down aperture.
Wed Dec 6 2023, Pachon
I was confused by inapprorpriate CR to FITS file conversion. The PSF's aren't saturated. In fact we could use more flux.
This method works well (on Chris' laptop) for file conversion:
mdcraw -o 1 -D -4 -T CU2A0987.CR2
convert CU2A0987.tiff CU2A0987.fits
That makes a nice, well-behaved FITS file. PSF is about 40 microns across, which I think means for a 200mm focal length we are basically getting resolved images of the fiber tips, for a 600 micron fiber.
For next time, perhaps use smaller fiber diameters. 200 microns would be good.
I used gphoto2 to change the lens aperture to f/6.3. I was worried we were getting aberrations at faster f-number but I now think it's just fiber tip illumination non-uniformity.
I also removed the ND filter in the optical path. There is now no filter in the beam. Wasn't able to debug why no light in the vertical panel. Might just leave that for next time. It's vignetted by telescope anyway.
started another data collection into 23-12-06_observing_run directory on La Cie disk.
Thurs Dec 7, 2023 Pachon
Tasks:
Try fixing second outrigger panel- use different feed fiber?
investigate mounting schemes for mirror seeing monitoring- mount DUMSUM on Aux Tel somewhere. Maybe second Nasmyth port?
Pack up items.
Truss OD on AuxTel is 2.250 inches in diameter
upper rail on stairs is 2 inches diameter
lower rail on stairs is 3/4 inches diameter.
10 am local Dec 7: I swapped the drive optical fiber for upper extension to one that was plugged into the array. Need to see if that worked.
Battery in calipers iis LR44. Need to bring down more.
Any repositioning of DIMSUM to include mirror seeing would have to go for the ride w telescope elevation axis, and would only work when mirror covers are open.
Ordered parts for more DIMSUMS: two monochrome Canon 5D IV from MaxMax. More Xenon flash sources from Hamamatsu, and this from B&H
Jan 27 2024, CWS
We need to do better coupling light into fibers. Thor labs sells and 1:2, 1:4 and 1:7 fibers with 200,400, 600 micron cores.
The 1:2 version comes in 1mm core as well.
Let's assume we want the final emitting end to be smallish fiber, 200 microns.
If it's a 1:4 bundle then we need to feed it with a larger one, at least 400. 600 would be even better.
getting a uniform light distribution on output face would benefit from a mode scrambler.
So how about 1:4 plugged into the light source, largest possible is 600 micron fiber. That a diameter of about 1.2mm, and light into each should be the same.
Each of those feeds 1:4 200 micron bundle. That gives us 16 sources, each 200 microns diameter.
So we should order one 600 micron 1:4 and four 200 micron 1:4's.
The SMA threads are 1/4-36. Digikey sells them, part number A104989-ND. Bought 100 of them.
Asked Helen to place this order since credit card failed.
Feb 14 2024 Pachon, Stubbs
Changed optical fiber configuration to have Xenon source feed attenuator module to 600- micron 1:4 fiber then 4 of 200 micron 1:4 bundles. This gives us 16 sources 200 microns in diameter.
I did find one fiber that was flopping/loose in the pegboard, that was presumably the one that showed anomalous behavior in analysis done Feb 2024 by Ali K.
Checked using headlamp that all fibers look comparable.
When running remotely on data collection using gphoto-2 to interrogate aperture worked fine, after power cycling the camera.
But the
./CommunicateTrial.sh
script failed.
Tried a number of things- disk was not full, camera power cycle. Eventually realized SD card in camera was full. We (Elana was consulting via Zoom) used EOS camera utility on mac computer to reformat the SD card.
Used EOS tool on mac mini to center up the image and adjust fiber positions to get all 16 in FOV. Used dcraw to dump image metadata.
Filename: CU2A5938.CR2
Timestamp: Wed Feb 14 21:18:31 2024
Camera: Canon EOS 5D Mark IV
ISO speed: 100
Shutter: 1/197.4 sec
Aperture: f/5.0
Focal length: 271.0 mm
Embedded ICC profile: no
Number of raw images: 1
Thumb size: 6720 x 4480
Full size: 6880 x 4544
Image size: 6744 x 4502
Output size: 6744 x 4502
Raw colors: 3
Filter pattern: RG/GB
Daylight multipliers: 2.074708 0.932504 1.176114
Camera multipliers: 2040.000000 1024.000000 1456.000000 1024.000000
When I walked up to camera, focal length was set to 100mm and I have no idea how that happened.
Current issue is that the flash is failing to trigger. Here is the manual for it: Godox_XProS_20180905.pdf
Here is a video on flash operation:
Plan for tomorrow, Feb 15:
reset flash transmitter
normal synch
power cycle both receiver and transmitter
if all this fails, find white light source
Feb 15:
Did 'factory reset' on flash trigger module
Did power cycle on receiver
Taking an image with manual trigger worked to generate flash
Taking an image with Canon EOS utility also worked with light spots
But running shell scripts didn't work:
---these show no spots:
-rw-r--r-- 1 stubbslab staff 26M Feb 14 21:58 CU2A5971.CR2
-rw-r--r-- 1 stubbslab staff 26M Feb 15 2024 CU2A5977.CR2
-rw-r--r-- 1 stubbslab staff 26M Feb 15 2024 CU2A5978.CR2
-rw-r--r-- 1 stubbslab staff 26M Feb 15 2024 CU2A5979.CR2
-rw-r--r-- 1 stubbslab staff 26M Feb 15 2024 CU2A5981.CR2
-rw-r--r-- 1 stubbslab staff 26M Feb 15 2024 CU2A5982.CR2
-rw-r--r-- 1 stubbslab staff 26M Feb 15 2024 CU2A5976.CR2
-rw-r--r-- 1 stubbslab staff 26M Feb 15 2024 CU2A5980.CR2
(base) stubbslab@MacBook-Stubbs code % pwd
/Users/stubbslab/Documents/strobed_dimm/code
----- these do show fibers illuminated:
IMG_023.CR2, taken with EOS utility. :
-rw-r--r-- 1 stubbslab staff 28M Feb 15 10:09 IMG_0021.CR2
-rw-r--r--@ 1 stubbslab staff 26M Feb 15 11:08 IMG_0022.CR2
drwxr-xr-x@ 8 stubbslab staff 256B Feb 15 11:25 Photos Library.photoslibrary
-rw-r--r-- 1 stubbslab staff 26M Feb 15 11:26 IMG_0023.CR2
(base) stubbslab@MacBook-Stubbs Pictures % pwd
/Users/stubbslab/Pictures
so there is some configuration problem with our script?
putting data here on laptop: /Users/christopherstubbs/data/DIMSUM
christopherstubbs@Christophers-MacBook-Pro DIMSUM % scp stubbslab@auxtel-macmini03.cp.lsst.org:/Users/stubbslab/Pictures/IMG_002\*.CR2 .
I think we're saturated. Try again at f/20. This will be image IMG_0024, 1/125 sec at f/20. Did this conversion:
dcraw -o 1 -D -4 -T IMG_0024.CR2
convert IMG_0024.tiff IMG_0024.fits
then read fits file into MATLAB for inspection.
Even at f/20 we're saturated. So I need to re-install one of the optical attenuators.
Also need to solve the fact that we aren't triggering the flash using our own scripts.
So I don't have the 1 inch ND filters here. Must have taken them back to Boston. Rigged up a Kapton tape attenuator.
Take image IMG_0028 at 1/10 sec and f/10.
Still saturated. Try f/20
image 0029 is better but still just barely saturated at cores of sources. Backed out the Xenon source fiber on attenutor to make focus worse. Try that with image 0030 at 1/10 and f/20
image 0030 is still saturated in core at f/20. Inserted a second kapton tape filter in second filter holder slider.
Try again, this is 0031
That's better. Tons of flux, tight PSF:
dome is closed and hot.
Will take a stack of images 'by hand' using EOS tools. Starting frame is 0032 on Feb 15 2024.
Frames went 0031-0080 then (weirdly) 0000-0004. Time is 1414 Boston time. Deleted images 0000-0004 to avoid confusion.
So overall this works. We need to figure out how to get gphoto-2 to take an image.
Try just 1 frame from command line. (note card is getting full).
(base) stubbslab@MacBook-Stubbs code % gphoto2 --capture-image-and-download --no-keep
New file is in location /store_00020001/DCIM/100EOS5D/CU2A5983.CR2 on the camera
Saving file as CU2A5983.CR2
Deleting file /store_00020001/DCIM/100EOS5D/CU2A5983.CR2 on the camera
this goes into directory where command was executed. In this case
/Users/stubbslab/Documents/strobed_dimm/code
After Slack messaging with Ali have turned off live mode in EOS utility.
Tried CU2A5984.CR2. no sources.
Ali suggests running this program:
#! /bin/bash
gphoto2 --reset
gphoto2 --auto-detect --set-config /main/imgsettings/imageformat=32
gphoto2 --set-config /main/actions/eosremoterelease='5'
gphoto2 --set-config /main/actions/cancelautofocus='0'
gphoto2 --set-config capturetarget='1'
gphoto2 --capture-image-and-download --no-keep
got:
(base) stubbslab@MacBook-Stubbs code % source ./testprogram.sh
Model Port
----------------------------------------------------------
Canon EOS 5D Mark IV usb:001,022
New file is in location /store_00020001/DCIM/100EOS5D/CU2A5985.CR2 on the camera
Saving file as CU2A5985.CR2
Deleting file /store_00020001/DCIM/100EOS5D/CU2A5985.CR2 on the camera
New file is in location /store_00020001/DCIM/100EOS5D/CU2A5986.CR2 on the camera
Saving file as CU2A5986.CR2
Deleting file /store_00020001/DCIM/100EOS5D/CU2A5986.CR2 on the camera
New file is in location /store_00020001/DCIM/100EOS5D/CU2A5987.CR2 on the camera
Saving file as CU2A5987.CR2
Deleting file /store_00020001/DCIM/100EOS5D/CU2A5987.CR2 on the camera
New file is in location /store_00020001/DCIM/100EOS5D/CU2A5988.CR2 on the camera
Saving file as CU2A5988.CR2
Deleting file /store_00020001/DCIM/100EOS5D/CU2A5988.CR2 on the camera
so it took four images, 5985 to 5988.
copying them over
That worked!
1600 Boston time:
Kicked off a test collection with file xfer to LaCie.
Verified with image 5993 that it's working well!
Started a long term run
Feb 16 10:38 local Pachon time.
The cores of the images from Feb 14-morning of Feb 16 are saturated.
I installed an aluminum foil attenuator in one of the filter holders, replaced the Kapton tape that was in there.
This should reduce light level by at least a factor of two.
We can adjust f-number remotely to get desired light levels. Note high f-number makes us less sensitive to thermally driven focus changes.
We also have less aperture averaging and a smaller beam cone. Currently operating at f/20. With 220mm focal length our input aperture is 220/20 ~ 11mm.
I think this is better than operating at low f-number and cutting light level at the source.
Tasks:
OK to let it stop running over the weekend.
review performance and adjust f-number as needed to attain desired light level.
Imaged obtained after 1030 pachon time on Feb 16 should be OK to look at.
Image 6636 is most recent on disk, now. Wait for 6637 and verify light level. 6642 is a good test- grabbing that one.
Also now that we know how to extract dome shutter status from EFD (See image quality dashboard) we can better correlate that with measurements.
Well, that definitely cut light out! Peak is now around 600 ADU. So we should open up f-number more. Each f-stop is factor of two in flux.
So going from f/20 to f/10 should be 4x the light. Going from f/20 to f/5 should be 16x the light. That would give us around 9500 peak.
1214 Pachon time.
I used EOS utility to change lens to f/5, after halting current acquisition. We are getting perilously close to filling SD card on camera but I don't have time to change it and re-align.
Image 6694 should be at f/5.
As I think about this, I believe I changed camera focus and that's why things are so mushy now. Need to go up and do an autofocus with dome light cracked. That's also why flux peak is so low.
Rats.
1218 stopped data collection, going up to focus. Image 6708 should be good test frame.
Nope, no change.
Did a focus on camera as follows:
Set to "Av" for auto exposure. Set lens to AF
Partial button press to get a beep
change back to 'M' and MF.
lens is set to f/5. test image is 6710.
PSF looks good but it's misaligned. Drop back on zoom setting to around 150
redid focus as above, slid attenuator out to get more flux.
test image is 6711
OK this looks acceptable. Going with this config.
Seems fewer than 16 spots but outta time.
started another auto-run at image 6713.