Compare commits

..

No commits in common. "cba8856c8516311bc1ea418d2ff283c69406fabc" and "4fb8507160d65d9f104214c29722c044a10ae781" have entirely different histories.

1 changed files with 0 additions and 7 deletions

View File

@ -56,11 +56,6 @@ except ImportError:
# about half the time, with no lost frames measured on either computer. # about half the time, with no lost frames measured on either computer.
# Binning goes to 1 vertical-first (the horizontal minimum depends on it), and # Binning goes to 1 vertical-first (the horizontal minimum depends on it), and
# Width/Height ask for more than any sensor so the clamp lands on the maximum. # Width/Height ask for more than any sensor so the clamp lands on the maximum.
# The exposure the camera already holds caps its frame rate too, so a short
# fixed exposure is written before the rate, and auto-exposure is turned back
# on afterwards. Without it, tower 111's camera, left at 3.5 s by the old
# profile's 9 s auto limit, got a 'standard' profile clamped to 0.28 fps. A dry
# run writes nothing, so its frame rate still reflects the old exposure.
# The per-frame chunk data is what the keep rule reads; each item must be # The per-frame chunk data is what the keep rule reads; each item must be
# enabled before chunk mode itself, which locks them. # enabled before chunk mode itself, which locks them.
_RAW_COMMON = [ _RAW_COMMON = [
@ -74,8 +69,6 @@ _RAW_COMMON = [
("Height", 100000), ("Height", 100000),
("PixelFormat", "BayerRG12p"), ("PixelFormat", "BayerRG12p"),
("DeviceLinkThroughputLimit", 250000000), ("DeviceLinkThroughputLimit", 250000000),
("ExposureAuto", "Off"), # so the short exposure below sticks
("ExposureTime", 1000.0), # before the rate: see the note above
("AcquisitionFrameRateEnable", True), ("AcquisitionFrameRateEnable", True),
("AcquisitionFrameRate", 1000.0), # clamped to the camera's maximum ("AcquisitionFrameRate", 1000.0), # clamped to the camera's maximum
("ChunkModeActive", False), ("ChunkModeActive", False),