(NOT TO Land) No Case: SAC-DisCor.

[RuofanKong]

Why are these changes needed?

Related issue number

Checks

• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/latest/.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failure rates at https://ray-travis-tracker.herokuapp.com/.
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested (please justify below)

[Edilmo]

@RuofanKong can we abandon this? or you want to keep it around?

[RuofanKong]

@Edilmo Thanks for checking! This is prototyping SAC-Discor, an algorithm on top SAC as an option to improve convergence of SAC. I want to keep this PR for a while. Once we landed Apex-SAC, we may need to evaluate if there's a need to incorporate this new algorithm afterwards. I will definitely let you know.

[Edilmo]

@Edilmo Thanks for checking! This is prototyping SAC-Discor, an algorithm on top SAC as an option to improve convergence of SAC. I want to keep this PR for a while. Once we landed Apex-SAC, we may need to evaluate if there's a need to incorporate this new algorithm afterwards. I will definitely let you know.

No problem. Thanks for the quick answer.