Page 2 of 8 FirstFirst 1 2 3 4 5 6 7 8 LastLast
Results 16 to 30 of 111

Thread: 11.19 Computer Trades

  1. #16
    Join Date
    Jun 2006
    Location
    Edison, NJ
    Posts
    15,636

    Re: Computer Trades

    True, I was just making a point is all.
    You insist that there is something a machine cannot do. If you will tell me precisely what it is that a machine cannot do, then I can always make a machine which will do just that! -J. von Neumann

  2. #17
    Join Date
    Aug 2002
    Location
    New Jersey
    Posts
    44,491

  3. #18
    Join Date
    Apr 2008
    Posts
    1,224

    Re: Computer Trades

    I've had the same thing, especially with Florida. Hanley Ramirez will probably be a guy we tell our grandkids about, but they keep trading him by 2010 almost every time. Plus, he makes the minimum salary. Also, Nick Markakis on Baltimore. He is the the guy they are building their team around for the future. He ends up on another team almost every time. What kills me is that they always trade way up in salary.

    I hate to say this, but maybe there should be a franchise setting on certain young players.

  4. #19
    Join Date
    Mar 2007
    Location
    Cleveland, OH
    Posts
    2,861

    Re: Computer Trades

    Quote Originally Posted by ohms_law View Post
    True, I was just making a point is all.
    Hm...and what's this point?

    True, the AI wouldn't have used commissioner ratings when it made its trade...but it wouldn't have used my team's either. I suppose I could have gone in under CLE and SD to see what they 'thought' of the trade...but commissioner mode DOES tell us whether, objectively, it was fair.

    It might be worth noting that CLE's scouting is a B, SD's a C in that particular example.

    If B and C scouting is so far off that it makes the AI think that trade is balanced, then I would suggest we have a bigger problem than the computer "piling players on" and that FRS is absolutely right, expenses need to be fixed and/or the scope between A and D scouting/farming narrowed SUBSTANTIALLY.
    Retired Dynasties I'm Proud of
    To Rule in Kansas City Part I and Part II (Kansas City Royals 1969-73, Hall of Fame)
    Cardinal Sins (St. Louis Cardinals 1976-78) and it's sequel:
    Diverting Destiny (Montreal Expos 1994)
    Script for my Requiem (New Orleans Blues (fictional) 1954)

  5. #20
    Join Date
    Jun 2006
    Location
    Edison, NJ
    Posts
    15,636

    Re: Computer Trades

    Define "balanced". In terms of perceived value, I guarantee that the trade is balanced, since that's the way the program is written. In terms of how useful that perceived value actually is though... That's a whole different story.
    You insist that there is something a machine cannot do. If you will tell me precisely what it is that a machine cannot do, then I can always make a machine which will do just that! -J. von Neumann

  6. #21
    Join Date
    Mar 2007
    Location
    Cleveland, OH
    Posts
    2,861

    Re: Computer Trades

    Hm. Maybe you can define how the computer evaluates players then.

    Completely ignoring where the players wound up (as we know the AI doesn't look at the entire team,) I'm looking at a 70/71, 65/66, 80, 67/68, 85 and 71/72, only one of these players (well) past their prime, balanced against a 79/80.

    Now, SD *is* substantially over budget, so I could buy a payroll dump strategy as this would pretty much bring them into balance. However, the two minor leaguers (65/66, 67/68) don't help that strategy and (shouldn't) be an incentive to CLE.

    How bad does their scouting have to be to convince SD that giving up an 80 AND an 85 (along with assorted others) is worth a 79/80? What are these parameters for balancing trades that I'm not seeing?
    Retired Dynasties I'm Proud of
    To Rule in Kansas City Part I and Part II (Kansas City Royals 1969-73, Hall of Fame)
    Cardinal Sins (St. Louis Cardinals 1976-78) and it's sequel:
    Diverting Destiny (Montreal Expos 1994)
    Script for my Requiem (New Orleans Blues (fictional) 1954)

  7. #22
    Join Date
    Mar 2007
    Posts
    19

    Re: Computer Trades

    There are some pretty simple ground rules we should be able to tell the AI to go by in trades (with other AI teams or with a human team):

    1. Players with Overall below about 78 and Peak below 80 have no trade value unless the team acquiring one is (a) in contention and (b) plugging a gaping hole in their roster. (If the top 2B in the organization is a 66/72 guy, they might be interested in acquiring somebody's 77/77 guy.) Such players should be ignored in a trade.

    2. Cap trades at 6 players per side. I can't remember the last time I saw a trade with more than 6 players going in either direction.

    3. Increase the trade value assigned to a player's Peak rating a little. A young 65/95 player should be more valuable in a trade than the AI currently believes he is.

    4. Increase small market teams' urgency to trade star players who are about to go FA at the deadline, if they're not in contention. Similarly, increase any non-contending team's urgency to trade medicore-to-good veterans for whatever they can get around the deadline. This just keeps things interesting.

  8. #23
    Join Date
    Aug 2002
    Location
    New Jersey
    Posts
    44,491

    Re: Computer Trades

    Some of these trades are making less and less sense. For example, the Marlins sent Hanley Ramirez to the Mets for:

    Carlos Delgado, Moises Alou, Ryan Church, Pedro Martinez, Ruddy Lugo, Raul Casanova, and Brant Rustich.

    This trade is total nonsense for both sides. The Mets already have Jose Reyes. The Marlins just gave up their top shrotstop making the league minimum for 3 old injury-prone expensive guys (Delgado, Alou, Martinez) and others. Hanley Ramirez ended up playing a pinch-hitter role for the Mets.

    Oh, and then, just for good measure, the Marlins later sent Delgado back to the Mets (in the same season) for a minor league pitcher. They also shipped off Pedro and Church to other teams later on.

    I think this should be an urgent fix

  9. #24
    Join Date
    Jun 2006
    Location
    Edison, NJ
    Posts
    15,636

    Re: Computer Trades

    The frequency needs to be dialed back down some. That's the immediate problem, anyway. As I've been saying though, the larger problem is simply awareness. The value of these deals, considering the contracts and the player's skills, may be OK, but they don't consider the impact on the teams at all. The AI lacks team awareness.
    You insist that there is something a machine cannot do. If you will tell me precisely what it is that a machine cannot do, then I can always make a machine which will do just that! -J. von Neumann

  10. #25
    Join Date
    Aug 2002
    Location
    New Jersey
    Posts
    44,491

    Re: Computer Trades

    I can't figure out how that Mets-Marlins trade has equal value...but nonetheless, it seems like it doesn't even take into account its own financial status, except "we're small-market, trade!" and then it makes trades without regard to finances. Trading a league-minimum star player for 3 high-priced guys in their late-30's and early-40's is ridiculous.

  11. #26
    Join Date
    Jun 2006
    Location
    Edison, NJ
    Posts
    15,636

    Re: Computer Trades

    ummm... yea, I see your point.
    You insist that there is something a machine cannot do. If you will tell me precisely what it is that a machine cannot do, then I can always make a machine which will do just that! -J. von Neumann

  12. #27
    Join Date
    Apr 2008
    Posts
    135

    Re: Computer Trades

    Rate players primary/secondary position. Auto sort lineup and rotation (including minors). Calculate team value. Create new auto sort using proposed trade. Compare team rating. Calculate proposed salary differential in terms of budget/current standings. Accept/Reject/Counter-offer.

  13. #28
    Join Date
    Aug 2006
    Location
    Waterloo, Ontario
    Posts
    5,684

    Re: Computer Trades

    I think that having the AI look for holes in the team, where certain guys fit in, etc., this would solve a lot of the bad trades. As the AI would primarily trade for needs with places where they have extra talent.
    Active Dynasty
    Meeting Success: A New Regime - Follow us as etothep chronicles me and eddie's efforts to bring a championship back to Queens

    Paused Dynasties
    The Goose continues the Hawk's battle for Capital Hill
    Une Rève Réaliser: Les Expos de Montréal (1969-)

    Retired Dynasties
    The San Diego Padres, into a Friar Destiny (with Jeffy25 and Ragecage)
    A New Era Takes Flight - The 2008 Toronto Blue Jays
    The Blue Birds: A new Era

  14. #29
    Join Date
    Jun 2007
    Location
    Kent, WA
    Posts
    7,613

    Re: Computer Trades

    I just had one with the Marlins using HGM roster (not sure if it makes any difference) v11.09

    TO STL
    Dan Uggla (MLB) 390k
    Josh Willingham (MLB) 390k

    TO FLA
    Yadier Molina (MLB) 3.87M
    Todd Wellemeyer (MLB) 1M
    Hugo Castellanos (72/75) (AAA) 30k
    Troy Glaus (MLB) 11.78M
    D'Angelo Jimenez (BENCH) 390k
    Anthony Reyes (MLB #3 STARTER) 390k
    Josh Phelps (AAA) 30k
    Cliff Polite (AAA) 30k
    Adam Kennedy (MLB) 3.75M

    I wouldn't say this deal is HORRIBLE, but the Cardinals obviously shed a bunch of payroll and the Marlins now have a higher payroll than their budget mainly due to an aging Troy Glaus

  15. #30
    Join Date
    Aug 2007
    Posts
    399

    Re: Computer Trades

    Are the AIs of some teams "dumber" than other teams? The AIs of the Marlins, Orioles and Reds seem to be mentally handicapped, while there are other teams (Red Sox) who consistently steal big talent from other teams. My examples from a general discussion thread.

    If some teams are programmed to be stupid, making them more like the smart teams would go a long way toward fixing the imbalanced trade problem.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •