結果:


Designing the New Figure Toolstrip Around User Experience
Guest Writer: Travis Roderick Travis joined MathWorks in 2013, bringing experience from previous roles in software development across the healthcare, finance, and storage network industries. He earned a BA in Computer Science in 2001, followed by a master’s degree where he explored the intersection of technology and creativity—using probabilistic genetic algorithms to generate music for his thesis. Although he enjoys the
- It's the right thing to do scientifically. A computational paper is essentially just an advertisement of what you've done. The code contains vital details about how you actually did it. A computational paper is incomplete without the code.
- If you only describe your algorithm in a paper, I have to implement it before I can apply your research to my problem. If you share the code, I can get started much more quickly using your research. This means I publish faster and since I am a good scientist, this means you get cited faster.
- Other scientists start off as users of your code. This leads to citations. Over time, some of them start deeply using and modifying your code, this leads to collaborators.
- Once you decide to share code via something like GitHub, you quickly start adopting good software engineering practices without initially realizing it. This improves the quality of your research since adopting good software practices makes it more likely that your software will give the right answers.

Introducing the Tabbed Figure Container
Guest Writer: Brian Knolhoff Brian is a software engineer on the Figure Infrastructure and Services team at MathWorks. After first encountering MATLAB while calibrating radar systems, he now enjoys building and modernizing the tools that support engineers and scientists in their daily work. Outside of the office, Brian enjoys playing guitar, hockey, and board games, and maintains a collection of vintage





- Almost all resources rely solely on MathWorks servers. Once a failure (or a ransomware attack) occurs, everything is paralyzed, and there isn’t even a temporary backup server? For a big company like MathWorks to have no contingency plan at all is eye-opening. This tells us that we should have our own temporary emergency servers!
- The impact should be minimized. For example, many users need to connect to the official servers to download various support packages, such as the “Deep Learning Toolbox Converter for ONNX Model Format.” Could these be backed up and mirrored to the “releases” section of a GitHub repository, so users in need can download them.
- A large proportion of users who have already installed MATLAB cannot access the online help documentation. Since R2023a, installing the help documentation locally has become optional. This only increases the burden on the servers? Moreover, the official website only hosts documentation for the past five years. That means after 2028, if I haven’t installed the local offline documentation, I won’t be able to access the online documentation for R2023a anymore?