Quiz collegato alla guida · Medio Livello

Riproducibilità in ML: semi e determinismo Quiz

Distinguere i seed dalla riproducibilità completa e tenere traccia di generatori casuali, impostazioni deterministiche, suddivisioni dei dati, versioni software e variazioni di esecuzione.

Domanda 1 di 8

Che cosa controlla principalmente l'impostazione di un seed casuale?

Anteprima di ogni domanda8 domande

Le risposte e le spiegazioni vengono visualizzate mentre rispondi al quiz.

  1. Che cosa controlla principalmente l'impostazione di un seed casuale?
    • A fixed dataset and row ordering even if source files change
    • A saved model checkpoint
    • Initialization of a pseudorandom generator sequence
    • A pinned package environment
  2. Perché un seme da solo non è sufficiente per riprodurre un esperimento?
    • A seed preserves data membership after row order changes
    • Data, code, preprocessing, versions and hardware also affect results
    • A seed fixes package versions and hardware
    • A seed guarantees identical floating-point execution
  3. Cosa possono fare gli algoritmi deterministici abilitanti?
    • Guarantee bitwise-identical outputs across platforms and releases
    • Remove all randomness from data and augmentation
    • Avoid some nondeterministic operations where deterministic implementations are available, sometimes at a performance cost
    • Increase accuracy by eliminating all stochasticity
  4. Perché seminare i lavoratori dei caricatori di dati o i loro generatori?
    • Workers may use separate random streams for shuffling and augmentation
    • Every worker automatically shares synchronized generator state
    • Worker seeds eliminate accelerator nondeterminism
    • Each worker independently supplies the training labels
  5. Quali evidenze stimano meglio la variabilità derivante dall'addestramento stocastico?
    • A single run selected for its best score
    • The lowest training loss from one run
    • Results across repeated runs or uncertainty estimates
    • A large model checkpoint saved once
  6. Why preserve explicit split identifiers as well as a seed?
    • Record only the train/test row counts
    • Preserve which stable example IDs belong to each partition
    • Set a different optimizer learning rate for each partition
    • Assume a seed preserves membership after upstream row ordering changes
  7. Which statement about bit-for-bit reproducibility is accurate?
    • It is guaranteed by using a seed once
    • It is the only useful definition of reproducibility
    • It is independent of floating-point execution
    • It may fail across hardware, software versions or nondeterministic operations
  8. What should be recorded for an auditable training run?
    • Data revision, split, code, configuration, versions and checkpoint
    • Only the seed
    • Solo il nome del modello
    • Only the best metric