PGO uses only keyframes (e.g., equidistant) to mitigate heavy optimization burdens while odometry publishes every all (e.g., 10Hz) motion estimations
SC-PGO internally runs isam2 optimization so if you have many nodes and factors, the odometry and pgo seem not to be quite synchronized, but I expect the pgo would soon converge and finish if you wait a little time.
thanks for using our project.