[Exam Review] Serious Issues Observed in Submitted MATLAB Scripts

Abierto
  • ¿Algo no está bien?
#204 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
20/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Área
content

Línea de trabajo

The issue contains an exam review and an attached screenshot, but names no repository files, tests, or requested change. Start by checking the screenshot and the project’s existing course materials to determine whether this belongs there. Done is unclear until a specific change is identified.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

After reviewing the exams, I must address several issues that emerged very clearly during the marking process.

As Professor @MarcoRianiUNIPR already mentioned, some of the submitted solutions were absurd. I would go further: several were not only incorrect but also embarrassing from a basic programming‑practice perspective.

A few critical points:

Some students did not even load the dataset yet still produced “results” in their scripts. This is simply impossible. If the data is not loaded, MATLAB cannot generate any output. Such submissions indicate that the code was not written, tested, or understood by the student.

Basic file‑naming rules were ignored. Several MATLAB files were saved with spaces or dots in the filename. When you do this, MATLAB cannot run the script. This is fundamental knowledge expected from anyone attending this course.

Students who received zero marks did so because their entire code was clearly generated by large language models. The structure, the errors, and the lack of connection to the dataset make this extremely easy to detect.

Some scripts contained more than 200 lines of code written in 75 minutes. This is not realistic and further confirms the use of generative tools without understanding.

The attached screenshot is one such example of code produced by a large language model, including lines such as “I asked you what I should print here and you told me the numeric data names so here it is”, which no student would reasonably write during an exam.

This is a serious reminder: your future depends on the skills you build now. Please take exams

Image

seriously. Exams are designed to help you learn, not to be outsourced.

Lenguaje dominante
MATLAB
Estrellas
30
Forks
1
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de UniprJRC/DSwithMATLAB

Todos los issues de UniprJRC/DSwithMATLAB

Issues similares

Más issues de MATLAB

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.