11:34 Oct 27, 2017 |
Polish to English translations [PRO] Tech/Engineering - IT (Information Technology) | |||||
---|---|---|---|---|---|
|
| ||||
| Selected response from: Maciek Drobka Poland Local time: 09:19 | ||||
Grading comment
|
Summary of answers provided | ||||
---|---|---|---|---|
4 +2 | dry |
|
Summary of reference entries provided | |||
---|---|---|---|
Dry Running code and Debugging |
|
dry Explanation: A we frazie: dry run (testing) https://en.wikipedia.org/wiki/Dry_run_(testing) |
| |||||||||
Grading comment
| ||||||||||
|
3 hrs |
Reference: Dry Running code and Debugging Reference information: 4.4 Dry Running code and Debugging Sometimes when we run codes with errors, the error messages are unclear. To get a full sense of how programs are actually working in MATLAB, we need to be able to read a program, and compute the output on paper. Doing this helps you understand the intricate workings of how MATLAB reads a program and also helps you detect and debug logical and numerical errors in the program. In this section we will inspect code and run it without actually running it in MATLAB. Finally, we will use this skill to find logic and numerical errors in a code and fix them. 4.4.1 Dry Running code Dry running a code means that instead of running the program using MATLAB, you run the program in your head. This exercise is usually aimed towards improving logical reasoning and gives a deeper understanding of the workings of MATLAB. https://www.coursehero.com/file/p5vcvcl/for-row-11lengthA1-f... |
| |
Login to enter a peer comment (or grade) |
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.