Moving the vcam streams to scexao5 and doing file saving there will minize desynchronizations caused by network drops and latency, which is paramount for high framerate FLC acquisitions.
To move to scexao5 we need to ensure there is a large enough SSD data pool for temporary storage and slow-sync on a nightly basis to scexao6's long term pool. In addition I think this can be used to create a synchronized shared-memory stream for tasks like phase diversity WFSing.
@DasVinch has listed hardware required to implement SSDs on scexao5 which is current blocker.
Moving the vcam streams to scexao5 and doing file saving there will minize desynchronizations caused by network drops and latency, which is paramount for high framerate FLC acquisitions.
To move to scexao5 we need to ensure there is a large enough SSD data pool for temporary storage and slow-sync on a nightly basis to scexao6's long term pool. In addition I think this can be used to create a synchronized shared-memory stream for tasks like phase diversity WFSing.
@DasVinch has listed hardware required to implement SSDs on scexao5 which is current blocker.