Exercise idea: Airplane Boarding Simulation

Aperta
#1,475 3 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
content

Direzione di ricerca

Non vengono indicati file, test o punti di ingresso dell’implementazione. Inizia esaminando i metodi di boarding proposti e la visualizzazione e la ricerca collegate, quindi definisci come devono essere modellati e testati il processo, i parametri e i risultati. Il lavoro è completato quando esiste una specifica dell’esercizio concordata, con un ambito di confronto e criteri di completamento definiti.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

new exercise idea

There aren't a lot of modelling or simulation exercises right now. After watching a CGP Grey video recently, I thought it would be interesting to simulate the boarding process of an airplane and compare different methods. This could also work well as an exercise. It seems only suitable as a side exercise, though.

I haven't fully thought this through and I'm not even sure if this kind of exercise fits exercism well, but the responses on Slack were positive, so I decided to post the general idea here regardless.

There are a few methods to board an airplane that are used in practice and also some unpractical, but theoretically more efficient, ones:

  • Back to Front & Front to Back
  • Random
  • Window -> Middle -> Aisle
  • Steffen modified*
  • Steffen perfect*

(Visualisation of them)
(* Watch the video for an explanation, or if you're more interested, check out Optimal boarding method for airline passengers and Experimental test of airplane boarding methods (paywall warning))

The exercise would be about simulating the process and potentially comparing them in regards to the time it takes to fully board the plane. A bonus task could be a visualisation of the results or the process.

My naïve implementation would be to discretise the process, with a grid representing the aisle and seats and each action taking one time unit to do. The passengers would enter the grid in a specific order based on the used method. There would be multiple actions each passenger can do:

  1. Move forward in queue/aisle
  2. Store the carry-on in the overhead compartment
  3. Take a seat
  4. Make room for another passenger that has a seat further on the outside (e.g. aisle is already sitting, next passenger needs to move into window seat)

A few parameters could be changed:

  • seat layout
  • two entrances instead of one
  • the simplification of the simulation (e.g. one could skip 4) from above)

There are a few questions I don't know how to answer yet:

  1. Would the exercise say how to model the process or should the student come up with it?
  2. Depending on 1), do we solely test for results (this works regardless of the chosen implementation) or also the individual actions/steps (this would likely require the model to be part of the exercise)?
  3. Should a comparison be part of the exercise, or should it be enough to implement a single method (which?)?

As I said above, I'm really not sure if and how this would work, so please don't hesitate to share your thoughts & ideas on how a general exercise about a simulation of airplane boarding would work, especially if they're completely different to my ideas above :)

Lingua principale
Ruby
Stelle
362
Fork
566
Merge medio
15h 13m
PR unite (30g)
8

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di exercism/problem-specifications

Tutte le issue di exercism/problem-specifications

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.