Me (RavingMagicMan) and tjwombo made a spreadsheet to calculate the Pokemon Attack required for all Kanto gyms and dungeons. It is especially helpful for clickless runs, and can be expanded to other regions using the formulas.
Why do you divide by 37 for all the gyms? I recently redid the minimum attack on the wiki and got vastly different numbers for all of those. Even if you are trying to implement xAttack, the number would be MinimumAttack*2/3
Edit: Also your formula is going to be slightly inconsistent throughout since you're just adding up the total health and dividing. Since the wiki minimum attack rework I did, the wiki is currently as accurate as you can get without including typing and weather. Instead of adding everything together, I divided each by the minimum attack such that you'll always beat it in 30 seconds (which is how many attacks you get in one gym run)
My minimum attack sheet https://docs.google.com/spreadsheets/d/1HSoQ3XYtXXtocJBh-6vjciBjfgZTbhe1yviclNfyZpM/edit?usp=sharing
The wiki with updated values https://pokeclicker.miraheze.org/wiki/Gyms
We got the 37 by looking through the source code, and somewhere I saw a spot that said the attack went off every 900 ms. With that in mind we would have gotten the 67 in the dungeons and I think we were just sleep deprived, so we just took the 7 and slapped it into the 30 seconds for the gyms (should be 33 if logic was correct). But after your post, I actually went into the game to see what was actually going on, and yes the attack goes off once every second so it should be divided by 30.
Also your totally right on the health insight because currently we would have any damage carry over to the next pokemon, but that's not how it works. Thanks for pointing out this inconsistency.
You'd have to ask Red or another dev but I believe the 900ms might be a part of the fix for Firefox, which was previously attacking every 1.1 seconds (while Chrome and Client were both every 1 second). This issue was fixed in uh... 0.9.0 maybe? I don't remember the exact version but I think that has to do with the 900ms
