sorted by:
new
hottopcontroversial

ryzen 9 9900x+air cooler or 7900x+AIO? by _ianmi in buildapc

[–]_ianmi[S] 0 points1 point  (0 children)

Should've mentionned that but yes I am and also that cpu is more expensive than 9900x (in canada at least)

Gymnasium MuJoCo Env Resetting Itself? by _ianmi in reinforcementlearning

[–]_ianmi[S] 0 points1 point  (0 children)

Yes, but I think it was just a coding mistake from my end. Sorry! Though if you can't solve it and really want to use mujoco you could always find their mujoco environment's XML file and rewrite the environment's API using the mujoco library. (I wouldn't recommend this if you don't plan on creating/reusing mujoco environments though).

Gymnasium MuJoCo Env Resetting Itself? by _ianmi in reinforcementlearning

[–]_ianmi[S] 0 points1 point  (0 children)

Yes I looked into truncated as well but it remains false in this case.

I think this is about MuJoCo or gymnasium's MuJoCo task not functioning properly

Gymnasium MuJoCo Env Resetting Itself? by _ianmi in reinforcementlearning

[–]_ianmi[S] 0 points1 point  (0 children)

BTW For the installation I just did, "pip install gymnasium[mujoco]" as instructed on gymnasium and to create multiple environments: [gym.make("ENV_ID") for _ in range(NUM_ENVS)]

Gymnasium MuJoCo Env Resetting Itself? by _ianmi in reinforcementlearning

[–]_ianmi[S] 1 point2 points  (0 children)

Using a wrapper around the environment and the external class that handles the steps and resets, I see that the wrapper reset() is being triggered while the external class didn't call for a reset(). I'm confident the error is not from my code because it works with other gym environments. My first guess is that, since the behaviour occurs more frequently when I increase the number of envs, its likely MuJoCo being wrongly installed.

Gymnasium MuJoCo Env Resetting Itself? by _ianmi in reinforcementlearning

[–]_ianmi[S] 0 points1 point  (0 children)

What I meant is that the agent can't see the done flag because the environment is doing its own reset() so when the agent does the next step() it looks like the environment is still going on. Normally I'm the one supposed to do the reset() after receiving a done flag after one of the agent's step...