Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

cnn-vgg16.ipynb got abnormal results

Abierto
#76 2 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
jupyter-notebook

Línea de trabajo

Open pytorch_ipynb/cnn/cnn-vgg16.ipynb and compare its run on Google Colab with the linked Colab notebook and supplied training log. Reproduce the unchanged notebook, apart from the CUDA device ordinal, and verify that the resolved run shows decreasing cost and increasing accuracy rather than remaining near 2.303 and 10%.

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

Descripción

Hello Sebastian,
First of all, I would like to express my gratitude for your great work and knowledge sharing!

I just ran the cnn-vgg16.ipynb on Google Colab without any modification (except the CUDA device ordinal). The result I got was totally abnormal, and was different from yours provided. The cost didn't decrease and the accuracy didn't increase at all. Could you please have a look at it?

Thank you so much, again!

Below is my train log. And the notebook on Google Colab is here.

Epoch: 001/010 | Batch 0000/0391 | Cost: 2.3682
Epoch: 001/010 | Batch 0050/0391 | Cost: 2.2857
Epoch: 001/010 | Batch 0100/0391 | Cost: 2.3016
Epoch: 001/010 | Batch 0150/0391 | Cost: 2.3024
Epoch: 001/010 | Batch 0200/0391 | Cost: 2.3069
Epoch: 001/010 | Batch 0250/0391 | Cost: 2.3022
Epoch: 001/010 | Batch 0300/0391 | Cost: 2.3035
Epoch: 001/010 | Batch 0350/0391 | Cost: 2.3035
Epoch: 001/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 0.63 min
Epoch: 002/010 | Batch 0000/0391 | Cost: 2.3032
Epoch: 002/010 | Batch 0050/0391 | Cost: 2.3020
Epoch: 002/010 | Batch 0100/0391 | Cost: 2.3012
Epoch: 002/010 | Batch 0150/0391 | Cost: 2.3041
Epoch: 002/010 | Batch 0200/0391 | Cost: 2.3035
Epoch: 002/010 | Batch 0250/0391 | Cost: 2.3009
Epoch: 002/010 | Batch 0300/0391 | Cost: 2.3026
Epoch: 002/010 | Batch 0350/0391 | Cost: 2.3005
Epoch: 002/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 1.25 min
Epoch: 003/010 | Batch 0000/0391 | Cost: 2.3008
Epoch: 003/010 | Batch 0050/0391 | Cost: 2.3013
Epoch: 003/010 | Batch 0100/0391 | Cost: 2.3013
Epoch: 003/010 | Batch 0150/0391 | Cost: 2.3018
Epoch: 003/010 | Batch 0200/0391 | Cost: 2.3027
Epoch: 003/010 | Batch 0250/0391 | Cost: 2.3029
Epoch: 003/010 | Batch 0300/0391 | Cost: 2.3028
Epoch: 003/010 | Batch 0350/0391 | Cost: 2.3036
Epoch: 003/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 1.88 min
Epoch: 004/010 | Batch 0000/0391 | Cost: 2.3025
Epoch: 004/010 | Batch 0050/0391 | Cost: 2.3021
Epoch: 004/010 | Batch 0100/0391 | Cost: 2.3015
Epoch: 004/010 | Batch 0150/0391 | Cost: 2.3024
Epoch: 004/010 | Batch 0200/0391 | Cost: 2.3027
Epoch: 004/010 | Batch 0250/0391 | Cost: 2.3014
Epoch: 004/010 | Batch 0300/0391 | Cost: 2.3030
Epoch: 004/010 | Batch 0350/0391 | Cost: 2.3026
Epoch: 004/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 2.50 min
Epoch: 005/010 | Batch 0000/0391 | Cost: 2.3014
Epoch: 005/010 | Batch 0050/0391 | Cost: 2.3027
Epoch: 005/010 | Batch 0100/0391 | Cost: 2.3023
Epoch: 005/010 | Batch 0150/0391 | Cost: 2.3017
Epoch: 005/010 | Batch 0200/0391 | Cost: 2.3007
Epoch: 005/010 | Batch 0250/0391 | Cost: 2.3018
Epoch: 005/010 | Batch 0300/0391 | Cost: 2.3029
Epoch: 005/010 | Batch 0350/0391 | Cost: 2.3028
Epoch: 005/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 3.13 min
Epoch: 006/010 | Batch 0000/0391 | Cost: 2.3018
Epoch: 006/010 | Batch 0050/0391 | Cost: 2.3009
Epoch: 006/010 | Batch 0100/0391 | Cost: 2.3020
Epoch: 006/010 | Batch 0150/0391 | Cost: 2.3030
Epoch: 006/010 | Batch 0200/0391 | Cost: 2.3025
Epoch: 006/010 | Batch 0250/0391 | Cost: 2.3005
Epoch: 006/010 | Batch 0300/0391 | Cost: 2.3033
Epoch: 006/010 | Batch 0350/0391 | Cost: 2.3028
Epoch: 006/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 3.75 min
Epoch: 007/010 | Batch 0000/0391 | Cost: 2.3024
Epoch: 007/010 | Batch 0050/0391 | Cost: 2.3027
Epoch: 007/010 | Batch 0100/0391 | Cost: 2.3032
Epoch: 007/010 | Batch 0150/0391 | Cost: 2.3044
Epoch: 007/010 | Batch 0200/0391 | Cost: 2.3026
Epoch: 007/010 | Batch 0250/0391 | Cost: 2.3030
Epoch: 007/010 | Batch 0300/0391 | Cost: 2.3026
Epoch: 007/010 | Batch 0350/0391 | Cost: 2.3024
Epoch: 007/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 4.37 min
Epoch: 008/010 | Batch 0000/0391 | Cost: 2.3025
Epoch: 008/010 | Batch 0050/0391 | Cost: 2.3033
Epoch: 008/010 | Batch 0100/0391 | Cost: 2.3034
Epoch: 008/010 | Batch 0150/0391 | Cost: 2.3021
Epoch: 008/010 | Batch 0200/0391 | Cost: 2.3034
Epoch: 008/010 | Batch 0250/0391 | Cost: 2.3034
Epoch: 008/010 | Batch 0300/0391 | Cost: 2.3027
Epoch: 008/010 | Batch 0350/0391 | Cost: 2.3030
Epoch: 008/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 5.00 min
Epoch: 009/010 | Batch 0000/0391 | Cost: 2.3031
Epoch: 009/010 | Batch 0050/0391 | Cost: 2.3029
Epoch: 009/010 | Batch 0100/0391 | Cost: 2.3033
Epoch: 009/010 | Batch 0150/0391 | Cost: 2.3035
Epoch: 009/010 | Batch 0200/0391 | Cost: 2.3019
Epoch: 009/010 | Batch 0250/0391 | Cost: 2.3027
Epoch: 009/010 | Batch 0300/0391 | Cost: 2.3037
Epoch: 009/010 | Batch 0350/0391 | Cost: 2.3027
Epoch: 009/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 5.62 min
Epoch: 010/010 | Batch 0000/0391 | Cost: 2.3030
Epoch: 010/010 | Batch 0050/0391 | Cost: 2.3023
Epoch: 010/010 | Batch 0100/0391 | Cost: 2.3031
Epoch: 010/010 | Batch 0150/0391 | Cost: 2.3023
Epoch: 010/010 | Batch 0200/0391 | Cost: 2.3029
Epoch: 010/010 | Batch 0250/0391 | Cost: 2.3022
Epoch: 010/010 | Batch 0300/0391 | Cost: 2.3023
Epoch: 010/010 | Batch 0350/0391 | Cost: 2.3029
Epoch: 010/010 | Train: 10.000% |  Loss: 2.303
Time elapsed: 6.25 min
Total Training Time: 6.25 min
Lenguaje dominante
Jupyter Notebook
Estrellas
17.6k
Forks
4.1k
Métricas de merge de PR
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 rasbt/deeplearning-models

Todos los issues de rasbt/deeplearning-models

Issues similares

Más issues de Machine Learning

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.