OOTPOU for OOTP 9

[satchel]

Can the "development tracker" track changes in potential? I'm running a talent-only league, and the development tracker gives me a "can't divide by zero" error when I try to run it.

[fhomess]

Originally Posted by satchel

Also, what number should I put in as the playoff odds "Pythagorean exponent?"

2.00 was the exponent originally proposed, although I believe that 1.83 is now a commonly accepted exponent as being slightly more accurate. Of course, you could use the Pythagenpat option, in which case the value you enter in this field is irrelevant as the utility calculates an exponent for each team based on their run ratio.

[satchel]

Originally Posted by fhomess

... 1.83 is now a commonly accepted exponent as being slightly more accurate. Of course, you could use the Pythagenpat option...

I don't remember seeing the Pythagenpat option, but I want to try it.

The error I'm getting is in line 109, line 2 of the Utils.pm file. I looked at that file in an editor, and there is no "integer" definition on the equation on line 109, whereas there is such a definition on the two similar preceeding equations. Should I try to insert the change, and put the integer restriction on that equation too, to solve my "division by zero" error?

Here's the part of the code I'm talking about:

    if ($talScale == 8) {
        $newTal = int(($inTal+66)/33);
        $newTal = min(8, $newTal);
        $newTal = max(2, $newTal);
    }
    elsif ($talScale == 80) {
        my $factor = int(200/13);
        $newTal = int(($inTal+$factor-5)/$factor);
        $newTal = min(13, $newTal);
        $newTal = max(1, $newTal);
        $newTal = ($newTal*5)+15;
    }
    else {
        my $factor = 200/$talScale;
        $newTal = int(($inTal+$factor)/$factor);
        $newTal = min($talScale, $newTal);
        $newTal = max(1, $newTal);

I'm thinking that maybe changing my $factor = 200/$talScale; to my $factor = int(200/$talScale); might solve this?

I did experiment with changing the "rating" scale in the Administration settings to a numerical value instead of putting it at "scouting" and I still got the error.

What does the Development Tracker's command Generate links—Generates the development links in the player HTML pages do? I've executed this command, in order to set up the Development Tracker, but I can't tell what it does. The explanation seems to say that it inserts some kind of link on the player html report pages, but I ran the command and haven't seen any links appear on player pages.

[satchel]

Our league is running the All-star voting utility, and we can't see how to vote for pitchers.

Edit: I suppose that the ballot for pitchers' comes up after the ballot for batters is filled out and submitted.

[satchel]

I've run our Development Tracker with "Ratings" activated, and it worked, but it's displaying both current ratings and talent ratings increases, and we're a talent-only league, so we want to see talent changes only, not ratings changes as well. Is there a way to see only talent ratings changes?

[Getch]

Originally Posted by satchel

I've run our Development Tracker with "Ratings" activated, and it worked, but it's displaying both current ratings and talent ratings increases, and we're a talent-only league, so we want to see talent changes only, not ratings changes as well. Is there a way to see only talent ratings changes?

Sigh... no. Didn't think of that type of setup. I'll look into it.

[satchel]

Thanks very much! Contribution coming your way.

[Solonor]

Originally Posted by Solonor

I have been using the original Dev Rept forever, but I never got around to updating and putting in the rest of the mods. Finally, at kq76's urging, I did and they're great!

However, I have two issues:

1. The Ratings Report only shows 1 player no matter what sorting parameters or team (including FA's).

2. The Playoff Odds Report is picking 2 wild cards when we only have 1.

(using OOTP8 for now)

I fixed the ratings report (there was a stray "1" at the bottom of the Ratings.pm file).

Fixed the wild card issue by commenting out the 2nd wild card code.

[sporr]

Originally Posted by Solonor

Fixed the wild card issue by commenting out the 2nd wild card code.

Which file do I find this in?

[etothep]

If I don't understand much of what the readme file says, should I just assume I shouldn't use this?

Or is there a sparknotes version of just what this does? Not big into all the technical jargon is all

[Solonor]

Originally Posted by sporr

Which file do I find this in?

LSAdmin.pm

[satchel]

Originally Posted by etothep

Or is there a sparknotes version of just what this does? Not big into all the technical jargon is all

Here's a link to my league's Getch's Utilities page. We have the Development Tracker turned off, it's usually available, too.

Those links at the top of the page, Allstar-Draft-Exports-Last Sim-Managers-Profile-Ratings, show the various tools included in the suite of Utilities.

[sporr]

Originally Posted by Solonor

LSAdmin.pm

Thanks for the info. Which lines in there should I comment out?

[Solonor]

Originally Posted by sporr

Thanks for the info. Which lines in there should I comment out?

########### Find Second Wildcard Winners ###########
# if ($nDivs % 2 == 0) { #only do second wildcard if even number of divisions
# foreach $subleague (sort {$a <=> $b} (keys %subLeagues)) {
# $subLeagues{$subleague}->{WC2WINS} = 0;
# $subLeagues{$subleague}->{WC2WINNERS} = 0;
# foreach $team (sort {$teams{$b}->{SEASONWINS} <=> $teams{$a}->{SEASONWINS}} (keys %teams)) {
# if (($teams{$team}->{SUBLEAGUE} eq $subleague) && (($teams{$team}->{DIVWINNER} + $teams{$team}->{WC1WINNER}) != 1)) {
# if ($teams{$team}->{SEASONWINS} > $subLeagues{$subleague}->{WC2WINS}) {
# $subLeagues{$subleague}->{WC2WINS} = $teams{$team}->{SEASONWINS};
# }
# }
# }
# } #End of Wildcard Subleague loop
########### Find First Wildcard Winners ###########
# foreach $team (keys %teams) {
# if (($teams{$team}->{SEASONWINS} == $subLeagues{$teams{$team}->{SUBLEAGUE}}->{WC2WINS}) && (($teams{$team}->{DIVWINNER} + $teams{$team}->{WC1WINNER}) != 1)) {
# $teams{$team}->{WC2WINNER} = 1;
# $subLeagues{$teams{$team}->{SUBLEAGUE}}->{WC2WINNERS}++;
# }
# }
# foreach $team (keys %teams) {
# if ($teams{$team}->{WC2WINNER} == 1) {
# $teams{$team}->{WCTITLES} += 1 / $subLeagues{$teams{$team}->{SUBLEAGUE}}->{WC2WINNERS};
# $teams{$team}->{WC2WINNER} = 1 / $subLeagues{$teams{$team}->{SUBLEAGUE}}->{WC2WINNERS};
# }
# }
# } #End of second wildcard IF block

[sporr]

Originally Posted by Solonor

a lot of code

Much thanks!

[mikev]

Hey Getch, is there any way that the draft utility can be used for an inaugural draft?

[fhomess]

Originally Posted by satchel

I don't remember seeing the Pythagenpat option, but I want to try it.

The error I'm getting is in line 109, line 2 of the Utils.pm file. I looked at that file in an editor, and there is no "integer" definition on the equation on line 109, whereas there is such a definition on the two similar preceeding equations. Should I try to insert the change, and put the integer restriction on that equation too, to solve my "division by zero" error?

Here's the part of the code I'm talking about:

    if ($talScale == 8) {
        $newTal = int(($inTal+66)/33);
        $newTal = min(8, $newTal);
        $newTal = max(2, $newTal);
    }
    elsif ($talScale == 80) {
        my $factor = int(200/13);
        $newTal = int(($inTal+$factor-5)/$factor);
        $newTal = min(13, $newTal);
        $newTal = max(1, $newTal);
        $newTal = ($newTal*5)+15;
    }
    else {
        my $factor = 200/$talScale;
        $newTal = int(($inTal+$factor)/$factor);
        $newTal = min($talScale, $newTal);
        $newTal = max(1, $newTal);

I'm thinking that maybe changing my $factor = 200/$talScale; to my $factor = int(200/$talScale); might solve this?

I did experiment with changing the "rating" scale in the Administration settings to a numerical value instead of putting it at "scouting" and I still got the error.

What does the Development Tracker's command Generate links—Generates the development links in the player HTML pages do? I've executed this command, in order to set up the Development Tracker, but I can't tell what it does. The explanation seems to say that it inserts some kind of link on the player html report pages, but I ran the command and haven't seen any links appear on player pages.

I presume you have the ratings or talent scale set to "Scouted". If you do this, then $talScale = 0 in the above equation, so the factor is divided by 0.

Add another elsif statement to handle that case as follows (this will hide the ratings/talents when set to "Scouted"):

    if ($talScale == 8) {
        $newTal = int(($inTal+66)/33);
        $newTal = min(8, $newTal);
        $newTal = max(2, $newTal);
    }
    elsif ($talScale == 80) {
        my $factor = int(200/13);
        $newTal = int(($inTal+$factor-5)/$factor);
        $newTal = min(13, $newTal);
        $newTal = max(1, $newTal);
        $newTal = ($newTal*5)+15;
    }
    elsif ($talScale == 0) {
        $newTal = 0;
    }
    else {
        my $factor = 200/$talScale;
        $newTal = int(($inTal+$factor)/$factor);
        $newTal = min($talScale, $newTal);
        $newTal = max(1, $newTal);
    }

I'm working on some other minor fixes to these utils as well. For example, the background appears gray because the background image is still referencing "si" in the image file name instead of "bnn", which was a switch made when OOTP parted ways with Sports Interactive.

[fhomess]

Ok, I've created a patch for the OOTPOU utilities. I've tested this out on two of my own leagues, but there could still be some issues. If so, just let me know and I'll do my best to fix them.

OOTPOUpatch.zip
(A Readme file is included in the zip)

Enhancements:
1. Added pythagenpat option to Playoff Odds calculator.
2. Export tracker will now display league file date, with old team exports appearing in red text and new team exports appearing in blue text.

Fixes:
1. Playoff odds report now shows pythagorean losses instead of team losses, so Pyt.Rec column is correct.
2. Playoff odds report now correctly shows 1 wild card winner with odd number of divisions and 2 wild card winners with even number of divisions.
3. Background image and BNN logo image at bottom of reports now correctly appear (previously referenced SI images in the file names).
4. Fixed divide by zero error when using the "Scouted" option for ratings or talent scales. This option will now hide those ratings on the ratings page.

[fhomess]

Originally Posted by fhomess

Enhancements:
2. Export tracker will now display league file date, with old team exports appearing in red text and new team exports appearing in blue text.

Just to clarify, new vs. old exports will be relative to the league file date. So if the commish, for some reason, re-uploads the league file, it's possible that a new export will appear as old relative to the new date.

[satchel]

Frank, thanks a ton for these fixes.

I had been looking for the Pythgenpat since it had been mentioned.