Let me clarify the math a little. When I write .15*rip-f(1.15*30+12)/40*shred, that is my estimate for the damage gained by refreshing rip during TF when rip still has f fraction of its time remaining. You gain .15*rip damage due to TF's effect, but you lose f rip, worth f*30 energy, which would otherwise be spent on a TF'd shred doing 1.15*shred damage for 40 energy. Thus you lose f*1.15*30/40*shred damage.

You also lose CP, but assuming you aren't refreshing rip just as savage roar is about to fall off, the worst case here is that you have to use a 1 CP roar later. This lasts a little over half as long as a full CP roar, so we can say you lose 12 energy, a little under half the cost of savage roar, in the worst case. This energy would otherwise be spent on non-TF'd shreds, so you lose 12/40*shred damage. If f is small, you've probably already refreshed savage roar so this loss won't occur; if f is large, this loss will tend to approach its maximum value, since you'll be short on CP after applying the rip in the first place. Thus as a rough estimate I multiply this number by f, yielding a loss of f*12/40*shred damage. (This factor isn't really significant to my results in the previous post since f is close to 1 in most of the figures there. It just yields a more accurate value for the damage gain when f is small.)

This yields a damage gain of .15*rip-f(1.15*30+12)/40*shred for refreshing rip during TF. A similar calculation (but without the CP complication) yields .15*rake-g*1.15*35/40*shred damage for refreshing rake during TF when rake still has g fraction of its time remaining.

I was thinking about how to compare the numbers and decided to work backwards, and to simplify things I am only going to look at the shred and rip numbers. My goal is simply to see if the numbers are close - so I will be making a series of assumptions.

Without the "C" statement, the number of rips was 11.5 and the number of shreds was 94.8. With the "C" statement, the number of rips was 14.1 and the number of shreds was 93.4.

Mew adds 2 seconds per "ripshred" so I am going to assume 11 ticks per rip and not 12. I am going to assume that the increased number of rips (14.1 - 11.5) directly translates into rip ticks that have the 15% bonus. In other words 2.6 * 11 ticks. Had the rip not been clipped all of these ticks would have been without the bonus. Using the numbers from your parse this gives (2.6 * 11 * 9558 * .15) extra damage due to clipping. That is 41,003.8 damage.

For energy/opportunity loss I am going to use the difference in shreds multiplied by 1.15 (in other words assume all the shreds we lost would have been cast during TF). The number of shreds lost is 94.8 - 93.4 or 1.4. So we have (1.4 * 1.15 * 15612) or 25,135.32 lost damage.

Taking the difference we get 15,868.48 damage or 52.9dps. There is extra lost damage spread out among the mangles, rakes and white damage - so the dps impact we are seeing is possible, assuming that the 14.1 number is credible. BTW - I checked one of my parses and my damage per rip tick/shred numbers are slightly lower than what you listed (and I just used) - so that accounts for some of the difference.

Next question - should we have clipped more than 2.6 of the Rips? Since the last 25% of the fight has no rips in it, we are looking at 225 seconds of fight - so the 11.5 base number for 22 second Rips is plausible. TF uptime is 22% (11 were cast). I am about to fall asleep so I will make some gross assumptions here. 22% of the rips would have been refreshed already. 22% of the time SR interferes. Some percent of the time not enough combo points are generated due to something that occurred before TF was cast along with some of the rules that take precedence - ripshred, berserk, rake, SR and mangle simply consuming all of the TF window. I can see it ending up at 2.6.

My last assumption is that the DPS < 25% line is being calculated incorrectly. Likely that was not reviewed as carefully as the rotation code.

TLDR: I can (more or less) see how the numbers came about in the current test case. This is without some of the potential refinements you listed. The key question in my mind is the 2.6 number. Perhaps you can measure that number through testing to see if it matches up. If we think that number is too low then it is time to question either Mew and or the scripts we are driving it with. If that number is credible then the rotation change is not a significant dps improvement.

Edit - there is also the question of 11 vs. 12 Rip ticks and how material that is. Based on comments made by Junlex in the cat thread, the number of ticks varies - sometimes it is 11 and sometimes it is 12.

To try to identify some sort of pattern as to when rip would last 11 ticks vs 12 ticks I ran a short log which I have uploaded:

World of Logs - Real Time Raid Analysis

I ran hit/exp capped with no trinket procs, no auto-attacks, no abilities used apart from mangle, shred and rip, to try to reduce the number of potential variables but no obvious pattern emerged. From this short run of 15 rips, 13 had 12 ticks, 1 had 11 ticks (starting at 13:03:22.303) and 1 had 13 ticks (starting at 13:06:16.292). A lot more data's required though, as when I did 6 rips earlier, 2 had 12 ticks while 4 had 11 ticks.

A couple of additional thoughts.

The check I added to test this does not check for the "A more powerful spell is already in effect" error. However, this should not be an issue in the current script since it is not pre-potting, and it is using the Potion of Tol'vir during Heroism which happens in the last 40 seconds of the fight where Rip is no longer being cast. The trinkets used are Unheeded Warning and Fluid Death so they are not a factor. I can't think of any other procs that affect AP outside of the potion. This is a condition that would have to be dealt with if I ever tried to implement this in Ovale though - or if I turned on pre-potting. Currently there is no call in the Mew script API to see if a Rip cannot be overwritten - but it would be very easy to add one (unfortunately I never made my Mew Eclipse environment capable of compiling the code).

Coming back to the 2.6 number. The current approach I have been testing is to put all abilities outside of Shred ahead of the Rip refresh. The first test was ahead of most abilities - except for one that would impact this - the three rip shreds. I will tinker with the script to selectively prioritize the Rip refresh higher and see if I can increase the 2.6 number and along with the overall dps.

Edit: testing with Rip refresh ahead of SR loses 15dps. Putting a check into the Rip Shred makes no difference at all. This code is never hit when we already have 5 combo points (not too surprising). I have been able to push the 2.6 number to over 3, but the net result was the 15dps decrease due to lower uptime on SR.

My guess is that the lack of rip refresh causes the "without C" script to enter the <25% state with 5 CPs, which means one additional FB during the <25% phase, which would match the damage% difference for FB that you report (without C: 2.9%, with C: 2.68%). You didn't paste the Number of Bites, but I guess it's higher in the "without C" case.

A simple solution would be to fudge the 25% BitW threshold so that it doesn't happen always at the same time. In reality what should be done is to change the script so that if it sees that, upon approaching 25%, by not refreshing rip early it can cast one additional FB, then the early rip refresh is ignored. The calculation of the gain in Rip damage is based on the assumption that at that time CPs have no other use, which becomes false as we cross the 25% threshold.

Hello !

I was about to swap my profession in order to get the awesome Synapse Springs and I did some simulations on Mew just to be sure I was not mistaken in forgetting LW to become an engineer.
I was rather surprised to see that engineering is about a ~50 DPS loss on my toon according to Mew and I don't find any reason to explain this DPS drop. Why Mew shows Synapse Springs as being under any +80 agi from other professions?
(I correctly reduced my agility by 80 when swapping my professions on Mew.)

I mean, this great activated +480 agi mini-trinket timed with TF to refresh our dots for full duration with a big AP boost and which produces a big energy pool to get the most out of it should be better than other professions, I am right?
Do you think that Synapse Springs may not be modeled correctly or timed with TF in Mew's script?
I dare not change my profession as Mew does not confirm to me that's a good decision. I'm not sure about my estimates on Synapse Springs.

Rawr seems to consider that both professions are exactly equal, which I do not really think is correct neither...

Rawr uses basic formulation, and the obvious easy way to model it would be to simply treat it as 80 agility when averaged over time. Mew Formulation does the same thing. At the moment, Mew Simulation simply uses the Springs every time it's off CD, not attempting to synch it.

If you glyph TF, attempting to line synch up Synapse Springs will probably be a DPS loss. If you glyph Berserk instead, the Mew seems to indicate a small DPS increase. Not sure why it is showing up as a DPS loss with Tiger's Fury glyphed, my guess is that it's spending more time desynched that it would normally be averaged over an infinite fight duration.

Of course I plan to use the glyph of Berserker in order to synch SS with TF!
My bad, I didn't checked the boxes, especially High Resolution Timer. I've just done the simulations once more and Synapse Springs appears to be a ~+47 DPS increase for my toon so I'll finally go for engineering.

Thank you very much for your advices.

Mew-20110412 is now available.

Major changes since last release:

• Dark Intent's periodic damage increase is now 1/2/3% per 4.1 PTR patch notes.
• Interrupts are reliable per 4.1 patch notes.
• Simulation is now the default model for all new profiles.
• The Simulator now allows for casting Rebirth/Tranquility durring the encounter.
• Furor and Predator's Swiftness are now modeled by the Simulator.
• Spell Vulnerability/Haste/Crit Taken are specifiable buffs/debuffs (Mostly used for Tranquility/Rebirth, also affects certain trinkets).
• New Simulator script calls getBerserkBaseDuration(), getEncounterDuration(), getElapsedTime(), and isAutoAttackEnabled()
• New Simulator script actions AUTOATTACK_START, AUTOATTACK_STOP.
• The Simulator now expects the script to manage the swing timer.
• Formulation no longer uses Ferocious Bite at all over 25% mob HP.
• New option that will cause Mew to model Glyph of Shred as +1/1/2 ticks.
• BUG: Change potion cooldown. (Was 60 sec is now 120 sec, no DPS impact for encounter durations worth modeling.)
• BUG: Apply the ToTT multiplier to trinket sourced damage procs. (DMC:H is still sub-par compared to other options.)
• BUG: Stampede buff duration is now always 8 sec regardless of the number of points in the talent.
• Numerous other internal changes, please see the SVN commit logs if you are curious.

Note: If you have a custom script, please look at the documentation in the google code wiki or the example script to ensure that you start the swing timer.

As usual questions/comments/bug reports appreciated.

I updated my sim script to include the updated sim script that Yawning just released along with modifications to my two scripts that incorporate changes to work with the new Mew release (the external buff code is the same in all three scripts and the interrupt and FC code is close to identical).

In my so-called "universal" script, there is a variable, "rotation" that will use the default Mew script if set to "0", my script if set to "1" and an experimental script if set to "2". The experimental rotation currently emulates the Atremedes fight.

The script can be found here: The Fluid Druid - View topic - Leafkiller's 4.0.6 Feral Ovale Script

For anyone using my script, please keep the following in mind: