You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'factoryDir' argument from this example requires a file called 'init.daq' in the folder. The calibration folder has a file called 'init_xyz.daq' that is generated during image capture, but this is not recognized. The workaround is having the user rename init_xyz.daq to init.daq.
The text was updated successfully, but these errors were encountered:
Yes, your "workaround" is the standard procedure. You can have multiple init.daq files by putting them in multiple directories, e.g. named after the device numbers.
Is there any documentation on these standard procedures? It seems that there is a lack of documentation on this type of information within Github. It would be helpful to know more of this information about assumptions / expected use cases that were made when developing the code base.
If there can be multiple init.daq files, would it be better to explicitly input the filename, rather than directory where the file is located? This would eliminate possible errors from having multiple init.daq files for different devices.
The 'factoryDir' argument from this example requires a file called 'init.daq' in the folder. The calibration folder has a file called 'init_xyz.daq' that is generated during image capture, but this is not recognized. The workaround is having the user rename init_xyz.daq to init.daq.
The text was updated successfully, but these errors were encountered: