[UIMA-4063] DUCC RM: run its schedule on the OR clock instead of its own

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0-Ducc
• Fix Version/s: 2.0.0-Ducc
• Component/s: DUCC
• Assignee: Jim Challenger
• Reporter: Jim Challenger
• Created: 27/Oct/14 16:51
• Updated: 02/Dec/14 20:44
• Resolved: 02/Dec/14 20:44

Description

This has gone back and forth over time. At one point the OR would get 'stuck' and blast its clock many times a second so we moved RM to its own clock. This seems to be remedied now so the RM should go back to the OR clock to increase responsiveness. This revival includes a "blasti-guard" so RM does not schedule more often than 1 OR clock even if things go awry.

The code for both modes is kept in the RM so its straightforward move back and forth between the modes.