与「MT1」相关的搜索结果

A new project called OmniDrive enables some Blu-ray drives to rip older console games directly to a PC. With custom firmware installed, certain compatible drives can now read discs from systems like the Nintendo GameCube, Wii, original Xbox, and Xbox 360 The project targets Blu-ray drives using MediaTek MT1959 chipsets. Once modified, the drives work with tools like Redumper and MPF to create full backups of physical game discs. Supported systems currently include: >Nintendo GameCube >Nintendo Wii >original Xbox >Xbox 360. There is also limited support for newer systems such as the PlayStation 3, PS4, PS5, Wii U, and Xbox Series X, although those discs are still heavily encrypted. Older consoles and disc drives are becoming harder to find and repair, while physical discs wear out over time. This offers collectors and preservation groups an easier way to archive games before the hardware disappears. There are still important limitations. OmniDrive only works with a small number of compatible Blu-ray drives, and flashing unofficial firmware carries some risk.

In today's episode of programming horror... In the Python docs of random.seed() def, we're told "If a is an int, it is used directly." [1] But if you seed with 3 or -3, you actually get the exact same rng object, producing the same streams. (TIL). In nanochat I was using the sign as a (what I thought was) clever way to get different rng sequences for train/test splits. Hence gnarly bug because now train=test. I found the CPython code responsible in cpython/Modules/_randommodule.c [2], where on line 321 we see in a comment: "This algorithm relies on the number being unsigned. So: if the arg is a PyLong, use its absolute value." followed by n = PyNumber_Absolute(arg); which explicitly calls abs() on your seed to make it positive, discarding the sign bit. But this comment is actually wrong/misleading too. Under the hood, Python calls the Mersenne Twister MT19937 algorithm, which in the general case has 19937 (non-zero) bits state. Python takes your int (or other objects) and "spreads out" that information across these bits. In principle, the sign bit could have been used to augment the state bits. There is nothing about the algorithm that "relies on the number being unsigned". A decision was made to not incorporate the sign bit (which imo was a mistake). One trivial example could have been to map n -> 2*abs(n) + int(n < 0). Finally this leads us to the contract of Python's random, which is also not fully spelled out in the docs. The contract that is mentioned is that: same seed => same sequence. But no guarantee is made that different seeds produce different sequences. So in principle, Python makes no promises that e.g. seed(5) and seed(6) are different rng streams. (Though this quite commonly implicitly assumed in many applications.) Indeed, we see that seed(5) and seed(-5) are identical streams. And you should probably not use them to separate your train/test behaviors in machine learning. One of the more amusing programming horror footguns I've encountered recently. We'll see you in the next episode. [1] [2]

『#ANISONIC# SP!!』モモーイ NewGame+ CDリリイベ大感謝祭！出番終わりました✨楽しかった〜🥰改めて桃井さん、リリースおめでとうございます😭💿💕 素敵な機会に立ち会えて幸せです...！！ 一緒に盛りあがってくれた皆さんも本当にありがとうございました🫶

シーちゃまのおともだちのライブ映像εïзが公開されたヨ♪♪ ファントムシータ【1ST WORLD TOUR "Moth to a flame"】おともだち @YouTubeより