[BUG] Can't we specify `standardized_rew_adv` and `standardized_cost_adv` at the same time?

[r-y1]

Required prerequisites

• [X] I have read the documentation https://omnisafe.readthedocs.io.
• [X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
• [X] Consider asking first in a Discussion.

What version of OmniSafe are you using?

0.1.0

System information

no need

Problem description

Can't we specify standardized_rew_adv and standardized_cost_adv at the same time? I guess it is a bug.

https://github.com/PKU-MARL/omnisafe/blob/main/omnisafe/utils/config.py#L216

Reproducible example code

The Python snippets:

Command lines:

Extra dependencies:

Steps to reproduce:

1. 2. 3.

Traceback

No response

Expected behavior

No response

Additional context

No response

[Gaiejj]

We apologize for the problem, it was a simple typo. standardized_cost_adv and standardized_rew_adv are usually a generic trick that defaults to True in OmniSafe, but should not be forced to be specified as True.The correct way to write it should be

assert (
     isinstance(configs.standardized_rew_adv, bool) 
     and isinstance(configs.standardized_cost_adv, bool)
 ), 'standardized_<>_adv must be bool'

We'll fix this as soon as possible, thanks for your feedback!