# Math-Model-and-Machine-Learning documents six directories and ships nine, with no licence > A Chinese-language collection of competition papers, textbooks and lecture notes for mathematical modelling and machine learning, kept by one student as a public record of self-study. It asks for stars, it leaves both of its to-do items unticked, and its contents are declared as gathered from the internet. **QInzhengk/Math-Model-and-Machine-Learning** — Notes and resources on mathematical modeling, machine learning, deep learning and large language models. Continuously updated. - Repository: https://github.com/QInzhengk/Math-Model-and-Machine-Learning - Website: https://zread.ai/QInzhengk/Math-Model-and-Machine-Learning - Stars: 654 · Forks: 117 - Language: Jupyter Notebook - License: not declared - Published: 2026-09-10 · Updated: 2026-09-10 · Language: en - Canonical page: https://hysenlabs.com/projects/qinzhengk-math-model-and-machine-learning ## The documented tree has six directories and the root has nine entries The readme contains a directory listing, and it is worth checking against reality. What it shows is a readme and six directories: one for artificial intelligence material, one for mathematics, one for mathematical modelling, one for general computer studies, one for images, and the modelling directory again with five children for competition problems and papers, books, templates, algorithms and courseware. The actual repository root has nine entries, and three of them are not in that listing. They are markdown essays with long Chinese titles sitting beside the readme: one on the idea that everyone now has to work alongside artificial intelligence rather than just programming, one a panoramic guide to mathematical modelling and AI resources, and one a timeline of more than fifteen competitions with a grading of how much each is worth and what to avoid. So the three most substantial standalone documents in the repository are invisible in its own map of itself. A reader arriving from the readme would not know they exist. Two further gaps sit inside the listing. The mathematics directory is described in the tree as holding competition problems and answers from a university mathematics competition and from an Alibaba-run competition, but the readme's index has no mathematics section at all. And four of the five modelling sub-directories, for books, templates, algorithms and courseware, are listed as bare headings with no links under them at all. Eight directories documented, four of them empty in the index. ## The primary language is recorded as a notebook, and there are no notebooks The repository's detected primary language is a notebook format. The root contains no notebooks. What it contains is markdown files and directories whose names are in Chinese. A detector picking a notebook as the dominant language for a tree of markdown essays and images is picking up something that is not visible in the listing, or it is picking up notebooks that exist deep inside a subdirectory the readme describes only by name. Either way the number does not describe what a reader sees. For a repository whose whole purpose is to be browsed, the language field is one of the few things a search index or a package listing will show you, and here it points at a format that is not what you get. The same applies to the one English-facing field there is. The repository's recorded homepage is not the author's site; it is a third-party service that reads and summarises GitHub repositories. A reader arriving from that link gets an interpretation of the repository rather than the repository. The author's own blog appears further down the readme instead, and so do two separate side projects: one for scheduling pushes to a messaging account and one for scheduling messages from a chat bot in a different platform. Three other repositories share this readme as their front page. The blog link is worth one more look. It points at two posts, and both are numbered with the same ordinal in their titles. Two posts, both called the first one. ## Sixteen lines in the index, fifteen competitions, and two lines for the same contest The competition index is the most carefully built part of this repository, and it has two countable errors. It lists sixteen top-level entries. One of them, a challenge cup for a southern city, appears twice, once as the sixth entry and again as the fifteenth. So there are fifteen distinct competitions against a claim elsewhere of more than fifteen, which lands exactly on the boundary. The separate essay in the root is named as a complete list of fifteen or more competitions with a timeline and a grading of value, and the index delivers fifteen. The number in the filename is right and the index is one line too long. The second issue is a classification one. The American undergraduate competition and its Asia-Pacific counterpart are listed as two separate entries, and they are the same competition run in two regional tracks. Counting them the way a reader would, by what they would have to prepare for, that is fourteen distinct competitions plus one split into two tracks. Underneath the top level the structure is genuinely good. The national undergraduate competition expands into six subdirectories covering the archive of problems by year range, the official judging notes, a walkthrough of the problems, and excellent undergraduate papers. The graduate competition adds a provincial variant and its own papers. The American competition adds its own year range. A cup competition adds a collection of past problems and papers plus a separate big-data challenge. That is the part of this repository to bookmark. ## Everything over twenty-five megabytes is missing, and the replacement is a messaging channel There is one line in the project description that changes what this repository is. It says that all files larger than twenty-five megabytes are not uploaded. Nothing else is offered in their place except a messaging account. For a collection of textbooks, datasets and scanned papers, twenty-five megabytes is a low ceiling. It is below the size of most scanned books and above the size of most lecture notes, so the boundary falls exactly where you would expect: notes stay, books do not. The consequence is that the repository's largest and most expensive-to-replace content is not on GitHub, not in any release, and not in any archive. The readme's instruction for getting it is to go through the author's messaging account. That matters for two reasons. A repository that cannot be cloned completely cannot be mirrored, and a fork cannot reproduce it. And the answer to a missing file is a chat request rather than an issue, which means the gap is invisible to anyone auditing the tree. The other contact routes are the same shape: a group chat number printed in the readme, a group chat channel, and a question-and-answer circle on a different site. Four channels, none of them an issue tracker for missing content. ## Both to-do items are unticked, and one of them is the artificial intelligence directory There is a to-do section near the top, and it has two boxes. Neither is ticked. One is for mathematical modelling competition problems and excellent papers. The other is for artificial intelligence. The second box is the interesting one, because the repository is named for both subjects and the root contains a directory for artificial intelligence material described as covering deep learning, machine learning and large models. So the section the project is co-named after is marked as not done, in the same readme that opens by saying the project is continuously being updated. The first box is marked not done while the readme below it contains sixteen lines of competition index. The index exists and is linked; the checkbox was never updated. This is a small thing and it is the clearest signal in the repository about how it is maintained. There is no contribution guide describing a structure to follow, no naming convention, no statement about what belongs in which directory, and no review process. The readme's contribution section is the standard fork-and-branch-and-pull-request sequence with the default example commit message, and the acknowledgement section ends by saying that this part will be completed once the updates are done. For a repository that asks for pull requests, that is the whole of the guidance. ## No licence, and a promise to delete on an infringement claim The repository declares no licence, and there is no licence file in the tree. Without one, the default applies: no permission to copy, redistribute or adapt. For a personal notes repository that is defensible. For a collection of textbooks, lecture notes, competition papers and templates assembled from elsewhere, it is a gap that only the reader can see and only the author can close. The acknowledgement section makes the situation explicit. It ends with a sentence saying that the section will be completed once the updates are finished, that questions can go through the issue tracker, and that all of it is material gathered from the internet and will be deleted if there is an infringement claim. That is a takedown promise, which is a reasonable thing for a collector to say, and it is also an admission that the material's provenance is not the author's own. Combined with the absent licence, the position is: no rights granted, and a stated willingness to remove things on request. Two smaller details sit in the same section. The contributors table has two rows. One is the author. The other is a link to a profile on a question-and-answer site, labelled as thanks for support rather than as a code contribution. And one of the three acknowledged references is a course link carrying a tracking query string with a session identifier in it, baked into the readme permanently. The remaining two acknowledgements are other people's open repositories, which is the right way to credit a source you built on. ## Every line of the directory listing uses the closing glyph The directory listing in the readme is a fenced block of plain text, and it has a rendering bug that makes it harder to read than it should be. Every single line uses the glyph that means last child, including the lines that are not last children and including the one that is the only child. The readme file, which is the first entry and the only file, is drawn with the same connector as everything below it. In a correctly drawn tree you would expect the listing to branch, with children indented under parents. Here it is a flat column of lines that all look like the end of a branch, so the structure has to be inferred from the text annotations on the right rather than read from the geometry. Those annotations are the useful part, and they are informative. Each line says what the directory holds. The modelling directory's children are described as competition problems and excellent papers, books, templates, algorithms and courseware. The general computer studies directory is described as covering Java, office software and mini-programs, which is a considerable distance from mathematical modelling and is the one place the collection's scope visibly widens. The images directory is annotated more precisely than the rest: it holds a messaging-account QR code and a group-chat QR code, both for the same topic. That last annotation is the one that matters most for anyone auditing this repository, because it tells you what the images folder is for. ## Conclusion Treat this repository as a link index rather than as a course. The competition directory is genuinely organised and is the part worth bookmarking, and the contest timeline essay is the clearest single document in it. Two things to know before you rely on anything here. There is no licence, and the readme states the material was collected from the internet and will be removed on an infringement claim, which makes reuse a decision you have to make yourself. And everything over twenty-five megabytes is absent by design, so the largest files are only reachable through the author's messaging channel, not through the repository. ## FAQ ### What is in the Math-Model-and-Machine-Learning repository? Chinese-language notes and materials from self-study, organised into directories for mathematical modelling, mathematics, artificial intelligence, general computer studies and images. The modelling competition index is the most developed part, covering fifteen distinct competitions with subdirectories for past problems and excellent papers. ### Does the repository include the books and datasets it links to? No. The readme states that all files larger than twenty-five megabytes are not uploaded, and directs readers to the author's messaging account instead. A repository that cannot be cloned in full also cannot be mirrored, and a fork cannot reproduce it. ### What licence is Math-Model-and-Machine-Learning released under? None declared. The repository records no licence and there is no licence file in the tree, so the default applies. The readme's acknowledgement section says the material was gathered from the internet and will be removed on an infringement claim. ### How do I contribute to Math-Model-and-Machine-Learning? The readme gives the standard sequence: fork the repository, create a branch, commit with a message, push and open a pull request. There is no guide describing where a file belongs, no naming convention and no statement about the review process. ### How many maths modelling competitions does the index cover? Sixteen index lines, but one challenge cup is listed twice, giving fifteen distinct competitions, which matches the fifteen-or-more claim in a companion essay. The American competition and its Asia-Pacific counterpart are counted as two entries although they are the same contest in two regional tracks. ## Sources - [Issues](https://github.com/QInzhengk/Math-Model-and-Machine-Learning/issues) - [Project website](https://zread.ai/QInzhengk/Math-Model-and-Machine-Learning) - [QInzhengk/Math-Model-and-Machine-Learning on GitHub](https://github.com/QInzhengk/Math-Model-and-Machine-Learning) - [README](https://github.com/QInzhengk/Math-Model-and-Machine-Learning/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/qinzhengk-math-model-and-machine-learning