Add system test for variable_years option for orbit

[ekluzek]

Currently we have no testing for the variable_years orbit option which is important for Paleo work. This option changes the orbital parameters on Jan/1st of each year, each component should then get the new orbit and act accordingly. See issue #2081 for adding unit testing on this. For system testing we should run this at low resolution, and make sure we run over a change in year. You could start in December and just run over a year change. But, I'm not sure if that enables you to show that the change in orbit happened and shows up in each component.

It's also possible that a mismatch in orbital parameters between components, might cause the model to choke. But, I'm not certain on that, or on how different it needs to be for that to happen, or how long you'd have to run to see it. But, we at least need a smoke test that exercises this option and makes sure it doesn't blow up when you use it.

[billsacks]

@ekluzek do you know if this is still an issue? If so, can you move it to the appropriate post-cime-split repo?

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.