# NUEDC_Topic: three decades of Chinese electronic design competition problems, archived as files > NUEDC_Topic collects the past problems of the National Undergraduate Electronic Design Contest from 1994 through 2026 and stores them as PDFs, Word documents and spreadsheets in a directory per year. It is an archive rather than software, and its value is that the same problems can be searched, sorted by category and reused as practice problems. **CCBP/NUEDC_Topic** — 收集并整理了全国大学生电子设计竞赛从1994年至2025年的历年赛题，如有遗漏欢迎补充！ - Repository: https://github.com/CCBP/NUEDC_Topic - Stars: 1,030 · Forks: 88 - Language: Unknown - License: not declared - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/ccbp-nuedc-topic ## One directory per contest year, holding the original documents NUEDC_Topic collects and organises the past problems of the National Undergraduate Electronic Design Contest, described in the repository description as running from 1994 to 2025, with the heading and the tree covering 1994 through 2026. The structure is the archive. Each year is a top level directory named for the year, and inside it the problems are files with their letter prefix and the topic title in the filename. The 1995 directory holds four problems, A through D. The 2003 directory holds six, from a voltage controlled LC oscillator through to a liquid drip speed monitoring device. The 2013 directory holds ten, including a quadrotor autonomous aircraft, an inverted pendulum, a radio frequency broadband amplifier and a hand writing drawing tablet. The file types vary by year, and that is itself a signal about the archive's provenance rather than a design decision. The 1994, 1995, 1997, 1999 and 2001 entries are PDF. The 2012 entries are.docx. The 2014 entries are.doc, and the 2018 entries are mostly.docx with one.doc. The 2017, 2019, 2021, 2024 and 2025 directories each carry a spreadsheet alongside the problems, and some years carry a device list or component list file. The 2019 directory even includes JPG images for the field layout and hovering concentric circles of the line following robot, and the 2024 directory includes a ZIP attachment for the shelving inventory drone system. So this is not a normalised dataset. It is a set of files as they were obtained, with the awkward bits left in: a 1994 to 2007 directory holding one combined PDF of all problems from that span, and a 2022 directory split into subdirectories for the July and October contests because that year had two rounds. ## The year list has gaps, and one consolidated archive The top level directory list is worth reading as data rather than as a file browser. The years present are 1994, 1995, 1997, 1999, 2001, 2003, 2005, 2007, 2009, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025 and 2026, alongside a 1994-2007 directory. Two things follow. The early years are held as a single combined PDF in the 1994-2007 directory, so the 1996, 1998 and other even years in that range are not individually broken out as their own directories even though the contest ran in those years. And the repository is explicit that it is incomplete, since the readme asks for contributions if anything is missing or wrong. From 2009 onwards the coverage is per year and per problem, with the contest appearing to run every two years in the earlier period and annually from 2009. The 2012 directory is a full set of eight Word documents, the 2017 set has thirteen entries plus a topic list spreadsheet and a notes file about the topic list, and 2025 has an eight problem set with a device list PDF and a question and answer statistics text file. The 2026 entry shows something else: a regional round. There is a subdirectory for an April contest held in Jilin with four problems, alongside the main set of eight problems for the year. So the archive follows the structure of the contest itself, which in 2026 included a separate regional event with its own papers. ## Classification.xlsx sorts the problems by what they are about At the root of the repository there are two spreadsheets and a classification table. Classification.xlsx is the category index, and the table in the readme shows its columns. The categories are instrument type, communication type, measurement and control type, power supply type, signal processing, control type, aircraft, and high frequency and communication type, with a notes column at the end. The other spreadsheet files are per-year topic lists: a topic list spreadsheet for 2017 and a national topic list for 2019, a 2021 topic list with separate sheets for the undergraduate and vocational tracks, and topic list spreadsheets for 2024 and 2025. Those per-year lists are the useful part for anyone who wants to search rather than browse. A spreadsheet with one row per problem can be sorted by category, by year, or by whatever column the archive maintainers chose, and the spreadsheets for 2021 exist specifically to separate the undergraduate competition from the vocational and technical college competition, which are distinct events with different difficulty. The category axis is also the most useful thing about the archive as a study resource. A student preparing for a power electronics problem can find every year the contest asked for a switching supply, a converter or an inverter, and read the original statement. The categories are drawn from electronics, so they map onto the way the contest itself is organised: instrumentation problems, communication problems, control problems, and the rest. One thing to note is that the archive holds the problem statements, not the solutions or the marking criteria. There is a device list in several years and a topic list spreadsheet in others, which tells you what equipment was available in the lab, but the repository is a statement archive rather than a solution archive. ## A CI workflow and a generated tree, rather than an application The repository has a .github directory with a single CI workflow file, CI.yml, and a .gitattributes file. There is also a tree.bak file at the root alongside the README, which suggests the directory tree in the readme is generated and the backup is kept as a fallback. The tree itself is marked with readme-tree markers in the readme, a convention used by tooling that regenerates the tree between comment markers. The count at the end of the block states 34 directories and 232 files, which is a useful sense of scale: this is a few hundred documents, not a large dataset, and it is small enough that a clone is cheap. The primary language of the repository is listed as unknown, which makes sense for an archive of binary documents. There is no application code, no schema and no API. The value is entirely in the files. The practical consequence for anyone using this is that there is nothing to install and nothing to run. You clone, or you browse the repository on GitHub, and you read. For a GitHub repository of PDFs and Word documents, the web interface is often more convenient than a local clone, particularly when you want to link a specific problem to a teammate. The licence situation is the one gap worth flagging. The licence field on the repository says unknown, and there is no LICENSE file among the top level entries. The readme does not state terms. For a personal study aid that is one thing. For a company that wants to build a course or a training programme on top of this collection, the absence of a stated licence is a real question, and it is a question the repository maintainer would need to answer rather than one you can resolve by reading the files. ## Where this archive does not help you Three limits are worth being explicit about, and none of them are defects in the project. The first is language. The problem statements are in Chinese, and the repository carries no English translations. There is no machine translation layer, and no bilingual index. For a reader working in English, this archive is usable as a picture of what the contest asks, and as a source to translate, but it is not a source you can hand to a student who cannot read Chinese and expect them to work from it directly. The second is the absence of solutions. An archive of problems is excellent for practising, because you build the thing yourself, and it is much less useful as a reference for how a particular problem was solved. There are no schematic solutions, no component selections and no sample builds here. The device lists give you what was on the bench, which is a hint, but not an answer. The third is coverage. The early years are consolidated, the even years are folded into a single combined PDF, and the readme itself asks for contributions. If your question is specifically about a particular year, the archive may not answer it, and the correct move is to contribute the missing documents, which is what the readme invites. The alternative to an archive like this, for someone who wants practice problems, is a set of curated problem collections or an active community site, which tend to have solved versions and English text. For someone who specifically wants the authentic statement documents from this competition, with the original diagrams and component lists, this repository is the source and there is no substitute. ## Conclusion NUEDC_Topic suits a student or instructor who wants real hardware design problems with the original statement documents, rather than invented exercises, and the directory per year makes it easy to browse a single contest. It does not suit a reader who needs translations, since the statements are in Chinese and the repository carries no English version, and it does not carry solutions, only the problem papers. Before relying on it, check the gap in the year list, since 1996 and 1998 are absent and 1994 to 2007 is partly covered by a single combined PDF, and note that the last push was on 2026-09-21 while the repository has no tagged releases and no stated licence. ## FAQ ### What does the NUEDC_Topic repository contain? It collects and organises the past problems of the National Undergraduate Electronic Design Contest, with a directory per year holding the original problem documents. The statements are PDFs, Word documents and spreadsheets, and the coverage runs from 1994 through 2026. ### What file formats are used for the contest problems? They vary by year: PDF for the 1994 through 2001 sets, .docx for 2012, .doc for 2014 and 2018, and PDFs for most later years. Several years also include a spreadsheet topic list, a device or component list file, and image attachments such as the 2019 JPG field layout files. ### How are the NUEDC_Topic problems categorised? A Classification.xlsx file at the repository root sorts them by category, with columns for instrument type, communication type, measurement and control type, power supply type, signal processing, control type, aircraft, and high frequency and communication type, plus a notes column. Per-year topic list spreadsheets are also included for 2017, 2019, 2021, 2024 and 2025. ### Does NUEDC_Topic include solutions to the problems? No. The repository holds problem statements, topic list spreadsheets and device list files, but the visible documentation does not include solutions, schematics or sample builds. ### Is the NUEDC_Topic collection complete? Not entirely. Years 1996 and 1998 are absent as separate directories, and 1994 to 2007 is partly covered by one combined PDF. The readme states the collection covers 1994 to 2026 and asks for contributions of anything missing or in error. ## Sources - [CCBP/NUEDC_Topic on GitHub](https://github.com/CCBP/NUEDC_Topic) - [Issues](https://github.com/CCBP/NUEDC_Topic/issues) - [README](https://github.com/CCBP/NUEDC_Topic/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/ccbp-nuedc-topic