Environment creates the same scenario between resets
See original GitHub issueConsider this minimal example:
import gym
from gym.envs.registration import register
register(
id='simglucose-adult001-v0',
entry_point='simglucose.envs:T1DSimEnv',
kwargs={'patient_name': 'adult#001'}
)
env = gym.make('simglucose-adult001-v0')
env.seed(0)
env.reset()
>>> Observation(CGM=126.63092222821054)
env.reset()
>>> Observation(CGM=126.63092222821054)
The environment produces the same scenario Observation(CGM=126.63092222821054)
on reset()
, even on changing the seed unless I make
the environment again. This shouldn’t be the case as it keeps on generating the same episode.
Is this a potential bug, or am I missing something here? @jxx123
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Environments overview - Power Platform | Microsoft Learn
Environment history gives admins a timeline of the full environment lifecycle from the moment it's created until it's completely deleted with ...
Read more >Climate change widespread, rapid, and intensifying – IPCC
GENEVA, Aug 9 – Scientists are observing changes in the Earth's climate in every region and across the whole climate system, according to ......
Read more >Ecosystem Change - GreenFacts
World climate has already changed and continues to change, affecting temperature, rainfall, and sea levels. Commercially exploited fish stocks ...
Read more >Adaptation | National Geographic Society
In evolutionary theory, adaptation is the biological mechanism by which organisms adjust to new environments or to changes in their current ...
Read more >Global environmental change and health - NCBI - NIH
This causes inequalities in both health endangering exposures and health outcomes. ... Relations between human induced global environmental changes affect ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sumanabasu Thank you so much for your comments!
__init__
, actually this line in__init__
will call_seed()
function.The fix is in. Will make the initial BG settable in another PR.