-
Notifications
You must be signed in to change notification settings - Fork 201
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
Grabber input_mu function ROI limits #2360
Comments
You'd have to get Kasli gateware with non-standard number of ROI engines. I'm not sure if 200 wouldn't be problematic though in terms of fpga resources and timing. artiq/artiq/gateware/rtio/phy/grabber.py Lines 61 to 62 in 692572a
|
Is this really the only adjustment needed? I tried increasing artiq/artiq/coredevice/grabber.py Line 102 in 9a3f6f8
I'm afraid I didn't have the time to dig any deeper yet, but if there is some obvious place for me to look, I'd appreciate a hint. |
One-Line Summary
Is there anyway to get more than 16 ROIs from the grabber per EMCCD camera frame?
Issue Details
We have a system that requires us to average around 200 ROIs per camera frame with real time calculation. In order to do this we hoped to be able to use the grabber's functions that are shipped with the hardware. We have hit a wall because it seems that when we use more than 16 ROIs it gives a artiq.coredevice.grabber.OutOfSyncException. Anyone have any advice on how to proceed?
from artiq.experiment import *
import numpy as np
class RTIOAnalyzerGrabber(EnvExperiment):
def build(self):
self.setattr_device("core")
self.setattr_device("grabber0")
The text was updated successfully, but these errors were encountered: