diff --git a/README.md b/README.md index 90cb1b0809b4c1c783a031b4855b975063355055..78dd4c63fada028137e46b6be15d4ecf85e19c0b 100644 --- a/README.md +++ b/README.md @@ -32,9 +32,10 @@ which uses the data measured in real time during the flight as input and outputs To organize the work, it's suggested to divide it in 2 tasks: -1. **Define what's it is the apogee**: of course the apogee can be defined as the point of the trajectory where the vertical velocity is 0, but this definition is not applicable. Sensors have noise that disturbs the measurements, even at apogee the vertical velocity estimated is never equal to 0. Instead of detecting the exact instant of the apogee, it suggested to **define a region of the trajectory** where **it is reasonable** to assume that the rocket is at the apogee, or near it, and detect the apogee when the rocket enters in that region. **Finding the condition/conditions that define that region is part of the assignment**. - *(For example, the function detects the apogee when the altitude is > of 2700m. This condition define a zone that, in the logged flight, is near the apogee... but what happens if the rocket never reaches 2700m ? Or if at that altitude it is still moving with high vertical speed? This condition might work for this flight, but is not reliable in a general case and it is considered a bad choice. )* -2. **Implement an algorithm that detects the apogee**: starting from the definition of apogee found in the previous point, implement an algorithm in `apogee_detector.m` that detects the apogee. +1. **Define the condition that detects the apogee**: of course the apogee can be defined as the point of the trajectory where the vertical velocity is 0, but this definition is not applicable. Sensors have noise that disturbs the measurements, even at apogee the vertical velocity estimated is never equal to 0. + Instead of detecting the exact instant of the apogee, it suggested to **define a robust condition** that, if true, allows to decuce with confidence that that the rocket is **reasonabily near the apogee**. **Finding the condition/conditions is part of the assignment**. + *(For example, the function detects the apogee when the altitude is greater than 2700m. This condition define a zone that, in the logged flight, is near the apogee... but what happens if the rocket never reaches 2700m ? Or if at that altitude it is still moving with high vertical speed? This condition might work for this flight, but is not reliable in a general case and it is considered a bad choice. )* +2. **Implement an algorithm that detects the apogee**: starting from the condition found in the previous point, implement an algorithm in `apogee_detector.m` that detects the apogee. ## Algorithm requirements @@ -50,7 +51,7 @@ To take into account these factors, the function that you will submit will be te **data:** it is a support variable that you can use if and however you want, for example it could store previous sensors measurements or counters. It is declared inside `main.m`; if you want to use it you have to declare it there, otherwise you can just leave it as it is. -**timestamp**: the timestamp present in each log is expressed in milliseconds (us) +**timestamp**: the timestamp present in each log is expressed in microseconds (us) **pressure_measurement:** the barometer is used to measure the atmospheric pressure during the flight