[Greedy LAD] Have the ability to have data before the start bound IF it's a strategy 'latest' request

[jvigliotta]

Is your feature request related to a problem? Please describe.
Low frequency data in LAD views will have its values dropped as it ages out of the current time conductor window in real-time mode. While this is by design it can be counterintuitive.

Describe the solution you'd like
Would like to have LAD Views (strategy 'latest') requests hold onto older data outside of the start bound, if no other new data has come in, by default. Would also like the ability to turn this off.

[akhenry]

Testing

• Add ViperGround/OpenMCTTest/timelyParameter into a display layout
• Add ViperGround/OpenMCTTest/timelyParameter into a LAD table, and then add that LAD table into the previous display layout
• Switch to local clock
• On banner, run -

cd /usr/local/viper/python-scripts
python send_low_frequency_parameter.py --apid=899 --interval=60

• Set your time conductor to real-time mode, and only 30s of data
• Verify that when telemetry ages out of the current time conductor bounds it does not disappear
• Change the start bounds to 31s (assuming that the telemetry is now older than 31s)
• Verify that both the LAD view and LAD table still show telemetry values for the timelyParameter, even though it is technically outside the conductor bounds.

[akhenry]

@unlikelyzero To verify

[unlikelyzero]

I may misunderstand the testing instructions, but setting Time Conductor to:

Instead of seeing MAD LAD Data in both the Table View and LAD View, the data is sometimes dropped from the Table View.

[unlikelyzero]

working as designed. Need a release note