< Earlier Kibitzing · PAGE 56 OF 56 ·
|Feb-02-19|| ||virginmind: Hi <AylerKupp>, great wines in the Cochem region too - I stayed there for a week and the owner of the house had a vineyard in the area. We most probably passed through Ayl once, while going from Trier to Saarburg.|
|Feb-02-19|| ||AylerKupp: <virginmind> Thanks. I am not familiar with the wines from Cochem. In fact, I had never heard of them and they are not mentioned in any of my wine books. After a little research I found that they're from a region in the Mosel usually dismissed by wine writers, probably unjustifiably, particularly in hot years. But I suspect that there are an almost infinite number of unknown small regions in the world where the combination of soil, weather, and tradition allows fine wine to be made in small quantities. It would be impossible for anyone to be familiar with even a majority of them.|
I'm fairly sure that if you went from Trier to Saarburg that you passed though Ayl as it is on the main road between the two just north of Saarburg. And the Ayl vineyard is just north of the city of Saarburg. Someday I hope to travel through the German wine regions, at least the major ones.
You've just whetted my appetite. I think I'll go down to my cellar and chill a bottle of German wine for dinner.
|Feb-03-19|| ||virginmind: I guess others around may be better known. We just missed a wine festival which took place in Cochem a few days before. I don't drink much, but of course I'm aware of Riesling. Vineyards were scattered pretty much everywhere along the Mosel valley, but we were mostly interested in castles and such - amazing touristic region.|
Actually, close to where I live (Iasi), there is Cotnari vineyard, which is rather famous in Romania for its wines - maybe you heard of it too?
|Feb-06-19|| ||AylerKupp: <virginmind> I am not too familiar with eastern European wines and I have never had a Romanian wine. In fact, I have never heard of any of them. I have had Hungarian wines, Tokaj for sure (I even have some in my cellar since they live a long time) and some dry white wines from Lake Balaton but that was a long time ago. And (I think) I've had some Croatian wines as well. Plus some Austrian wines, mainly Riesling and Gruner Veltliner.|
The large wine store where I do most of my wine buying (I'm good friends with the owner) doesn't carry any. I live in Los Angeles, CA and searching the web for Romanian wine retailers in Los Angeles didn't show any. So it doesn't look like I will have an opportunity to try any time soon. I may have to wait until I visit Romania.
I did find a reference to Romanian wines in what I consider to the best book about wine ever written by far (I have 5 different editions dating back to the first one in 1971!), "The World Atlas of Wine" by Hugh Johnson and Jancis Robinson does have 2 pages (and that's all!) covering Romanian wines. But that's 2 more pages than any of my other wine books! It does have 4 pages of Hungarian wines, 1 page of Czech Republic and Slovakian wines, 1 page of what they call "Western Balkans" (Bosnia, Serbia, Albania, Montenegro, and the Republic of Macedonia), 2 pages on Croatian wines 2 pages on Slovenian wines, and 2 pages on Bulgarian wines besides the 2 pages on Romanian wines. So that's 14 pages of eastern European wines. If you are interested in learning about wines from all over the world I cannot recommend this book more highly, although it's a little bit pricey, £ 40 per the back cover although I might have gotten it at a discount.
As it's title implies the book is full of beautiful and clear color maps of each and every wine region covered. It shows both the Cotari region and winery as well as Iasi. The Cotari winery has a nice web page although, of course, it is oriented towards selling wine. A little more research showed me that Cotari is known for its sweet white wines and that they seem to age reasonably well.
I did find the location of the Consulate General of Romania in Los Angeles which happens to be not far from where I buy most of my wines but, needless to say, they didn't advertise any Romanian wine (or any other wine for that matter!) for sale.
|Feb-07-19|| ||virginmind: Los Angeles!? I thought you're from the Saar region! Well, that makes sense why no Cotnari (as it's spelled, not Cotari) wine over there, it's a bit far away. Although I suspect there may be some Romanian wines imported somewhere in California...Oh well, ha ha, right, I wouldn't expect our consulate to sell or advertise wines...|
Come to think of it, Cotnari winery is also sponsoring our local chess club, Politehnica Iasi. In fact, there's a bottle of "Feteasca Alba" of Cotnari on our kitchen table right now but, as I said, I don't drink much - I get headaches from it. It's indeed semi-sweet, although Cotnari also produce a dry wine, "Francusa".
It's pretty obvious from what you write that wines are indeed a big passion for you, congratulations! I can only imagine how such a tasty passion can warm your life. I doubt I will buy that book any time soon, but thanks for signalling it to me.
Actually you're right, apparently no trace of Cotnari selling in California, but I found a link for a reseller in Niles, Illinois (coincidence, it's the American state I've been staying in for a year, back in 1994-95): https://1000corks.com/wine/Cotnari
Bottles are pretty cheap as you can see and you may want to order a couple just for a taste of sweet Moldavian hills :) (Moldova is the name of the Romanian province where Iasi and Cotnari are situated - not to be confused with Moldova, a country neighboring Romania, which once used to form together a bigger Moldova. But that's another story.)
|Feb-09-19|| ||AylerKupp: <virginmind> All my references do say "Cotnari" and not "Cotari" so I guess that I just dropped the "t" when I wrote it down. And my spell checker didn't have either word in its database so it was useless in detecting the error. Sorry about that.|
But I did find a source of Romanian wines at a wine store not far from me at very low prices, all from Recas Castle winery. They have the international varieties Pinot Noir, Cabernet Sauvignon, and Pinot Grigio which would be interesting to try to see how they compare with the same grapes from regions I'm familiar with as well as Romanian varieties like Feteasca Regala (white, presumably dry) and Feteasca Neagra (which even I can tell from the name that it's red). Even more interesting they have two single-vineyard Feteasca Neagra and Cabernet wines, which should be more distinctive than the generic versions of the same varietals.
Yes, I'm fairly passionate about wines. I was introduced to fine wine by my future father-in-law almost 50 years ago when I was in college and have been passionate ever since. Since I didn't have much money in those days we struck a deal, I would wash his car for 1 bottle and I would wax it for 3 bottles. And my interest in his daughter also lasted since we celebrated our 47th wedding anniversary in late December of last year and this March we will be celebrating the 50th anniversary of the day we met.
Too bad about wine giving you a headache. Some of my friends get headaches after drinking red wine but not after drinking white wine but unfortunately that's not the case with you. I've found that taking some aspirin before or right after drinking wine seems to help them. Fortunately I seem to be "immune" to the problem. You might also try wine made from grapes low in tannin such as Pinot Noir and Gamay, the latter from Beaujolais. I like to cook and I typically use these or Zinfandel (a local California wine) when making stews because they are low in tannin and so don't become bitter when reduced in volume during cooking.
And, as a student of history and European history in particular, I am familiar with the history and "evolution" of Moldavia/Moldova/Bessarabia/Wallachia/Dobruja/Bu-
kovina, etc., so I wouldn't be one to confuse them. Another story, as you said. I did find the following interesting *.gif graphically summarizing the historical expansion/contraction of Romanian territory from 1859 through 2010: https://upload.wikimedia.org/wikipe...
Nice chatting with you. The world of chess is such an interesting one and you meet all sorts of nice people although, unfortunately, some not so nice ones as well. But I think it's worth it.
|Apr-03-19|| ||MrMelad: Continued discussion from the AlphaZero page
<Trolling, like beauty, is often in the eye of the beholder.
as a US Supreme Court Justice once said about pornography, "I can't define it, but I sure recognize it when I see it." Or words to that effect.>
I wouldn't compare your posts to pornography but admittedly sometimes it does feel like that... And not in the good sense! :)
But seriously, by definition trolling is a <deliberate> attempt to provoke. As long as your posts reflect your honest opinion and are not meant to provoke then you are fine by me even if the disagreement continues and the debate becomes circular.
Long posts can be informative or they can be pompous and boring and often they are both. I think that complicated issues often requires long posts and discussions that somtimes range over a lot of time.
"round and round" discussions can sometimes converge as the rounds becomes smaller until they encompass exactly the source of disagreement.
<So I suppose that could put me on your ignore list which, as I've said before, indicates that you have good judgment>
I'm happy that your style is not dependent on what people think of it, but I don't understand your willingness to admit of any wrong doing. People that ignores you doesn't have "good judgement" they have different taste.
There's a psychological approach which I very much agree with, it's called - I'm OK, you are OK. It's basically arguing that people can have 4 different types of interaction with other people:
1. I'm not OK you are not OK
2. I'm not OK you are OK
3. I'm OK you are not OK
4. I'm OK you are OK
The point is that the fourth type of interaction is the best approach to life and most healthy and the first type is the worst.
I hope I don't come off as condescending when I say I recommend both the approach and the book.
<if you don't put me on your ignore list, take the chance that my occasional although infrequent posted pearl of wisdom is worth the aggravation of suffering from reading my verbose and alleged troll-like posts>
I've never considered ignoring you as I've learned from your posts. I think you add a lot to many discussions and topics. I apologize if I gave the wrong impression, I'd like to restate that we have agreed on most of points we've discussed and that I respect your point of view on the things we don't.
In any case, thanks for the debate.
|Apr-03-19|| ||diceman: This is interesting.
I made an improvement on an Uhlmann
game. I also played out a few moves
after the improvement, and came to the conclusion the position was equal.
To test my analysis I ran the game fragment through CG's StockFish.
Here is the position of interest:
click for larger view
White has just played b2 to b4, as you
can see black's bishop is trapped, he must play cxb3 en passant.
Incredibly, the pgn gives cxb3 a question mark, and recommends Bxf2+ ???
Here is the relevant pgn:
<14.b4 cxb3 ? 14...♗xf2+ 15.♖xf2 +- +3.52 (26 ply) 15.Nxb3 = +0.23 (28 ply)>
So StockFish recommends a move for black that's +3.52 @ 26 ply, and questions a move that's +0.23 @ 28 ply.
Exactly the opposite of what it should be doing.
You almost get the idea it doesn't know it can capture en passant. However, since my pgn had cxb3 as the move StockFish says: Yup, it's equal.
I don't know if it's a StockFish issue,
or something to do with CG's StockFish?
|Apr-06-19|| ||AylerKupp: <<MrMelad> Regarding the personal stuff, I've posted in your forum, I hope it's okay with you.>|
Absolutely! I welcome any comments to my posts whether I agree with them or not. And my forum is a good place for them. My only concerns are that (a) I don't visit my forum too often so there may be a lag between when someone makes a post and I answer it and (b) sometimes it's not obvious what the context of the post is if it's related to a post on a different page. So please bear with me.
As far as your post above, yes, I can see why you (and others) might consider them to be like pornography, and that's why I like the second definition better. After all, if my posts are like pornography then they must be clear and not fuzzy. Alas, I typically fail at that. But it then becomes a win-win situation, if they are fuzzy, then they are art. ;-)
<"round and round" discussions can sometimes converge as the rounds becomes smaller until they encompass exactly the source of disagreement.>
Unfortunately convergence for these "round and round" discussions is not guaranteed, and we often quickly reach the point of diminishing returns when considered the time and effort put into creating a reasonably well-thought out response. Sometimes it's just best to agree to disagree and move on to other things. After all, "the more you run over a dead cat the flatter it gets." But that's another story.
<don't understand your willingness to admit of any wrong doing.>
That's just another way of trying to break a deadlock. If you take responsibility for wrong doing for a situation, even though you don't think you did anything wrong, that sometimes lets you move on to more important things. After all, who is "right" and who is "wrong" is usually not relevant, it's the issues that are important.
One time during a meeting involving about 15 people I took responsibility for an action. After the meeting my boss' boss asked me "How could that possibly have been you fault?" My response was "It wasn't. But why should 15 people's times be wasted for about 20 minutes trying to determine who was right and who was wrong? Better to get that out of the way without wasting those 15 people's times and get down to the problem that we were trying to solve." I think that my boss' boss liked my attitude.
|Apr-06-19|| ||AylerKupp: <Personal stuff Ė continued> |
<There's a psychological approach which I very much agree with, it's called - I'm OK, you are OK. >
I remember that book. But sometimes someone <is> right and someone <is> wrong, and it's important to determine which one is what. Hopefully it can be done constructively and with civility, but it must be done regardless. But there should not be any reason to get personal about it.
The 4 interactions you mentioned reminded me of a chart that I used to present at kick-off meetings for new projects. It was titled "If you do what I say" and it went something like this:
1. If you do what I say and it turns out well, we'll both be praised for our good judgment.
2. If you do what I say and it doesn't turn out well, I'll be blamed for my poor judgment.
3. If you don't do what I say and it turns out well, you'll be praised for your good judgment.
4. If you don't do what I say and it doesn't turn out well, you're screwed.
<I've never considered ignoring you as I've learned from your posts. I think you add a lot to many discussions and topics. I apologize if I gave the wrong impression, I'd like to restate that we have agreed on most of points we've discussed and that I respect your point of view on the things we don't. In any case, thanks for the debate.>
Again, suggesting that people put me on their ignore list is another way of trying to terminate what I consider a less than productive discussion and move on to other things. Besides, since the number of people you can put in your ignore list is limited, I look forward to the quandary those people will eventually face if they eventually try to add someone else to their ignore list and find out that in order to do so they must delete someone from it. Decisions, decisions. :-)
And no, I don't think that you gave me the wrong impression. The main point that I was trying to make was that there are times when you want to know the best implementation (hardware + software) of a solution to a problem and there are times when all you want to know is the best software implementation. That's all. And after all, our motivations and interest for preferring one over the other may change in the near future; "Indecision is the key to flexibility". (same story as the dead cat's story).
|Apr-08-19|| ||MrMelad: <AylerKupp> I appreciate the time you invest in your comments and also your positive thinking and optimism. I value your many contributions in this site on many topics. |
Regarding our discussion in the AlphaZero page I think it has reached a point where both of us made our best case and we should either wait for others to chip in or just let it be.
|Apr-15-19|| ||AylerKupp: <<BOSTER> What is the difference between usual tree Search for engine (Kotov) and Monte-Carlo Tree Search, based for the AZ?>|
First let's make sure we're talking about the same thing. Here is what I think is a summary of the differences between search tree expansion and pruning in both classic engines (per Shannon's original 1949 paper "Programming a Computer for Playing Chess" (https://vision.unipv.it/IA1/aa2009-... ) as used by Stockfish, Komodo, etc. and an MCTS-like search tree expansion and pruning as used by AlphaZero ("Mastering Chess and Shogi by Self-Play with a General Reinforcement Learning Algorithm", ((https://arxiv.org/pdf/1712.01815.pdf (not much on MCTS), "A general reinforcement learning algorithm that masters chess, shogi and Go through self-play" https://deepmind.com/documents/260/... (better), and the "Game Changer" book (the easiest to follow, but ...) by Mathew Sadler and Natasha Regan) and "Technical Explanation of Leela Chess Zero" by Andy Olsen, https://github.com/LeelaChessZero/l... ). Both AlphaZero articles were written by members of the DeepMind team and they assisted the authors of "Game Changer". Be aware that there are contradictions on how MCTS is implemented in AlphaZero (if at all!) in all 3 papers and the book, so I'm not really sure how AlphaZero implements MCTS or its apparently close derivative, PUCT.
I'm aiming to highlight the similarities between the two approaches (of which, at a high level, there are many) and the differences, although of course there are many details I've left out, mainly because, sadly, I don't know them. :-(
Part 1 of 3: <Classic>
1. Start with the current game position (the search tree root) and identify all legal candidate next moves.
2. Select the "most promising" candidate next moves based on heuristics (which differ from engine to engine). The heuristics represent "educated guesses" as to which moves will be the roots of the branches of the search tree that are most likely to contain the best moves.
3. Evaluate the resulting position for the most promising next moves by means of a hand crafted evaluation function which returns an evaluation function based on centipawns.
4. Expand the tree by repeating the process for all the most promising candidate moves at the next level, an using the alpha-beta pruning algorithm to delete from the search tree when at least one move is found to be worse than a previously examined move; such moves need not be evaluated further. I call alpha-beta pruning an algorithm because when applied to a standard minimax tree, it returns the same move as minimax would, but prunes away branches that cannot possibly influence the final decision.
5. Ignoring quiescent search and extensions (which continue expansion of the subtree for a particular move if a response is either literally forced (such as a response to a check) or practically forced (if a recapture is needed to avoid overwhelming material disadvantage), continue to expand the tree until all the most promising moves have been evaluated.
6. Propagate the results upwards to the original root of the tree by selecting the move that, at each level, results in the alternating best (maximum) and worst (minimum) evaluation along each branch of the root tree (hence the name minimax). The intent is to select the branch of the search tree (the Principal Variation) that contains the best moves for each player at each level of the root tree. This assumes that each player will, in turn, select the move that results in the most advantageous position for them.
7. Repeat the process by increasing the depth of the search tree by one ply for the best moves (typically a small number, in the order of 5 or so) selected at each ply until the time management function of the chess engine indicates that it's time to make a move.
|Apr-15-19|| ||AylerKupp: Part 2 of 3 <MCTS (and it's close relative, PUCT)>:|
1. Start with the current game position and identify all legal candidate next moves.
2. Select the "most promising" candidate next moves based on the training of its neural network.
3. "Evaluate" the resulting position by conducting a series of game simulations (playouts) until a result (win, draw, loss) and determine the scoring percentage (no. of wins + number of losses/2) of that move as well as other statistics such as number of wins, probability that the move being examined will be selected (based on the training of its neural network).
At least that's the traditional definition of MCTS. The "A general reinforcement training ...", the "Mastering Shogi by Self Play ..." articles indicate that they obtain the game result probabilities by doing playouts, the "Technical Explanation of Leela Chess Zero" article indicates that AlphaZero (as well as Leela Chess Zero) uses the PUCT algorithm, and "Game Changer" explains the process reasonably well but never actually says that it uses MCTS and is not clear how the game result probabilities are obtained, other than "the percentage represents the prior move probability" without saying how that's calculated. Then again the focus of the book is to provide examples of AlphaZero's play and not to fully describe how AlphaZero works. But all articles and the book basically refer to an MCTS-time tree generation and branch evaluation and selection.
To make matters worse, MCTS-Minimax hybrids have been developed (see "MCTS-Minimax Hybrids with State Evaluations" and "MCTS-Minimax Hybrids with State Evaluations (Extended Abstract"; you must Google them and download them directly) which, of course, claims that combining the two methods yields the best results, at least in some domains. And, also of course, there seems to be some controversy on the suitability of "pure" MCTS for chess applications (see http://talkchess.com/forum3/viewtop...).
4. Expand the tree by repeating the process until a position is found that has not been found and evaluated (examined) before, or a position that ends the game.
6. Propagate the results upwards to the original root of the tree and recalculating the scoring percentage and the other statistics for each branch of the tree.
7. Repeat the process by increasing the depth of the subtree of the move being examined by one ply for those moves in the search tree (again, probably a small number, but I don't know the range of that number) that have the highest expected scoring percentage. Again, the engine's time management function of the chess engine determines when it's time to make a move.
|Apr-15-19|| ||AylerKupp: Part 3 of 3 <Pros and Cons of each>:|
Whenever you have 2 approaches you typically have pros and cons for each. In anticipation of your possible next question, here are some pros and cons to either the classic or MCTS-based approaches to tree searching. Most of these pros/cons are from published literature, some are my opinions and observations. The latter may not interest you. :-)
1. Some claim, as stated above, that MCTS is not that well suited for chess applications, contrary to the views of the DeepMind team and Matthew Sadler.
2. MCTS is supposed to provide a "more human" approach as far as best move selection because it immediately narrows down the best move candidates to consider and reduces these to a small number, just like a GM might do. Mathew Sadler says that "An engine such as Stockfish works on the basis that the evaluation of the best move determines the evaluation of the position" which is horrendously incorrect. Classis chess engines work on the basis that the evaluation of the best <branch> (in the minimax sense) determines the best of the move candidates considered. How to determine the best of the move candidates in a classic chess engine is determined by the search heuristics.
3. Minimax will provide the best answer in terms of what moves to play in a zero-sum game, MCTS will only approximate the best answer. But that apparently is good enough, at least under the conditions under which engine vs. engine chess games are played.
4. (my opinion) A classic chess engine using minimax will always be faced with the horizon effect no mater how deep it searches (see a tongue-in-cheek description of "AylerKupp's corollary to Murphy's Law (AKC2ML) in my header above). Based on the example in "Game Changer" MCTS <seems> to be able to reach deeper search depths in the same amount of time than a classic engine because it is apparently more efficient in identifying the best candidate moves and so it can better control the width of its search tree, narrowing the number of branches it needs to consider in order to dedicate its resources analyzing the most promising moves to get good results. It's unfortunate that I haven't been able to find any sources that list the calculation time and search depths achieved by AlphaZero for each move.
But, like Stockfish's aggressive search tree pruning, this is double edged. Yes, the engine can search deeper but it is also more likely to miss the best moves by both sides. Sadler says that "I think this also explains how AlphaZero might occasionally miss an unusual, 'unfair' tactic in a position. Since AlphaZero is pruning possibilities to consider so early and rigorously, it might discount a non-standard move before it could examine it at the depth required to see its hidden strengths.
5.(my opinion) But perhaps the best indication of the relative merits of minimax with heuristics and alpha-beta pruning vs. MCTS is provided by Komodo 12.x. In addition to its standard classic version, it provides an option to use MCTS instead of minimax, etc. and both engine versions have competed in the TCEC, CCRL, and CEGT engine vs. engine tournaments. In all cases Komodo 12.x standard performed better than the corresponding Komodo 12.x MCTS and achieved higher ratings. But, in fairness, the Komodo 12.x MCTS option is relatively new, likely does not perform as efficiently as the standard version (which has been available for some time in Komodo multicore) and even crashed 3 times in the most recent TCEC tournament. So we might not yet be comparing apples to apples in terms of performance, and the CCRL ratings for Komodo 12.x MCTS version have been increasing faster than the Komodo 12.x standard version. But, when all engine components are basically the same, Komodo 12.x with minimax consistently outperforms Komodo 12.x with MCTS.
Hopefully the above answers at least some of your questions. As usual, there is a lot of information out there in case you want to dig deeper.
|Apr-15-19|| ||AylerKupp: <<MrMelad> Regarding our discussion in the AlphaZero page I think it has reached a point where both of us made our best case and we should either wait for others to chip in or just let it be.>|
I agree, but there are still some things I want to say to clear up some misconceptions based on your last series of posts and offer yet another example of what I've been trying to say.
<<MrMelad> I'm trying to offset some of your claims as they seem to focus around diminishing and discrediting the accomplishments of AlphaZero and Leela.>
I am in <NO WAY> trying to discredit the accomplishments of AlphaZero and Leela Chess Zero. I think (and have said) that AlphaZero deserves a huge amount of credit for their ability to generalize the implementation of neural network-based game playing engines by reducing the amount of domain specific (i.e. game rules) needed to implement the engine. And Leela Chess Zero showed how neural network based training could be implemented by distributing the task across a network and tapping on the resources of individuals connected to that network. Similar, in a way, how the available computer resources of many individuals were tapped to support SETI.
But I am trying to put things in perspective and correct some of the claims made by the more enthusiastic and apparently ignorant posters out there. First, there is <nothing> original in the algorithms used in AlphaZero; not the use of neural networks for chess playing, the use of reinforcement training of the neural network, or use of MCTS. All of these algorithms have been applied to chess playing before. I'm sure that the AlphaZero developers implemented many enhancements and improvements in these algorithms. But original, no.
What I do think that AlphaZero accomplished is the best <integration> of these algorithms into a chess playing <system> (hardware + software), and as someone who has been responsible for system integration on many projects I know and appreciate how hard and unpredictable this can be. That and the pioneering work of efficiently using TPUs and their massive computational performance advantage to implement the best chess playing <system>.
|Apr-15-19|| ||AylerKupp: <<MrMelad> You use those arguments to "warn" people from giving too much credit to AlphaZero as if the competition between stockfish and AlphaZero was between two similar algorithms that one simply had a huge computational advantage.>|
Well, I am trying to make people aware that the results of the AlphaZero and Stockfish matches are inconclusive at best <IF> what you are trying to find out what's the best approach and algorithms to implement the best chess playing engines. Whether the competition was with similar or dissimilar algorithms is besides the point, as long as the two engines are running on hardware with similar computational performance capability, regardless of hardware architectures. If that constitutes a "warning", then so be it.
Let me try a different approach to try to convince you of that. Suppose there a 100-game match was held between AlphaZero and Leela Chess Zero, both of which have similar (though not identical) algorithms and architectures and, of course, likely different implementations of those algorithms. If AlphaZero was restricted to use only one 1st generation TPU (performance estimated at ~30 TFlops) and Leela Chess Zero used a GPU server configuration with two nVIDEA RTX 2080i GPUs, (performance estimated at ~13.7 TFlops each, with an aggregate performance estimated at ~27.4 TFlops) then I would say that the performance capability of their hardware was similar. If results of the match were a near tie (like the previous TCEC's Leela Chess Zero vs. Stockfish Superfinal, even though Leela Chess Zero had a substantial computing capability over Stockfish), then I would conclude that the performance of the algorithms in AlphaZero and Leela Chess Zero was also approximately equal. I think that you would probably agree.
Now conduct another 100-match except allow AlphaZero to use four 3rd generation TPUs, each with a performance estimated at ~ 360 TFlops for an aggregate performance capability of ~1,440 TFlops and a performance computational advantage of ~ 52.5X over Leela Chess Zero. If the first match with hardware of comparable performance capability ended in a near-tie, do you have any doubts as to which engine would win the second match? And if the winner was AlphaZero by a substantial margin (of which I have no doubt), would you then conclude that the AlphaZero <algorithms> were substantially better than Leela Chess Zero's <algorithms>? I hope not. And, if you were to agree that the results of this second match were inconclusive because of AlphaZero's substantial computational capability, would you also have agreed if the first match with two approximately equal hardware in terms of computational performance capability had not taken place?
So yes, I "warn" people against giving too much credit to AlphaZero as a result of its matches against Stockfish when AlphaZero enjoyed a substantial computational performance advantage. Particularly since both DeepMind's data and Leela Chess Zero's experience with a shorter time/move (AlphaZero) and without GPU support (Leela Chess Zero) show that Stockfish, as well as many other classic engines, would defeat them both convincingly if their computational capabilities were similar.
|Apr-15-19|| ||AylerKupp: <<MrMelad> <I don't think your intentions are malicious though, I just don't think you understand how AlphaZero works, i.e., how reinforcement learning or deep learning works.>|
My intentions are certainly not malicious, at least not intentionally. I present my opinions and provide data or links to data to support them. What else can I do? If others disagree with my opinions even though they agree on the data presented, or if they choose to ignore the data, there's nothing I can do about that.
As far as not understanding how Alpha Zero, reinforcement learning, or deep learning works, I might surprise you. I have read every paper on Alpha Zero, Leela Chess Zero, neural networks, reinforcement learning, and deep learning that I have been able to find and read, and I have bought two books on neural network design and deep learning that I am now studying. An expert on those subjects? Clearly not, and I have a long way to go to even be considered "knowledgeable". But understanding? I think that I have a high-level understanding, enough I think to filter bs and wishful thinking from facts.
<<MrMelad> <I know sarcasm doesn't always translate well on the internet but I sometimes forget. My apologies for using it, it's not that funny anyways.>
Well, I have the same problem and I try to avoid it but, as you know, it's easy to backslide. And quips that somehow seem funny at the time that I write and post them typically don't seem so funny after a time and after others read them. My post was not intended as a criticism of using sarcasm but just a statement of fact that, unless the use of sarcasm if very, very obvious, it's not an effective way to try to get a point across.
<<MrMelad> Here is the part where he says "You can't really compare CPU cores to GPU cores apples to apples">
What he actually said starting at ~ 00:07:00 was that CPUs and GPUs can't be compared because "they are <qualitatively different>" and the much larger number of available cores in the GPUs means that they can effectively perform a larger number of more limited operations in parallel (no surprise here!). So <CPU cores> cannot be compared to <GPU cores> <because of the kind of things that they can each do most effectively>. That's where the "apples to apples" comment was addressing, not in the context that their computational capabilities can't be compared.
|Apr-17-19|| ||MrMelad: <AylerKupp> thanks for you comments. I responded in the AlphaZero page.|
|May-16-19|| ||diceman: <AylerKupp:
7. Repeat the process by increasing the depth of the subtree of the move being examined by one ply for those moves in the search tree (again, probably a small number, but I don't know the range of that number) that have the highest expected scoring percentage. Again, the engine's time management function of the chess engine determines when it's time to make a move.>
If given enough time, will all moves be looked at? (at whatever the listed ply depth is)
|May-20-19|| ||LoveThatJoker: <AylerKupp> Thanks for the engine analysis on 37. Qh8+. I too had gone with this continuation. LTJ|
|May-20-19|| ||LoveThatJoker: PS. In regards to yesterday's Gazza puzzle.|
|May-20-19|| ||Sally Simpson: ***
Hi AylerKupp (finally spelling your name correct instead of AlyerKupp)
You will be interested in this:
it's paper on ICAT and chess computers.
|May-21-19|| ||AylerKupp: <Sally Simpson> Thanks for the article on iCAT. At first glance I thought that the result should be obvious that chess players would enjoy a game against a physical opponent more than against a virtual opponent but even so it's good to have some confirmation. As you know I am a wine aficionado and I read that some enologists subjected Cabernet Sauvignon grapes to DNA testing to try to find out the grape's origin. After some analysis, at presumably a non-trivial expense, they determined that the Cabernet Sauvignon grape was the result of a cross between the Cabernet Franc grape and the Sauvignon Blanc grape. Then someone pointed out that, given the name Cabernet Sauvignon, shouldn't the answer have been obvious? Particularly since Cabernet Sauvignon, Cabernet Franc, and Sauvignon Blanc are all grown in the Bordeaux region of France.|
But I do wonder if the test was too simplistic. I don't know whether the effect of the novelty factor of playing against a physical opponent was properly considered. The article didn't say (I don't think) the number of games that each participant played against the iCat. Could it be that, particularly with the 8 to 12 year old participants, the players enjoyed the game more when faced with the novelty of playing against a physical iCat rather than a virtual one? Would the results have been the same if the same group of players had played a greater number of games against each type of opponent so that the novelty factor would have worn off?
And I don't see why the participants were restricted to one kind of scenario (physical or virtual). It would seem to me that if they had a relatively large number of positions and if these positions were chosen at random, then there would have been minimum chances of duplication. Or, if by chance the same position was selected, a different position would have been substituted for it. And if the participants played both types of opponent (physical and virtual) and the order in which they played each opponent was randomly selected, then a more direct preference comparison would have been achieved. Oh well, just some thoughts.
|Sep-13-19|| ||AylerKupp: <My Experience with Dress Codes>|
On my last job before my retirement I was the manager of the software department for a company. The company did have a dress code but it was never enforced or even mentioned and, software developers being what they are, my subordinates pretty much dressed as they pleased, and I never talked to them about it because, frankly, I didn't know what the company's dress code was. I did mention to them, in case they didn't think of it on their own, that if they were giving a presentation in front of our customers, they should dress appropriately, business casual as a minimum.
I personally wore casual attire except when giving presentations to our customers when I always wore a business suits. I never wore jeans except on weekends, and no shorts or sandals or flip flops.
Then one day everyone in the company received an email that the company's dress code will henceforth be enforced. It prohibited everyone from wearing shorts, jeans (even nice ones), and sandals and for the women specifically it prohibited wearing Capri pants, spaghetti straps, and outfits with bare midriffs.
Nobody knew why this email came out of the blue and one of my employees objected particularly strenuously. She said that she was a single mother, her wardrobe consisted only of jeans, and that she could not afford to get a completely new wardrobe. She finished by saying "I'm not giving up my jeans!"
My response was along the lines of "I agree with you. I'm not giving up my jeans, my Capri pants, or my spaghetti straps but by popular request I have agreed to give up my bare midriff outfits."
I of course talked to the powers-that-be to find out what triggered the email. I was told that there were some foreign potential customers visiting the company from a country where they could be offended by our employee's casual dress (and in the case of software developers <very> casual dress) and they didn't want that to happen.
I asked why this wasn't indicated in the email since it did not seem like an unreasonable request for these customer's visits and any other customer's visits from countries that might be offended by our overly casual attire, and that if notified of such visits no one would object to more relatively "formal" attire when these customers were touring our facility, and then revert to their usual attire when there were no customers on site. I was told that this would be very hard to do.
Which was absolute nonsense since <every> visitor had to indicate when they would be visiting our facility and submit their security clearances ahead of time. I always received a notice of such visits and asked my subordinates that they should straighten up their offices and the walk spaces somewhat (software developers tend to be rather messy) prior to the customers' arrival. Which told me that the powers-that-be were not that serious about the "problem" and that the issue would quickly die out. And, sure enough, it did.
|Sep-13-19|| ||AylerKupp: <My Experience with Company Rules and Regulations>|
Since I'm on a roll and this is my forum I can address any subject at all (within reason) so I will. This was the incident that taught me that all rules have a way around them and, rather than try to fight an unreasonable (at least to me) rule head-on, it's easier to try to find the loopholes in the rules (there are always some) and go around them.
Many years ago before the existence of personal computers we used minicomputers which could be shared by multiple users. At another company where I was the head of software development for my department we had a centralized minicomputer in the second floor which served the needs of the software developers. Three of my subordinates were sharing an office on the first floor and they had to go upstairs to use the computer. They asked me if I could arrange to have a dumb terminal (the only ones available at the time) installed in their office since that would save them the time to up and down the stairs, increase productivity, blah, blah, blah.
That seemed like a reasonable request to me so I went to talk to the facilities manager. He told me that it was against company policy to do that because in those days they were required to install a hard conduit for the cables leading from the minicomputer to individual offices and, if my subordinates were to move, they would have wasted the money.
I was about to object when I saw the smile on the face of the facilities manager who said "However, if you install two terminals instead of just one, that would make it a terminal room that's OK as far as company policy goes and I will approve the request."
So my subordinates got two terminals in their office instead of one and were even happier. Perhaps FIDE could learn something from my experience.
< Earlier Kibitzing · PAGE 56 OF 56 ·
Daily puzzles, news, and more!