divide by zero error
See original GitHub issueHello, thank you for the work. I am facing the issue of dividing by zero error in the line below when calling the sample function to sample memory. Any idea why?
is_weight /= is_weight.max()
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
How to correct a #DIV/0! error - Microsoft Support
Microsoft Excel shows the #DIV/0! error when a number is divided by zero (0). It happens when you enter a simple formula like...
Read more >How to fix the #DIV/0! error - Excel formula - Exceljet
The #DIV/0! error appears when a formula attempts to divide by zero, or a value equivalent to zero. Although a #DIV/0! error is...
Read more >How to Avoid #DIV/0 Errors in Excel
1. Create a column for your formula. (e.g. Column E Conv Cost) 2. Click the next cell down in that column. (e.g., E2)...
Read more >How to Get Rid of #DIV/0! Error in Excel? Easy Formulas!
In Excel, you will get a DIV error when you have a formula where there is a division and the divisor is 0....
Read more >Division by zero - Wikipedia
For other uses, see Division by zero (disambiguation). ... is contained in Anglo-Irish philosopher George Berkeley's criticism of infinitesimal calculus in 1734 ...
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
Hi there! I faced the same issue and what I did is to sample another value of that same interval, until it is not an integer (given that the capacity is initialized to np.zeros ). In the prioritized memory I added the following:
This did the trick for me. Hope it does the same to you.
If anyone is still wondering why it pulls 0 from the replay memory, it is because the location in the replay memory that was sampled was not filled out yet and thus contained the initial values with which we initialized the replay buffer. i.e., 0’s. If you set a condition that the training does not start until the buffer is completely filled, then you never encounter this issue.