zmsn-1998
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Rebuttal Reviewer cgp7: 1. re: In the related work section, the differences or advantages of this benchmark w.r.t. other benchmarks should be highlighted. 2. As far as I understand, there is no way to specify multiple constraints at the same time. 3. In Sec 4.3 (task 3 - robots with goal), what is the constraint? 4. While the various types of tasks are clarified, the paper also claims that it supports 33 different task settings. Could you please clarify what these 33 task settings are? Answer: problem1: To our best knowledge, the learning framework of safe RL: openai/safety-starter-agents, but this framework is based on TensorFlow1 and depends on gym 0.15.3, which is not conducive for RL researchers to use it. Safepo is a unified multithreaded PyTorch framework that allows different algorithms to be fairly compared on the same setting (e.g. same data preprocessing, same update frequency). problem2: 我可以增加safety gym multi-constraint的实验 problem3: robot with goal Move the robot to a series of goal positions. When a goal is achieved, the goal location is randomly reset to someplace new, while keeping the rest of the layout the same. The sparse reward component is attained on achieving a goal position (robot enters the goal circle). The dense reward component gives a bonus for moving towards the goal. And the costraint is Hazards which are dangerous areas to avoid. These are circles on the ground that are non-physical, and the agent is penalized for entering them #todo 论文没有加goal的实验,准备加上去,同时准备增加button实验 problem4: Safepo can support Safe-Gym, Bullet-Safe-Gym, as well as our newly designed 4 safe tasks on hands, with a total of more than 30 tasks. Reviewer KqDf 1. The paper should highlight specific novel and contribution beyond the current benchmarks. While preexisting algorithms and benchmarks are mentioned in the Related Work section, there is no direct comparison of how SafePO provide in addition to the prior arts, such as between the SafetyGym and SafePO.  2. line 48-50 (and corresponding section in the analysis part): "But in general, the approaches implemented by a deep neural network (e.g., P3O) achieve a better performance than the convex approximation method (e.g., CPO); such an empirical observation is sharper when the task is more complex ": could improve if the authors clarify on the criteria they considered for performance and how the task complexity is defined 3. line 59-61: "We observe that it is very challenging for the agent to learn a safe policy if the cost is too sparse.The empirical result shows that: the agent learns little to improve the reward performance and always prefers to play an unsafe policy. " could improve further if a clear description of the cost ranges that pose a challenge problem1: problem2: When the state space and action space are large, CPO cannot guarantee the basic guarantee of SAFE in the convex approximation setting. 这边我会单独增加cpo的实验验证。 problem3: In the current simulation environment design, a dense reward will be used to assist RL learning, and a large task bonus will be given when the final target task is completed. For example, if we want an agent to go to a certain destination, we will not only give a reward for reaching the destination, but also give a reward design that is closer and closer to the destination, which is more conducive to the learning of the agent. When we only give the agent a reward for completing the task, when the state space and action space are large, it will make the learning process very challenging. In the safe RL setting, when our cost penalty signal is too sparse, it will also make it difficult for the agent to learn a safe policy. re: 59Ne As a benchmark paper, the performance of various baseline algorithms is critical. Unfortunately, the results shown in table1 and table3 are far worse than those reported in previous papers. If the baseline algorithm does not have the desired effect, the conclusions based on the experimental results are meaningless. At the same time, the following RL researchers will not benefit from it. What did the previous article refer to? Is it in the same setting as ours? It may be that our cost setting is different from other parameter Settings. For example, Focops has published its own code on Github, but when we took the code, we verified that it could not match the experimental data in its paper in Ant-v3 and other environments. At the same time, we modified it to the environment of Safety Gym, only modified the way of interaction between the model and the environment, and the algorithm result was also very poor. We also found someone who had the same problem as us in the Github issue, and the author replied that it was necessary to adjust the parameters carefully. However, there are still some problems. When we did the experiment, we found that the author's original implementation method, single-threaded mini-batch, needed 10h in safety gym in a simple environment, which was very unfriendly to RL researchers. Therefore, we made SafePO, which has a more efficient sampling speed and a more unified framework. Let RL researchers fairly compare the performance of different algorithms under a unified frpamework. Paper present four safety robot tasks, including robots with limited velocity, robots with circle, robots with goal and safety dexterousHands. However, these environments have been proposed in previous works, and the author's contribution is to re-test the implemented baseline algorithm in these tasks. Based on this, it is difficult for me to identify this as the main contribution of a paper. The Datasets and Benchmarks track serves as a novel venue for high-quality publications, talks, and posters on highly valuable machine learning datasets and benchmarks, as well as a forum for discussions on how to improve dataset development. Our innovation is to create a unified algorithmic framework for Safe RL researchers, which is the starting point of our work. At present, there is no unified framework for fair algorithm comparison in the Safe RL field. For example, the code of PCPO is still Theano. When implementing PyTorch, we are very careful to follow the original text and make a careful comparison with Theano code to ensure that there are no errors. The algorithm code for P3O has not been published, etc. I think our work has played a great role in promoting the follow-up research on Policy Optimazation in the whole Safe RL. The analysis of the results for various baseline algorithms is insufficient. Paper does not explain why the algorithms fail on some safe tasks. In Discussion C.3, the authors attempt to analyze the difference between (FOCOPS, PPO-L, and P3O) and (CPO, PCPO, and TRPO-L). However, these discussions are not linked to the experimental results. re: hb7D There are grammatical errors and issues with flow throughout. There are many places in the paper where the language is non-technical or unusual, e.g., Lagrange multiplier “keeping calm” (lines 58, 225), calling an algorithm a “winner” (lines 181, 182), and “solid” safe RL benchmark (line 7). The paragraph in lines 188-198 is incredibly confusing and does not help me understand why CPO, TRPO-L, and PCPO are underperforming. Section 6.4 (Sparse Cost) is also confusing. “This is because the total cost limit is tiny, so the robot obtains a small cost for each step, implying the robot knows very little about the environment.” This statement makes no sense. Why would a small cost limit result in the robot getting a small cost in each step? How do we know the robot “knows very little about the environment”? “We know the algorithm near the cost limit usually obtains better performance than that far away from the cost limit. This is because the higher cost implies the robot learns more about the environment, which helps the robot understand a safer policy.” Why would a higher cost imply that we’ve learned more about the environment? Why does a policy “near the cost limit” imply it performs better? These are unsubstantiated and (in general) false claims. re: fKDX [W1] The proposed benchmark suite is mostly a collection of existing environments (Limited Velocity Robots, Safety-gym, Bullet-safety-gym) and re-implementations of existing algorithms. It, therefore, has limited novelty. I'm confused about the main contribution of this paper. The Datasets and Benchmarks track serves as a novel venue for high-quality publications, talks, and posters on highly valuable machine learning datasets and benchmarks, as well as a forum for discussions on how to improve dataset development. Our innovation is to create a unified algorithmic framework for Safe RL researchers, which is the starting point of our work. At present, there is no unified framework for fair algorithm comparison in the Safe RL field. For example, the code of PCPO is still Theano. When implementing PyTorch, we are very careful to follow the original text and make a careful comparison with Theano code to ensure that there are no errors. The algorithm code for P3O has not been published, etc. I think our work has played a great role in promoting the follow-up research on Policy Optimazation in the whole Safe RL. [W2] The analysis of the experiment is not deep enough in the paper, authors largely rehash existing ideas. (Sec 6.3 Sec 6.4). [W3] The authors mentioned the sparse cost problem in sec 6.4, but they do not discuss it more and give possible solutions. 这边的解决方案是增加多一些关于sparse cost 的实验 [W4] In the provided code, the safe-marl-baselines algorithm seems to be derived directly from [1], which is not properly integrated into the SafePO framework. 这个是一个问题,需要讨论

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully