Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edge Bounce with Elasticity Parameter #51

Draft
wants to merge 27 commits into
base: master
Choose a base branch
from

Conversation

frehe
Copy link
Member

@frehe frehe commented Feb 3, 2023

No description provided.

marcinpaluch1994 and others added 27 commits November 24, 2022 16:17
made target position slider window less tall.
added hint to turn off TF JIT for getting going
…mass M to m_cart and cart pole mass m to m_pole

added comments about meaning of "stage" in MPPI
renamed TargetPositionGenerator to TargetTrajectoryGenerator, since we target a complete trajectory, not just cart position.
renamed my_logger() to get_logger()
say which compiler we are using
add check for existing terminate_experiment field
add docstring
…istency with other config files.

added more docstrings for undocumented methods and constructors.
added updated_attributes to barebones controller.
improved formatting of logging output
added dictdiffer to requirements.txt
renamed target_position cost function to cartpole_trajectory_cost.py.
replaced some load_config with the load_or_reload_config_if_modified, so that the configs are cached for change checking.
added logger to Compile.py
…g and the cartpole is at least balancing itself and swinging up from down position. Big changes all over!

Now anytime any of the config files is modified during runtime, the using class has its tf.variable assigned the new value.
To get this work, the variable MUST NOT EXIST before it is set this way the first time. Otherwise the compiler just uses the field at compile time and the changes are never seen inside.
The cartpole window now does not reset the initial position and angle sliders on each start.
…hanging the cost weights during runtime! Yay, finally!

Trick was to make sure that all values are actually propagated to tf variables, e.g. numpy arrays, ints, string, not just float

Changed logging format to start with level for better readability.
added string type to computation_library.py
…nfig values in cartpole_trajectory_generator.py.

added dt to params in cartpole_trajectory_generator.step() call.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants